Posted 19 September 2011 - 11:22 AM
I have a XP-SP3 workstation that will not connect to our exchange server. It has in the past, however, as I've actually used this workstation.
Here's the basics:
"workstation" has an ip address of 220.127.116.11
"exchangeserver" has an ip address of 18.104.22.168 and has not been recently changed
While in a command prompt, remotely logged into "workstation," I ran "ping 22.214.171.124" and the results timed out, with 4 failures. I pinged 126.96.36.199 and 188.8.131.52 and a few others on the 1.1.x.x subnet with complete success.
At "workstation," I worked it from the other way and ran "ping exchangeserver" and came up with the result of "exchange server [184.108.40.206]" which is an IP address that has never been used, and especially not for a server. It, predictably, failed.
I attempted to "ipconfig /flushdns" and was told it resolved successfully, but I was still unable to get outlook up and running, not was I able to get a connection to 220.127.116.11 or exchangeserver in the command line.
The next command I thought to use was "tracert," which I did for all the machines I pinged. Pinging 18.104.22.168 and 22.214.171.124, the results were gateway (126.96.36.199), external gateway (192.x.y.z), otherserver (188.8.131.52). When I did it for exchange server, my hopes were gateway (184.108.40.206), external gateway (192.x.y.z), *, with the last 27 hops being dead. But if I tracert now, it tells me "exchangeserver [220.127.116.11]".
- The workstation IS connected to the network
- The DNS is now correct (tracert shows the table has been fixed, based on the name resolution above)
- The gateway isn't broken, or no one would be connecting to outlook or any server for that matter
What am I missing? Or what should me next steps be? Google has a lot of answers that feature flushdns. I found one thread that says I need to "reset the stack" and reboot the machine. Does that make sense to anyone, because I'm not familiar with that and need some education on it before I'm comfortable enough to just go ahead and try it remotely.