NIC -> Modem-Router TCP/IP Problem

[hksoftware]

Hi,
Here's the situation:
I have a Wi-Fi modem-router, connected to my PC's NIC with a patch cable. Link is ok, both PC and router confirm 100MB/s connection. However, the PC cannot get an IP from the routers internal DHCP server. Not can they ping each other.

Here's some facts:
it IS a patch cable, connection IS fine.
router is fine (Tried XBOX on ethernet ports, no problems at all.)
Tried reinstalling NIC with latest drivers.
No firewall is switched on.
Tried removing any other protocols (such as Microsoft Windows Network Client, file & Printer sharing)

It appears to be a layer 3 protocol issue, but I'll leave that to the experts.

I'm thinking of just bunging another NIC in there instead but I'd prefer to get this running.

 

[bcastner]

1. "No firewall is switched on."

Many firewall products are still active even if set to disabled; notably Norton and Zone Alarm. You need to keep them from starting at all, preferably, configure them properly for your LAN setting.

2. It could be a Winsock service stack issue: faq779-4625

3. The inability to ping suggests a firewall issue. Beware of "hidden" firewalls in anti-virus programs. Pc-Illan, for example, is notorious for this.

 

[hksoftware]

Thanks for the pointers.
Zone alarm is fully shut down, not running.
AV is Norton AV, no firewall there.

I'll look into the Winsock fixer and keep you posted.

Thank you!

 

[hksoftware]

Just Tried the Winsock Fix and it did absolutely nothing.
Any more ideas?

 

[LawnBoy]

If your XBOX can get through the router then the router is working and handing out DHCP. But you knew that...

When you say you can't ping the router, have you manually set an IP in the nic? No IP, no ping.

What do you get if you ping localhost?

What do you get from ipconfig /all?

 

[hksoftware]

Hi,
Just tried manually setting the NICs IP...

Can ping localhost fine, 100% success, <1ms.
ipconfig /all gives:

Node Type: Unknown
IP Routing Enables: No
WINS Proxy Enabled: No

DHCP Enabled: No
IP Address: 192.168.1.5
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
DNS Servers: 192.168.1.1

 

[LawnBoy]

Your settings look fine. If you're sure of the patch cable and the port you're connected to on the router, then it looks like a dead NIC.

 

[attrofy]

With DNS enabled, did you do "IPCONFIG /RELEASE" and "IPCONFIG /RENEW"?

When you say tried pinging localhost - what do you mean exactly? Loopback test of 127.0.0.1?

 

[LawnBoy]

Yes, when you

ping localhost

it performs a loopback test, proving the OS is communicating with the NIC. It does not prove that the NIC is communicating with the network, just that it is alive.

 

[attrofy]

I actually found out by accident in another application I was working on that typing "localhost" was the same as the 127.0.0.1. I learned something new (which you confirmed) today - that means I get to go home now.

If that patch cable is indeed a straight through connection and not a crossover cable, and you are getting good loopback test, you might check to see if the NIC mfg has a windows utility - many of them now have testing functions in them. Also, is there any settings in the WAP/Router that lets you specifically configure the LAN side seperatly from the WI-Fi side. Is this a Linksys router, which model? They tend to be notorious for requiring the latest software/BIOS updates.

 

[bcastner]

Localhost is whatever the HOSTS file says it is, usually 127.0.0.1 but not necessarily.

 

[attrofy]

ahhh - that makes more sense. Since it was the server I was messing with - that stands to reason.