New x58 Motherboard: Destination Host Unreachable

[Eluros]

Greetings, all,

So, with the recent pan-searing of my old S939 Motherboard, I plopped an i7 920, EVGA x58, and 6 gigs of RAM into my system (I'll upgrade to x64 Vista pretty soon). Removed all chipset/network/display/etc. drivers, repaired the OS, and installed the new drivers. Everything seems to work fine... except for my networking drivers.

I'm on a college campus (so no router in my room), but am able to pull a valid DHCP-enabled IP address from the network. However, whenever I try to ping other websites, it states: "Destination Host Unreachable". The wall port still works, as I verified with my laptop.

I've tried uninstalling drivers, removing them completely with DriverSweeper, and installing new ones from EVGA's website. I've tried-- per the EVGA technicians' recommendation-- flashing the bios. However, still no luck.

Any ideas? I really prefer not to reformat, so I'm open to pretty much anything. My boss (I actually work in IT) suggested I try seeing if I can run a tracert from the command prompt... since I couldn't ping I doubt it, but I'll give it a shot.

Thanks in advance!

 

[spidey07]

What is the source address or the destination host unreachable? This could also be a firewall or access control list on the network not allowing your machine to ping.

 

[DrGreen2007]

First, can you ping your default gateway or DNS servers?

 

[JackMDS]

Try another Network card (if you need to buy one they are less than $10).

Otherwise, http://www.ezlan.net/debug.html

 

[Eluros]

Greetings,

Thanks so much for your supplies!
First things first: So, I've discovered that I am able to access websites by their IP Address, even though I can't via their FQDN (if I'm remembering what a hostname is called correctly from back when I took the Network+). Sounds like a DNS issue to me... however, I've tried ipconfig/flushdns and still no go.

My machine definitely can ping google and other sites... done it other times before from here in the past.

I can indeed ping my Default Gateway or whatever I want, as long as it's a numeric IP Address.

Thanks again, all! (Glad I have a laptop, too)

 

[JackMDS]

Try to change the DNS to use 4.2.2.2

 

[Eluros]

Try to change the DNS to use 4.2.2.2

Jack, fascinating; it worked! It's running extremely slowly, but I'm typing this with it. I read that it's a free server apparently... may I ask what you believe the implications of the non-DHCP DNS working are, so I can tell our college's network technicians?

Thanks so much!

Edited for clarification

 

[spidey07]

Give them the output of "ipconfig/all" It almost sounds like somebody is playing hacker on your subnet.

 

[Eluros]

Interesting... so I plugged my laptop into the wall, grabbed my DNS servers, and manually popped them in, and they work as they ought. Seems like DHCP should be able to pull them just fine, but at least I now have a workaround.

I look forward to seeing if I'll have the same issue (having to manually input my DNS server) at home this summer...

While any more suggestions/advice would be appreciated as to the root of the problem, the immediate problems have been solved. Thanks!

 

[spidey07]

Originally posted by: Eluros
Interesting... so I plugged my laptop into the wall, grabbed my DNS servers, and manually popped them in, and they work as they ought. Seems like DHCP should be able to pull them just fine, but at least I now have a workaround.

I look forward to seeing if I'll have the same issue (having to manually input my DNS server) at home this summer...

While any more suggestions/advice would be appreciated as to the root of the problem, the immediate problems have been solved. Thanks!

What you are running into is network security. Campus networks are a haven of "bad shit being done".

There are many counter measures for college campus networks as they are the hot bed of "bad shit". It may not make sense but your symptoms are fit for combating college students.

Basically, I'm not surprised at the results if you are on a college network.