Announcement

Collapse
No announcement yet.

SMTP VS TCP listen port can not be changed from 25

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • SMTP VS TCP listen port can not be changed from 25

    I am trying to change the default SMTP vs' TCP listen port on Exchange 2003, but it just keeps on listening on 25!

    I have restarted the SMTP service after altering the port in ESM, but it still accepts connections on 25 instead of whatever I set it to (I have tried 9925, 925 and 24).

    Any ideas?

    I have a feeling a reboot might fix it, but that's just stupid and rubish! I have had a problem with this server before where it looked like the GAL was not updating until a reboot - new users were not visable in Exchange until after reboot.

    Any ideas folks?

    thanks.
    Last edited by Carl Farrington; 3rd April 2007, 21:35. Reason: didn't specify E2k3

  • #2
    Re: SMTP VS TCP listen port can not be changed from 25

    I remember, we had some weird problems with this server about six months ago, after the boss continually hitting the reset button on the server a few times a day every time his wi-fi connection got a bit flaky. The IIS metadata was left corrupt, and there was some difficulty getting Exchange 2003 and SMTP to work properly again.

    This may be related. Ho hum

    Comment


    • #3
      Re: SMTP VS TCP listen port can not be changed from 25

      OK, I had to use Metaedit to alter the SMTP listen port (it was at Lm\Smtpsvc\1\ServerBindings)

      There is obviously something wrong with the integration between IIS and Exchange 2003 on this server.

      Unless somebody is able to help, I will play around myself and perhaps just leave it semi-broken for now

      At least I have been able to do what I needed to do for now, and it works.

      Comment


      • #4
        Re: SMTP VS TCP listen port can not be changed from 25

        If you have had to modify the meta base directly to get the change to take and the server has been reset at frequent intervals, then you probably have a system that is going to need some attention.

        At the very least IIS will need to be reinstalled, which on an Exchange server is not a straight forward job.

        At this time you could leave the server alone and hope that things don't get worse. Otherwise you need to be looking at possibly a full rebuild of that server so that it is stable and working correctly.

        The director who thinks resetting the server to fix a wireless connection needs to be instructed what the correct course of action is.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment

        Working...
        X