L
Lori
I have a home user running WinXP Home connecting to our corporate
network (Win2K) via a VPN.
He's working without a problem with the exception of sporatic problems
connecting to our Exchange server (Exchange 2003 on Win2K) via Outlook.
At times, he'll be able to launch his email & work without a problem.
Randomly, Outlook hang and his connection to the Exchange server drops.
When this happens, his connection to the other servers remains
unaffected.
I found that when this problem occurs, if he pings the Exchange server
he's getting the public IP addy. However he CAN ping the internal IP
addy. This led me to believe something is wrong with his DNS config.
So I set up an LMHOSTS file creating a permanent resolution for our
Exchange server. I imported the LMHOSTS file, had him reboot, no dice.
When he pings the Exchange server by name he still gets the public IP
addy.
I'm completely confused as to what the problem is and how to fix it....
Any help would be greatly appreciated!
network (Win2K) via a VPN.
He's working without a problem with the exception of sporatic problems
connecting to our Exchange server (Exchange 2003 on Win2K) via Outlook.
At times, he'll be able to launch his email & work without a problem.
Randomly, Outlook hang and his connection to the Exchange server drops.
When this happens, his connection to the other servers remains
unaffected.
I found that when this problem occurs, if he pings the Exchange server
he's getting the public IP addy. However he CAN ping the internal IP
addy. This led me to believe something is wrong with his DNS config.
So I set up an LMHOSTS file creating a permanent resolution for our
Exchange server. I imported the LMHOSTS file, had him reboot, no dice.
When he pings the Exchange server by name he still gets the public IP
addy.
I'm completely confused as to what the problem is and how to fix it....
Any help would be greatly appreciated!