No Internet with Static IP

[wevy69]

Hi everyone. Hope you can help. I ahve a number of windows 7 pro 64 bit computers. I have configured them with static IP addresses. None of them can get internet. I can ping other machines on the network and vice versa but cannot ping the router. If I configure an xp machine with these details then internet works fine. It Appears that the windows 7 machine only wants to work with dhcp. I have another domain running dhcp with a different set of ip credentials. Any help would be much apreciated as I have tried lots of solutions like disabling IPv6, removing and reinstalling adapter flushing dns and so forth.

 

[UsernameIssues]

Welcome to the Seven Forums.

Please post the IPCONFIG info for one of the W7 computers while it is assigned a IP via DHCP.

Then post the IPCONFIG info for the same W7 computer while it is assigned a static IP.

 

[archer]

Hi wevy69, Welcome to Sevenforums.

If you're setting up a static address you also have to manually configure your Gateway and DNS server(s). Try plugging in the address of your router for these.

Make sure your PC and router are on the same subnet as well.

For example, your router has an address of 192.168.1.1 with a netmask of 255.255.255.0 and your PC has an address of 192.168.2.1 also with a netmask of 255.255.255.0. This puts your PC on a different subnet than your router and they won't be able to communicate regardless of your Gateway and DNS settings. In this case you would either change the netmask of both to include each other's subnets (255.255.0.0 for instance) or give the PC an address of 192.168.1.xxx to match the router's subnet.

enable NetBios

 

[wevy69]

Thanks for the replys. Information is as follows.

Static IP Details

C:\>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Officehp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
Physical Address. . . . . . . . . : 78-E3-B5-C5-80-76
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::9c25:f97d:1176:3784%13(Preferred)
IPv4 Address. . . . . . . . . . . : 172.16.16.158(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.128
Default Gateway . . . . . . . . . : 172.16.16.129
DHCPv6 IAID . . . . . . . . . . . : 276358069
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-B0-C3-5A-78-E3-B5-C5-80-76
DNS Servers . . . . . . . . . . . : 172.16.16.129
172.16.16.130
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{724828DB-9D3C-4450-A14E-00E1E9925192}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 12:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\>

DHCP IP Details

C:\>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Officehp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dspdom.northants.sch.uk
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : dspdom.northants.sch.uk
Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
Physical Address. . . . . . . . . : 78-E3-B5-C5-80-76
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.12.66.160(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Lease Obtained. . . . . . . . . . : 20 November 2013 12:31:41
Lease Expires . . . . . . . . . . : 28 November 2013 12:31:41
Default Gateway . . . . . . . . . : 10.12.66.1
DHCP Server . . . . . . . . . . . : 10.12.66.3
DNS Servers . . . . . . . . . . . : 10.12.66.3
10.12.66.1
Primary WINS Server . . . . . . . : 10.12.66.3
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.dspdom.northants.sch.uk:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : dspdom.northants.sch.uk
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 12:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\>

As mentioned i have also used the static details on an xp machine and this works fine. These win 7 machines are to replace all of the xp machines that are using static IP's at the moment. The addresses I am using are not already used on the network as this has been checked.

 

[UsernameIssues]

We will have to see if other forum members see where the problem is - I don't see it.

 

[archer]

We will have to see if other forum members see where the problem is - I don't see it.

 

[Kari]

Is there a reason why you use two different reserved private IPv4 ranges, 10.12.X.X for DHCP and 172.16.X.X for static? If the router is the same with same settings on both examples, I mean if the router's IP is not changed it being 10.12.X.X while PCs are looking a default gateway at 172.16.X.X, it seems IMO logical that there's no internet connection.

 

[archer]

As already mentioned and now pointed by Kari as well, PC and router should have same DNS and subnet group for them to communicate.

 

[UsernameIssues]

I'm guessing that the router is of commercial grade. It has multiple VLANs setup.

My office uses 10... and 172... IP ranges too.

Like the OP said...
...the XP boxes work using the 172.16.... static setups
...the W7 boxes don't.

 

[Kari]

That's why I asked if there's a reason for using different IP ranges.

 

[archer]

@ OP, can you please provide us with the model and make of the router that you are using?

 

[wevy69]

Hi. There are two different domains on the same network. The router is configured for both. I have around 200+ machines on the 10. Range and use DHCP. I have around 10 machines on the 172. Range in the office with static IP's. This has been working fine for around 2 years with the draytek router we use. Problem has only surfaced now upgrading workstations to win 7. Thanks everyone for looking into this. It now has me baffled.

 

[wevy69]

The router is a Draytek vigor. Not sure of model number but will update when back on site.

 

[wevy69]

Now sorted. Thanks to everyone for looking at this. It turns out that I needed to connect a cable to ports 3 or 4 on the router for the 172. range. Ports 1 and 2 were for the 10. range. It would seem that even with a cable only plugged into port 1 XP machines on the 172. range were still able to route through port 1. Again thanks to everyone for looking. Oh and the router is a Dratek Vigor 2830 if anyone is interested or may come accross the same problem.

 

[archer]

Congrats for getting the solution. Did some reading on the issue posted in your last post.

We can achieve that leaking routes between the global routing table and the VRF (and vice-versa
because otherwise you can't obtain bi-directional connectivity) could be
achieved by appointing some static routes, ie.

ip route vrf x <dest prefix> <dest prefix mask> <next-hop> global
ip route <vrf dest prefix> <vrf dest prefix mask> <interface> <vrf next-hop>

For a more realistic scenario, to this simple configuration you need to add
some kind of redistribution and take into account NATting if using private
addresses inside the VRF

I am sure you have it but this can be handy.