Software

Ask something
Discussion Locked

Microsoft Exchange and TCP/IP

0 helpful
7 replies

by mike.lacy

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Win2K Compaq Proliant 400MHz 4way server with 1meg of ram and Exchange 5.5 SP4 loaded on it. The problem is that after I loaded about 200 mailboxes to the server, moved from another server in the same site, approx. 20% of the users that were working just fine can't contact (ping) the server. Also the server can't ping the client. I took a laptop and used the exact wires at one of the clients that can't ping and it worked fine. The 20% worked fine Friday in the evening and not on the following Monday morning. The only change made over the weekend is that approx. 100 mailboxes were moved to the server.

7 replies

by malchango

I hate to say this, but it sounds more like a name resolution problem than an e-mail problem. Check to see if the new server is in the WINS database. If you are not using WINS, create an LMHOSTS file and put the server address in there. Other than that, see if these computers can see any other servers. Can they ping the gateway?

Try these things and see how they work.

Good Luck,
malChango

by mckaytech

This sounds like one of those seemingly unrelated co-incidence problems. There is no way I can think of for a mailbox migration to break basic network connectivity so I'm guessing that something happened to DHCP over the weekend.

When you take your laptop to a machine that doesn't work, and run "ipconfig /all" from the command line of both machines, does the output make sense?

paul

by wayne.rumley

This may be a daft point but... when you are pinging back and forth, are you using the name or the IP Address? If you haven't used the IP Address then try this (You could also enter the IP address of the MailServer into the Exchange profiles on the client).

Good Luck.

Wayne.

This discussion is closed to new replies.