Port 25 problems

[3147]

I'm not sure what the hell is up with my Exchange server so I hope someone can help . I can't telnet from local clients or externally to port 25 on the mail server. All the other server services are working fine. I can telnet to post 25 on the server it’s self no problem. I’ve deleted the Virtual SMPT server and rebuilt it but this did not help. Can any one shed any light or pointers


\\muos o(-_-)o

 

[Marcs41]

router? firewall? ISP block? ....

Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.
Free Tip: The F1 Key does NOT destroy your PC!}

 

[3147]

router? firewall? ISP block? .."

What you quoting above has no relevance as the tests I’m doing a LAN based, but thanks anyway

If I go to the server and input the following to cmd

telnet 127.0.0.1 25 I get connected to the SMPT server

If I go to a client PC within the LAN and telnet to the server on port 25 the connection is refused

I’m go puzzled….. Any help welcome

 

[Marcs41]

no relevance?
That is your first mistake!

I do not know your setup, but a client PC routes throught the default gateway, which may or may not be a router or firewall. In other words, it is not de facto so the a client PC's Telnet session even gets to your server!

Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.
Free Tip: The F1 Key does NOT destroy your PC!}

 

[Davetoo]

The first thing you should do 3147 is knock that chip off your shoulder. Going to any site for help, then disrespecting those that are trying to help you is not a good move, period.

The next thing you should do is heed Marc's advice and check the things he asks you to check, and provide the information he asks for. He knows what he's talking about, as do many others here...clearly you don't, so it'll pay you to learn the troubleshooting steps that you are given as they may benefit you later on with a different problem.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[3147]

God I must have p***ed you off lander215 I did not mean to disrespect any one at all, I'm not like that. Chip off your shoulder what the hell,,, are you dam mad? I write a few words and you kick my a** like that. I’m only a tech user, I’m sorry if I got it wrong. Marc I'm very sorry if I've upset you I did mean to. Just for your info Marc a guy within the company that I help for free a kid’s charity also dose a bit of IT changed the exchange server to listen on port 2525 as he was testing a plug-in and forgot to change it back. I’m sorry if I anyone else on the forum took offence like lander215. I’m new so please accept my apologies if there needed.

Jeff

 

[3147]

I should say before I get ripped again he only changed his on indound connections....

Jeff

 

[Marcs41]

You did not offend me or lander, but the point lander is making is that you should answer queries if you don't know the answer in the first place instead of assuming you know it cannot be what I refer to.
WE are not in front of your LAN or PC, so WE can only ask you to check and post back on things WE know could be the problem.
If they are not, we move on the the next step.

So, that said, since you state yourself the port has been changed to 2525, it is quite obvious a Telnet on 25 will not work. You do however not specify WHERE the 2525 was changed, on the Server (which would surprise me as you can Telnet on the server itself), or on the router/firewall?
Either way, you either put it back to 25, or Telnet on 2525.

Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.
Free Tip: The F1 Key does NOT destroy your PC!}

 

[Davetoo]

There was no ripping involved and like Marc said, nobody was offended. But the attitude you came across with was inappropriate for these forums.

While there is never a dumb question, there can be some silly responses from time to time.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[3147]

ok let's just forget it all and move forward.

All the best

Jeff