Setting a fixed IP loses internet connection

[mercyh]

Paul asks a very good question (one of the first that should have been asked)

Do you have connection to your network with the fixed IP and are only not able to browse the internet, or do you have no network connection at all when you assign the IP?

[sjors]

Quite so, will try that next week, finding fixed and dhcp-ip through the network.
And yes, it's only the internet that can't be reached with a fixed IP!

Keep them suggestions coming, tnx.

Sjors

[mercyh]

And yes, it's only the internet that can't be reached with a fixed IP!

This eliminates a problem with duplicate IP or improper subnet mask. We are left with one of the following:

1. Improper gateway IP address> This has been checked and double checked

2. DNS setting problem> This can be tested by trying a PING WWW.GOOGLE.COM at the command prompt which I think will fail. If this fails, go to a working machine on your network and issue the same command. Write down the IP address of www.google.com that it shows. Go back to the non working machine and attempt to ping that IP address directly. If this works I would test with a DNS server entry from opendns (www.opendns.com). (Their dns server IP's are in the lower right hand side of the page underneath the red OpenDNS logo).

3. Firewall rules that do not allow that address (or a range of addresses that include that address) to access the web. > To test this I would check that the highest numbered address in your DHCP range is free. I would then TEMPORARLY assign this machine that top address and see if it works. ( If your dhcp range is from xxx.xxx.xxx.100 - xxx.xxx.xxx.199, and xxx.xxx.xxx.199 is free, assign xxx.xxx.xxx.199 to this machine and see if it work.)

4. Something on your network that is not "standard" such as an internal proxy server, untangle filter, or smart switches and vlans.

[BitDreamer]

Here is what I would try.

Do these steps from a good PC and from the problem PC
First - ping the router > ping 192.168.1.1
Then - ping a website's IP address such as google > ping 209.85.225.103
Then - ping the website > ping www.google.com

If you can't ping the router, the network connection is not working at all.
If you can't ping Google's IP address, you have a router problem.
If you can't ping Google.com, you have a DNS problem.

[mercyh]

Hang on to your hat. Your thread got featured in the Windows Secrets newsletter. You will soon have more suggestions then you could try in a week....

[keysailor]

I have found that repeatedly changing networking setups can 'gum up' the system. After changing settings, try first disabling, and then re-enabling the network adapter. Be sure to wait a bit for it to complete, as the visual cues aren't that great. You can also try the repair option.

If that doesn't work, try clearing the arpcache. From the DOS prompt, type "netsh interface ip delete arpcache" (no quotes)

If that errors, out, check if this system has MS' Routing and Remote Access turned on. Turn this off, then clear the arpcache. If you need Routing and Remote Access, turn it back on.

Turn off Routing and Remote Services from the Admin console: under Administrative Tools, Computer Management, Services

If you don't need that service, leave it off. You say you want the static IP for remote access, so you might need the service. You don't specify the OS, so if it's WinXPPro, SP3 disables it by default.

[Eric Legge]

I would try using the free trial of Network Magic. - http://www.purenetworks.com/download/

If it works, but you have to use it every time, your wireless adapter has probably developed an incurable fault.

In any case, if you have another wireless adpater, try using it.

[sjors]

Ha, still thinking with me, tnx.
It's not wireless, it's ethernet.
Nevertheless, I had a chance today to look at the pc.
There seems to be working some special programm that is communicating with specific drivers to measure certain things like food-quantity and watertemperature.
It's a fish breeding farm (for those interested: www.seafarm.nl).
It conflicts with internet-connections whithin a couple of hours when automatic IP etc is configured.
So that's a nono for this pc, at least untill I have spoken to the ones responsible for this programm.
That means this topic will close for the moment, anyway from my part.
When I have other news I will let you all know on this forum.
Thanks again for your concern.

Regards,
Sjors

[Paul T]

Thanks for the feedback.

cheers, Paul

[dmoisan]

Also don't forget to flush the DNS cache. From a command prompt:

ipconfig /flushdns

You will use the ipconfig commands most often in troubleshooting, particularly ipconfig /all. I don't use netsh unless something is very messed up.

[sjors]

Hi David,
Just this morning I had a reaction of the Norwegian installer of this pc. He writes:
The pc was originally configured with a fixed IP, due to the wireless remote control unit.
This type of equipment responds very badly to dynamic/DHCP enabled networks.

That declares a lot, don't you people think?

Sjors

[Paul T]

Is there a remote device the PC connects to?
Does their software and send directly from the NIC, rather than via Windows?
Nothing worse than badly behaved programs.

cheers, Paul

[Azalyn]

Hey sjors,

Try this:

IP 192.168.1.20
Submask 255.255.255.0
Gateway 192.168.1.1
DNS1 <IP address> ..can check at myipaddress.com or your router's main page
DNS2 8.8.4.4