Cannot ping server on network from one laptop only

I have a laptop connected to our network that sees every machine but our exchange server.
It picks up an IP address by DHCP ok and I can see other servers and ping all devices but I just cannot see or ping the exchange server whatever i try.
My network has three servers and about 40 pcs connected and I can ping all other address ok.
If I run an IP scan scan program like Angry Ip Scanner ( on my laptop and my PC which are sat next to each other on my desk my PC list the server and ip address as 'alive' but the laptop doesn't see it at all and shows the ip adress of the server as dead.
I have tried running a winsock fix util and resetting tcpip also but to no avail.
Any halp would be very much appreciated. If I can get away without having to reinstall XP that would be great!
Thanks in advance
Who is Participating?
asiduConnect With a Mentor Commented:
Remove the DHCP setting for the machine and assign another IP address to the machine manually and see if the problem still exists.
frsupportConnect With a Mentor Commented:
run a tracert from the client to the exchange server , see exactly where the connectivity is lost

Check your host files on the client, make sure there are no incorrect entries pointing to the exchange server

Uninstall & reinstall the clients network card


try a ping

check your clients firewall

fhmcConnect With a Mentor Commented:
Am I correct to assume both the laptop and the exchange server in question share the same subnet?

If so...
I second asidu's suggestion so far as a first first phast testing is concerned.

My initial tests would also include:
ARP testing (check the ARP tables on both hosts (are there refs to the "target" host's IP or MAC address from either "source" host?
 clear the ARP cache on both hosts
verifying no "goofy" type custom routes were "somehow" defined for either the laptop's IP on the server or the server's IP on the host
verifying no "goofy" firewall policies are in place on either the server or laptop that exclude the other's address
try plugging the server and/or laptop into a different switch port (maybe the switch is your problem.)
check all of your log files, eventvwr, firewall logs, etc.

it may sound like a lot of work, but all of the tests together shouldn't take more than 15 minutes.
if you're interested in pursueing any of my suggestions and you have any questions w/ regard to the process, please indicate so in your next post.  I'll do what I can to assist you.

finally, a packet analyzer such as wireshark can be employed to provide a more granular observation of the conversation (rather, attempted conversation) between the two hosts.

good luck.
We Need Your Input!

WatchGuard is currently running a beta program for our new macOS Host Sensor for our Threat Detection and Response service. We're looking for more macOS users to help provide insight and feedback to help us make the product even better. Please sign up for our beta program today!

BigCapAuthor Commented:
Thanks for the comments guys. I will take a look at this again and keep you posted asap!
A few other more important issues have cropped up since...bah!!

Thanks again
I have no objections.
no objections
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.