How bizzare - XP TCP/IP problem.

[carl0s]

Here's a weird one.

 

My laptop is/was having connectivity issues - no problem getting to the router here, and the router could ping t'internet, also I could do DNS lookups, but nothing else.

 

Anyhow, I can see what's wrong, I just can't understand why.

 

XP hasn't err, fully realised that the LAN cable has been unplugged - it shows as 'Network cable unplugged' in network connections, and the red-cross in the system tray, but if I do an ipconfig, I see the following:

 

Windows IP Configuration


Ethernet adapter Wireless Network Connection:

       Connection-specific DNS Suffix  . :
       IP Address. . . . . . . . . . . . : 192.168.2.3
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.2.1

Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       IP Address. . . . . . . . . . . . : 192.168.1.4
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1

 

The WLAN here (girlfriends house) is on 192.168.2.0/24.

192.168.1.0/24 was temporarily set on the LAN connection whilst I was reprogramming my Dbox2 cable box on Sunday.

The weirdest thing is that I have the ethernet cable unplugged though.

 

So XP isn't fully realising that the network cable is unplugged and the routing table isn't being updated accordingly. The routing table therefore looks like this:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 16 6f ba f1 76 ...... Intel(R) PRO/Wireless 2915ABG Network Connection
- Packet Scheduler Miniport
0x50003 ...00 15 58 2d f4 74 ...... Broadcom NetXtreme Gigabit Ethernet - Packet
Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
         0.0.0.0          0.0.0.0      192.168.1.1     192.168.1.4       20
         0.0.0.0          0.0.0.0      192.168.2.1     192.168.2.3       25
       127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
     192.168.1.0    255.255.255.0      192.168.1.4     192.168.1.4       20
     192.168.1.4  255.255.255.255        127.0.0.1       127.0.0.1       20
   192.168.1.255  255.255.255.255      192.168.1.4     192.168.1.4       20
     192.168.2.0    255.255.255.0      192.168.2.3     192.168.2.3       25
     192.168.2.3  255.255.255.255        127.0.0.1       127.0.0.1       25
   192.168.2.255  255.255.255.255      192.168.2.3     192.168.2.3       25
       224.0.0.0        240.0.0.0      192.168.1.4     192.168.1.4       20
       224.0.0.0        240.0.0.0      192.168.2.3     192.168.2.3       25
 255.255.255.255  255.255.255.255      192.168.1.4     192.168.1.4       1
 255.255.255.255  255.255.255.255      192.168.2.3     192.168.2.3       1
Default Gateway:       192.168.1.1
===========================================================================
Persistent Routes:
 None

 

Strange huh. I'm just disabling the ethernet entirely for now whilst I figure it out. I'll probably try the usual netsh int ip reset stuff, maybe winsockxpfix and what not, but I just thought it was really weird and definately not something I've ever seen happen.

 

Anyone else seen this?

[ivan]

Similar thing here.

 

I had the CarPC out and connected it indoors via the ethernet cable to do some updating the other day.

 

When I disconnected it and put it back in the car it wouldn't connect to the internet via wireless (on the same router) until I disabled the ethernet adapter. It connected to the router OK but no further, not even the LAN.

 

Damn M$...

[Lewis]

/release?

[Pete]

I've seen TCP/IP stack on Windowz do lots of odd things.

 

Was it DHCP or manually configured out of interest?

[ivan]

Didn't work for me. Nor did /renew

[carl0s]

I just had a brainstorm. When I was flashing the DBox, it told me something in german about a mediasense patch that it had applied.

 

I thought nothing of it and just carried on anyway.

 

Seems some NICs have problems detecting a link to these DBoxes with their half-duplex 10baseT connection, hence the need for a 'mediasense patch' (which I didn't need.. mine just worked..)

 

I guess that'll be the culprit here then. Phew!

[Lewis]

Didn't work for me. Nor did /renew

 

renew wont work if it is static

[carl0s]

I've seen TCP/IP stack on Windowz do lots of odd things.

 

Was it DHCP or manually configured out of interest?

 

 

 

It was manually configured.

 

It's the mediasensing patch. There's a german page which points to the registry key here:

http://www.keyteam-board.to/wbb2/thread.php?postid=302583

 

Thank fuck for that. I never reformat for little problems, but I had to last week because d3d acceleration just was not going to work, and I tried *all* the known culprits, so I'd have been really pissed off if I wasn't able to figure this one out as well.

 

I'd already tried downgrading the NIC driver since I remember windows update giving me a newer one a little while ago.

 

Ho hum. Thought something really odd was going on for a minute.

[carl0s]

Folge dann diesem Pfad:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters

 

Hast Du Dich bis zum Pfadende durchgehangelt dann machst Du im rechten Fenster einen Rechtsklick mit der Maustaste und fügst den nachfolgenden DWORD Wert ein

 

Wertname: DisableDHCPMediaSense

Datentyp: REG_DWORD - Boolescher Wert

Wertdatenbereich: 1

 

sweet

[Pete]

You're like the kids at work... "How do you do xxxxyyyy?" - 2 seconds later after disturbing me from my highly intellectual work* - "It's ok I worked it out"

 

*(ok, forum browsing)

[carl0s]

LOL

 

I really didn't think I'd figure that one out though, I mean.. it's not an easy one to google for really I don't think. Sort of thought I might eventually get it fixed by running a load of general tools and scripts and never actually finding the root cause.

 

I'm just glad I remembered where the 192.168.1.4 came from - at first I thought it was from a customers house the other day.

 

phew.

 

You can get back to your highly intellectual work now, cheers!

[ivan]

Nice one Carlos. I'll take a look in that area on the CarPC tomorrow.

 

renew wont work if it is static

 

T'was DHCP on both Lewis. Sorry, should have said.