Win2k Server & Exchange 5.5 static port mapping problem with DS and IS

[shitomu]

I just upgraded the server in my building from Windows NT 4.0 Server to Windows 2000 Server. I back'd up and removed Exchange 5.5 before doing so, then re-installed it and restored all mailboxes and map'd users. Everything went fine.

My predecesor setup Exchange 5.5 (with the static port registry changes, for the DS and the IS) and punched holes in the firewall we have, so that users can remotely access (through the Internet) Calendaring, Contact lists, and Email, through Outlook, using MAPI. That worked all fine and good with NT 4 Server. I found the fix on Microsoft's site, but I can't seem to get it to work under Win2k Server.

I realize that VPN'ing would work fine, as a substitute (there is already a VPN setup for other applications), but due to political reasons, that is not an option right now.

What are your suggestions?

Thanks

 

[shitomu]

Here's a little more information for you:

I setup 1225 and 1226 as the ports that Exchange 5.5 communicates on. Port 1225 receives communication just fine, but it's port 1226 that isn't.

Any help would be GREATLY appriciated.

 

[aniconica]

Get the utility called fport.exe and run it on the server and this will tell you if any other applications have control of that particular port number. I had a similar problem and found that a service was grabbing the port before exchange could, and stopped it from working.

 

[shitomu]

aniconica

Thanks for your reply and I did as you suggested. These are the programs that are using ports 135, 1225, and 1226:

233 svchost -> 135 TCP C:\WINNT\system32\svchost.exe
233 svchost -> 135 UDP C:\WINNT\system32\svchost.exe
1232 dsamain -> 1225 TCP d:\exchsrvr\bin\dsamain.exe
1314 store -> 1226 TCP d:\exchsrvr\bin\store.exe

"dsamain" and "store" look correct, but "svchost" looks strange; I would assume that Exchange 5.5 would be handling that.

aniconica and anyone else, have you heard of any problems with an incompatibility with AD and Exchange 5.5?

Also, I have been doing some reading and there is one thing that I haven't done, that I will try tonight, after everyone has gone home: change the LDAP port, for Exchange, from 389 to 390 and see if that corrects the problem.

Thanks for your help!

 

[shitomu]

Here's more information about the problem:

There are multiple buildings and the AD spans all of them. Email can only be accessed in the building (where I work) where the Exchange server is.

The question now: do I need to install the ADC, when running Exchange 5.5 in an AD, when the AD spans multiple buildings and IP subnets?

 

[shitomu]

I'm a little late with this, but here goes:

The problem that I encountered was that I somehow misconfigured Exchange 5.5 and instead of giving the FQDN for the server, after getting Outlook configured for the server, it would only pass the hostname. As a quick patch, until I can do a reconfiguration, I distributed HOSTS and LMSHOSTS files to the users to point the hostname to the IP address of the server.