After a change of the Exchange server's ip address and a switch to NAT. The client Outlook doesn't start off initially, after an error of failure to load "Your Microsoft Exchange Server is not available." Outlook hitting retry will then it will go through.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Corporate Outlook starting problem
- Thread starter msakata
- Start date
HI.
This is a name resolution problem.
You can do the folowing (not all solutions are good for you, you should check each one individualy):
* Check if the clients were using LMHOSTS or HOSTS file with the wrong ip address.
* Implement an internal DNS server instead of using the ISP DNS servers. This can also improve performance.
* Implement WINS
* Use HOSTS or LMHOSTS files on clients with the new name to ip address mapping of your server.
However server side solutions like DNS and WINS should be preferred over manual client side solution like LMHOSTS and HOSTS files.
Bye
Yizhar Hurwitz
This is a name resolution problem.
You can do the folowing (not all solutions are good for you, you should check each one individualy):
* Check if the clients were using LMHOSTS or HOSTS file with the wrong ip address.
* Implement an internal DNS server instead of using the ISP DNS servers. This can also improve performance.
* Implement WINS
* Use HOSTS or LMHOSTS files on clients with the new name to ip address mapping of your server.
However server side solutions like DNS and WINS should be preferred over manual client side solution like LMHOSTS and HOSTS files.
Bye
Yizhar Hurwitz
- Thread starter
- #3
Thank you for posting. I have changed the internal dns of exchange box to point to the new internal ip address. and restarted the DNS service.
Will WINS help this situation even if I am running the Exchange 2000 with Windows 2000 Server.
Lastly one machine inside the network is able to start Outlook without it ever asking for a retry or saying it is unavailable.
SO I tried to duplicate it settings on the bad computers.So I change both hosts file (hosts and lmhosts) to represent the new server ip adress like "10.10.10.2 Server" in the top of the file. Lastly I even imported a part of the registry for
"HKEY_Local_machine/Software/Microsoft/Exchange" from the computer which Outlook was running fine on.
If you could help some more that would be much appreciated.
Thank you
Will WINS help this situation even if I am running the Exchange 2000 with Windows 2000 Server.
Lastly one machine inside the network is able to start Outlook without it ever asking for a retry or saying it is unavailable.
SO I tried to duplicate it settings on the bad computers.So I change both hosts file (hosts and lmhosts) to represent the new server ip adress like "10.10.10.2 Server" in the top of the file. Lastly I even imported a part of the registry for
"HKEY_Local_machine/Software/Microsoft/Exchange" from the computer which Outlook was running fine on.
If you could help some more that would be much appreciated.
Thank you
HI.
The following info should help:
* How many (and version) servers in the network?
* How many clients and what OS?
* Outlook version in use?
* How many ip subnets?
* Are there any WAN links?
* How is ip addressing currently configured?
* How is name resolution currently handled?
* Current DHCP WINS DNS HOSTS LMHOSTS settings?
I assume that if you point all clients and servers to the internal W2K DNS server as the primary DNS server and you remove all existing LMHOSTS and HOSTS files (only remove obsolute lines, not the whole HOSTS file) you will be able to solve but it depends on your specific network.
Bye
Yizhar Hurwitz
The following info should help:
* How many (and version) servers in the network?
* How many clients and what OS?
* Outlook version in use?
* How many ip subnets?
* Are there any WAN links?
* How is ip addressing currently configured?
* How is name resolution currently handled?
* Current DHCP WINS DNS HOSTS LMHOSTS settings?
I assume that if you point all clients and servers to the internal W2K DNS server as the primary DNS server and you remove all existing LMHOSTS and HOSTS files (only remove obsolute lines, not the whole HOSTS file) you will be able to solve but it depends on your specific network.
Bye
Yizhar Hurwitz
- Status
Similar threads
