Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Workstation Lost Exchange Connection


  • Please log in to reply
3 replies to this topic

#1 cuistech

cuistech

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:03:37 PM

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 1.2.3.4
"exchangeserver" has an ip address of 1.1.2.3 and has not been recently changed

Investigation
While in a command prompt, remotely logged into "workstation," I ran "ping 1.1.2.3" and the results timed out, with 4 failures. I pinged 1.1.2.4 and 1.1.2.5 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 [1.1.2.21]" 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 1.2.3.4 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 1.1.2.4 and 1.1.2.5, the results were gateway (1.2.1.1), external gateway (192.x.y.z), otherserver (1.1.2.4). When I did it for exchange server, my hopes were gateway (1.2.1.1), external gateway (192.x.y.z), *, with the last 27 hops being dead. But if I tracert now, it tells me "exchangeserver [1.1.2.3]".

Evaluation
- 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.

BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:09:37 PM

Posted 19 September 2011 - 11:56 AM

Check your router settings there is a route missing preventing you from communicating to another subnet.

Also hiding things makes it difficult for us to assist you.

the 192.168.0.0/16 range is widely known.

Can you paste the full tracerts unedited.

#3 cuistech

cuistech
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:03:37 PM

Posted 19 September 2011 - 12:06 PM

1.2.1.1
192.168.2.18
*
* (repeat until failure at jump 13 - "destination host unreachable")

That was the last time I attempted to resolve it via name. I went back to repost a new tracert, just to make sure. Now it connected in 3 jumps, when I did it via IP, and via name.

Now I'm getting:
1.2.1.1
192.168.2.18
[exchangeserver] 1.1.2.3

I guess I was just impatient. I'm sorry for wasting your time... /facepalm...

#4 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:09:37 PM

Posted 19 September 2011 - 12:29 PM

Eh it happens. Glad it is working now, must have been a network glitch.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users