Link to home
Start Free TrialLog in
Avatar of adamscott0049
adamscott0049

asked on

IP Configuration Help

I've got an XP machine that I wish to connect to two completely different networks, and I'm having some issues.
Configuration Attached...
There are no issues when attempting to access network resources on each adaptor, ie, www.domain1.com and www.domain2.com but when you try and access an internet resource (only available through domain1.com adaptor) the connection times out.
Can anyone offer any assistance?
Ethernet adapter Local Area Connection:
 
        Connection-specific DNS Suffix  . : domain1.com
        Description . . . . . . . . . . . : Intel(R) 82566DM Gigabit Network Con
nection
        Physical Address. . . . . . . . . : 00-1C-C4-9B-5F-77
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 172.16.103.59
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 172.16.103.254
        DHCP Server . . . . . . . . . . . : 172.16.2.1
        DNS Servers . . . . . . . . . . . : 172.16.2.11
                                            172.17.2.1
                                            10.0.1.90
        Lease Obtained. . . . . . . . . . : 05 August 2008 08:25:48
        Lease Expires . . . . . . . . . . : 13 August 2008 08:25:48
 
Ethernet adapter Wireless Network Connection:
 
        Connection-specific DNS Suffix  . : domain2.com
        Description . . . . . . . . . . . : D-Link AirPlus G DWL-G122 Wireless U
SB Adapter(rev.C)
        Physical Address. . . . . . . . . : 00-17-9A-B9-3A-29
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.10.101
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.10.1
        DNS Servers . . . . . . . . . . . : 192.168.10.1

Open in new window

SOLUTION
Avatar of Member_2_3654191
Member_2_3654191
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Can you do a route print at the commnd ine and post back your results. Thanks
Hi

Your computer is getting confused because you have defined two default gateways. Remove the default gateway from your wireless adapter (domain2). The reason for this is - if your computer tries finding another computer and it cannot locate it, it will send it to the default gateway for help.  This mostly happens when you want to connect to a resource that is not on your network (for instance internet), in which case the resource should be sent to the router (gateway) connected to the internet, and you have said it should go through the default gateway of domain1.

Also, I would suggest looking at your routing tables to ensure you will still have connectivity to domain2 after doing the above change.
Go to the command prompt and do
route print

you should see a line like
Network Destination    Netmask             Gateway               Interface               Metric
192.168.10.0                255.255.255.0   192.168.10.101   192.168.10.101

If not then do the following on your command line

route -p add 192.168.10.0 mask 255.255.255.0 192.168.10.101

The above will create a persistant (survives reboots) to the domain2 network.

Hope this helps

Cheers


Avatar of Kieran_Burns
Kieran_Burns

If I could +1 an answer it would be Nivlesh to get it - exactly as he says. You can only have ONE default gateway. You will need to set up static routes to access any resources on the other subnet.
Avatar of adamscott0049

ASKER

Here's an updated route print. I've added a persistant route, but it's still not working for some reason. Thanks to all for your help.
C:\Documents and Settings\adam.scott>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 1c c4 9b 5f 77 ...... Intel(R) 82566DM Gigabit Network Connection - Pa
cket Scheduler Miniport
0x3 ...44 45 53 54 42 00 ...... Nortel IPSECSHM Adapter - Packet Scheduler Minip
ort
0x4 ...00 ff e6 03 65 59 ...... TAP-Win32 Adapter V8 - Packet Scheduler Miniport
 
0x50006 ...00 17 9a b9 3a 29 ...... D-Link AirPlus G DWL-G122 Wireless USB Adapt
er(rev.C) - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0   172.16.103.254   172.16.103.59       20
          0.0.0.0          0.0.0.0     192.168.10.1  192.168.10.101       100
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
     172.16.103.0    255.255.255.0    172.16.103.59   172.16.103.59       20
    172.16.103.59  255.255.255.255        127.0.0.1       127.0.0.1       20
   172.16.255.255  255.255.255.255    172.16.103.59   172.16.103.59       20
     192.168.10.0    255.255.255.0   192.168.10.101  192.168.10.101       100
     192.168.10.0    255.255.255.0     192.168.10.1  192.168.10.101       1
   192.168.10.101  255.255.255.255        127.0.0.1       127.0.0.1       100
   192.168.10.255  255.255.255.255   192.168.10.101  192.168.10.101       100
        224.0.0.0        240.0.0.0    172.16.103.59   172.16.103.59       20
        224.0.0.0        240.0.0.0   192.168.10.101  192.168.10.101       100
  255.255.255.255  255.255.255.255    172.16.103.59               3       1
  255.255.255.255  255.255.255.255    172.16.103.59   172.16.103.59       1
  255.255.255.255  255.255.255.255    172.16.103.59               4       1
  255.255.255.255  255.255.255.255   192.168.10.101  192.168.10.101       1
Default Gateway:    172.16.103.254
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
     192.168.10.0    255.255.255.0     192.168.10.1       1

Open in new window

Could you rerun the IPConfig again, just so we can confirm the second default gateway has gone?
You still have two default gateways. Remove the gateway in the TCP/IP settings for one of the NICs as stated in the before mentioned question and set a static route for networks that are not directly connected to that NIC but should be reached over that connection.
Your route is incorrect.
You need to add this
route -p add 192.168.10.0 mask 255.255.255.0 192.168.10.101
To dleete the incorrect one type
 route delete 192.168.10.0 mask 255.255.255.0
I think that Lee is wrong with that comment regarding the wrong route - the gateway on the static route corresponds to the one used for the second default gateway. Presuming that is correct, the static route must be as well
 
New IP config attached below... Default Gateway removed for wireless adaptor.
Ethernet adapter Local Area Connection:
 
        Connection-specific DNS Suffix  . : domain1.com
        Description . . . . . . . . . . . : Intel(R) 82566DM Gigabit Network Con
nection
        Physical Address. . . . . . . . . : 00-1C-C4-9B-5F-77
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 172.16.103.59
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 172.16.103.254
        DHCP Server . . . . . . . . . . . : 172.16.2.1
        DNS Servers . . . . . . . . . . . : 172.16.2.11
                                            172.17.2.1
                                            10.0.1.90
        Lease Obtained. . . . . . . . . . : 05 August 2008 09:47:02
        Lease Expires . . . . . . . . . . : 13 August 2008 09:47:02
 
Ethernet adapter Wireless Network Connection:
 
        Connection-specific DNS Suffix  . : domain2.com
        Description . . . . . . . . . . . : D-Link AirPlus G DWL-G122 Wireless U
SB Adapter(rev.C)
        Physical Address. . . . . . . . . : 00-17-9A-B9-3A-29
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.10.101
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :
        DNS Servers . . . . . . . . . . . : 192.168.10.1

Open in new window

and your route print now looks like?
Route print hasn't changed.
But it's still specifying the gateway 192.168.10.1 if your route print hasn't changed which would tend to suggest it's not working as it should?
try pinging a web site like
ping www.experts-exchange.com
See if it resolves the name and pings the address - this will check you DNS and route config. If it comes back with the IP address (DNS lookup working) tracert to the IP address and see which route it takes.
tracert 64.156.132.140
 
TraceRt as requested... Seems to make it to the internet proxy, and then stops.

C:\Documents and Settings\adam.scott>tracert 64.156.132.140
Tracing route to www-level3.experts-exchange.com [64.156.132.140]
over a maximum of 30 hops:
 
  1     1 ms     1 ms     1 ms  172.16.103.252
  2     1 ms     1 ms     1 ms  192.168.6.6
  3    12 ms     1 ms     1 ms  192.168.5.13
  4     1 ms    <1 ms    <1 ms  nn03a17.domain1.com [10.0.1.1]
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.

Open in new window

Well it proves your routing is correct! It's usual to not be able to get past the proxy with ICMP as it's common to block it.
Your issue is now not with routing - that looks like it is fixed. I would check to see if your proxy allows connection from your IP address / User ID now.
Hi your route has got an incorrect entry ..

Do you have a network adapter with the address 192.168.10.1 ? If not then you have a typo on your routes. Please delete the persistant router because you are confusing your computer since it is seeing two routes to the 192.168.10.0 subnet .. one of which is incorrect.

Are you able to ping www.yahoo.com ? If it resolves to an ip but cannot ping then its an issue with the gateway else dns issue (could be also due to not being able to reach the dns server).

Cheers
I would agree somewhat with that, but one question - why would the proxy not allow this connection through if it's routing through the correct NIC? If I disable the other NIC, the connection to the 'net is made no problems...
Do you have a firewall/proxy/filtering device/software on your gateway in domain1 that will be filtering your web access?
Yes we do, based on browser requests.
hi

your route print shows 5 interfaces

0x01 MS TCP Loopback interface
0x2 ...00 1c c4 9b 5f 77 ...... Intel(R) 82566DM Gigabit Network Connection - Pa
cket Scheduler Miniport
0x3 ...44 45 53 54 42 00 ...... Nortel IPSECSHM Adapter - Packet Scheduler Minip
ort
0x4 ...00 ff e6 03 65 59 ...... TAP-Win32 Adapter V8 - Packet Scheduler Miniport
 
0x50006 ...00 17 9a b9 3a 29 ...... D-Link AirPlus G DWL-G122 Wireless USB Adapt
er(rev.C) - Packet Scheduler Miniport

Whats the nortel and the TAP-Win32 Adapter V8 for? Are they disabled?

Both the Nortel and TAP-Win32 adaptors are virtual adaptors utilised with our VPN software. These are disabled when not in use. :-)
These two lines:
         0.0.0.0          0.0.0.0   172.16.103.254   172.16.103.59       20
          0.0.0.0          0.0.0.0     192.168.10.1  192.168.10.101       100
from your route print mean that you still have two default gateways. Have you rebooted since removing the second default and adding the static route?
hi

what nic are you talking about in your post above (listed below). Is it the 192.168.10.x or the 172 ?

I would agree somewhat with that, but one question - why would the proxy not allow this connection through if it's routing through the correct NIC? If I disable the other NIC, the connection to the 'net is made no problems...
The 192.168.10.x (No Gateway) adaptor is connected the the LAN-Only resources, and when this is enabled, it cuts the link to the internet. The 172.16.103.x (Default Gateway) adaptor is linked to the proxy then onwards to the internet. If I disable the 192 adaptor, the internet is restored, but this shouldn't affect things as theoretically the information is getting routed correctly regardless of whether it's enabled or disabled?
ok this is what i am thinking ... maybe your proxy server is unreachable when you have your 192.168.10.x nic enabled .. you can still get to the internet but not to the proxy and thus not to any websites.. which explains why you can traceroute. Whats the Ip address of your proxy? If you are using internet explorer then maybe it is forced through a group policy .. check in tools -> Internet Options -> Connections -> Lan Settings -> Proxy Server

Also your persistant router is not correct. Have you removed the following entry?

 192.168.10.0    255.255.255.0     192.168.10.1       1

I am thinking maybe the proxy is also on a 192.168.10.x subnet but on the other side .. that is on domainA side. So when you disable your domainB NIC, it sends everything out to the gateway when the proxy is being queried  .. when you have it enabled then it tries searching for the proxy on domainB because domainB is the place where all machines with 192.168.10.x live.




Just performed a reboot, and attached the outputs below. The multiple gateways have disappeared, but the issue posted just above is still affecting access...
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0   172.16.103.254   172.16.103.59       1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
     172.16.103.0    255.255.255.0    172.16.103.59   172.16.103.59       1
    172.16.103.59  255.255.255.255        127.0.0.1       127.0.0.1       1
   172.16.255.255  255.255.255.255    172.16.103.59   172.16.103.59       1
     192.168.10.0    255.255.255.0   192.168.10.101  192.168.10.101       100
     192.168.10.0    255.255.255.0     192.168.10.1  192.168.10.101       1
   192.168.10.101  255.255.255.255        127.0.0.1       127.0.0.1       100
   192.168.10.255  255.255.255.255   192.168.10.101  192.168.10.101       100
        224.0.0.0        240.0.0.0    172.16.103.59   172.16.103.59       1
        224.0.0.0        240.0.0.0   192.168.10.101  192.168.10.101       100
  255.255.255.255  255.255.255.255    172.16.103.59               4       1
  255.255.255.255  255.255.255.255    172.16.103.59               3       1
  255.255.255.255  255.255.255.255    172.16.103.59   172.16.103.59       1
  255.255.255.255  255.255.255.255   192.168.10.101  192.168.10.101       1
Default Gateway:    172.16.103.254
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
     192.168.10.0    255.255.255.0     192.168.10.1       1
 
U:\User Data Store PH\Adam.Scott>tracert www.google.co.uk
 
Tracing route to www.l.google.com [216.239.59.147]
over a maximum of 30 hops:
 
  1     1 ms     1 ms     1 ms  172.16.103.252
  2    29 ms    13 ms    10 ms  192.168.6.6
  3     1 ms     1 ms     2 ms  192.168.5.13
  4     1 ms    <1 ms    <1 ms  nn03a17.pitguk.com [10.0.1.1]
  5     *        *        *     Request timed out.
 
Ethernet adapter Local Area Connection:
 
        Connection-specific DNS Suffix  . : domain1.com
        Description . . . . . . . . . . . : Intel(R) 82566DM Gigabit Network Con
nection
        Physical Address. . . . . . . . . : 00-1C-C4-9B-5F-77
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 172.16.103.59
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 172.16.103.254
        DHCP Server . . . . . . . . . . . : 172.16.2.1
        DNS Servers . . . . . . . . . . . : 172.16.2.11
                                            172.17.2.1
                                            10.0.1.90
        Lease Obtained. . . . . . . . . . : 05 August 2008 10:59:29
        Lease Expires . . . . . . . . . . : 13 August 2008 10:59:29
 
Ethernet adapter Wireless Network Connection:
 
        Connection-specific DNS Suffix  . : domain2.com
        Description . . . . . . . . . . . : D-Link AirPlus G DWL-G122 Wireless U
SB Adapter(rev.C)
        Physical Address. . . . . . . . . : 00-17-9A-B9-3A-29
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.10.101
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :
        DNS Servers . . . . . . . . . . . : 192.168.10.1

Open in new window

delete the persistant route.... please :)
I'd second that request :o)
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
As requested, no change.
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0   172.16.103.254   172.16.103.59       1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
     172.16.103.0    255.255.255.0    172.16.103.59   172.16.103.59       1
    172.16.103.59  255.255.255.255        127.0.0.1       127.0.0.1       1
   172.16.255.255  255.255.255.255    172.16.103.59   172.16.103.59       1
     192.168.10.0    255.255.255.0   192.168.10.101  192.168.10.101       100
   192.168.10.101  255.255.255.255        127.0.0.1       127.0.0.1       100
   192.168.10.255  255.255.255.255   192.168.10.101  192.168.10.101       100
        224.0.0.0        240.0.0.0    172.16.103.59   172.16.103.59       1
        224.0.0.0        240.0.0.0   192.168.10.101  192.168.10.101       100
  255.255.255.255  255.255.255.255    172.16.103.59               4       1
  255.255.255.255  255.255.255.255    172.16.103.59               3       1
  255.255.255.255  255.255.255.255    172.16.103.59   172.16.103.59       1
  255.255.255.255  255.255.255.255   192.168.10.101  192.168.10.101       1
Default Gateway:    172.16.103.254
===========================================================================
Persistent Routes:
  None

Open in new window

did you have a look at my post above? about suspicion that your proxy server is on the same subnet as 192.168.10.x ?
I wonder if there is a route on the Proxy server that sends traffic to the 192,168.10.xxx subnet rather than the 172.16.103.xxx one. This would mean that traffic is looping rather than passing back and forth
knock knock .. anyone home?
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial