adding second network card stops internet connection from working

[tomtorfs]

Everyone,

I've got a Windows XP PC connected to a corporate LAN using DHCP etc.,
working perfectly. I needed to add a second network card to this PC to
be able to communicate with instruments. The second network card is
configured with a static IP address of 192.168.0.1 and subnetmask of
255.255.255.0.

When I disable the second network card internet works fine. When I
enable the card, I cannot browse to websites outside of our corporate
LAN. nslookup for these sites works, but the actual browsing gives a
timeout error.

I did a route print:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 13 21 69 01 81 ...... Broadcom NetXtreme Gigabit Ethernet
0x30004 ...00 10 18 11 cc 77 ...... Broadcom NetXtreme Gigabit Ethernet
for hp
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 146.103.2.189 146.103.32.46
20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
146.103.0.0 255.255.192.0 146.103.32.46 146.103.32.46
20
146.103.32.46 255.255.255.255 127.0.0.1 127.0.0.1
20
146.103.255.255 255.255.255.255 146.103.32.46 146.103.32.46
20
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1
30
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1
30
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1
30
224.0.0.0 240.0.0.0 146.103.32.46 146.103.32.46
20
224.0.0.0 240.0.0.0 192.168.0.1 192.168.0.1
30
255.255.255.255 255.255.255.255 146.103.32.46 146.103.32.46 1
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
Default Gateway: 146.103.2.189
===========================================================================
Persistent Routes:
None

I suspect the problem is the second 224.0.0.0 with mask 240.0.0.0 which
is directed to 192.168.0.1. Actually the only addresses I want to go to
the second network card are 192.168.0.* (which is why I used
255.255.255.0 as subnetmask for the second card). Why is Windows XP
adding the other double entries to the routing table, and more
importantly how can I get them out? I tried route delete but this does
not seem to work, and I would prefer a somewhat elegant solution (do
not want to be hardcoding any dynamic IP addresses etc.).

Can anyone help?

thanks,
Tom

 

[Grim Reaper]

192.168.0.1 is usually reserved for routers and the MSHOME network.
Try setting your second card to a some other number. 192.168.0.2 might
work... if not, try 192.1.0.1.
___________________________________
The Grim Reaper

 

[tomtorfs]

192.168.0.1 is usually reserved for routers and the MSHOME network.
Try setting your second card to a some other number. 192.168.0.2 might

work... if not, try 192.1.0.1.

The address makes no difference. However, I found out the routing table
was not the problem (224.* with submask 240.* does not affect my
external addresses such as 212.*). If I manually configure the web
proxy everything works fine, but not if the automatic proxy
configuration script is used (that script runs from a server at 10.*,
so should also not interfere with the 192.168.* local network).
Weird... I'll stick to the manual proxy setting for now.

greetings,
Tom

 

[Jack \(MVP\)]

Hi
Second card has to be on a different sub net.
The simplest way.
Card One 192.168.x.x Example 192.168.0.1
Card Two 192.168.y.x Example 192.168.1.1
Jack (MVP-Networking).

 

[tomtorfs]

Jack,

Second card has to be on a different sub net.
The simplest way.
Card One 192.168.x.x Example 192.168.0.1
Card Two 192.168.y.x Example 192.168.1.1

They are on a different subnet, first card has dynamic IP in range
146.103.32.* with subnetmask 255.255.192.0, and the second card has
static IP 192.168.0.1 with subnetmask 255.255.255.0. Anyway, everything
works fine now apart from automatic proxy configuration, I don't
understand why that refuses to work. Fortunately I could work around
this, as I used the Group Policy editor to apply manual proxy
configuration for all users, so the problem is basically solved.

greetings,
Tom