Windows 7: Static IP, Router, Office Network losing Internet

In general, yes; but not entirely true.

Each computer probably has one or more apps that do not rely on DNS for connectivity... like some antivirus apps try DNS, but if that fails, they try to update via a hard coded IP addresses. The same goes for many infections. I've seen posts where people had Skype working, but no DNS for their browser.

Also, each computer should be running a DNS service that caches previously resolved IP addresses. Some of these IP addresses will stay in that cache for days. Restarting the computer clears that local DNS cache.

OK! I got rid of Static IP issue.
I will set up constant ping right now on our workstation which acts like our file server. Question - when I see that ping window got all time outs, how does that isolate what is my issue? I will deal with it then, I suppose. I am off to setting up constant Ping.

No one has questioned my router yet - I used to have and use the CIsco WRVS4400N (I would still would like to go back to this since this routher allows VPN which I will need). Ring Central recommended E1200 because of some setting/configuration. A friend of mine tells me that Cisco WRVS4400N can do the same.

So far so good... my router is steady. Google Ping has time 126ms, 146ms from time to time.

Let's assume that the day starts normally and you can get to websites.
When you cannot surf to websites, check the ping window.

If the ping window shows all timeouts, then you are most likely no longer connected to the internet. What you do at that point depends on who owns the equipment between you and the internet. If TW provided a cable modem, then call TW and see what they have to say about your repeated disconnects. See if they can "see" your cable modem online. If you own the cable modem, then it might be time to replace it.



I see no problem using that router - but TW might want it out of the picture while you are working on their cable modem disconnect issue.

Another idea is, if its possible, directly connect the connection directly to a computer. Preferably a Laptop due to portability issues. Run the ping command that UsernameIssues suggested. I suggest doing this on a day you aren't going to be using the office much.

If you keep your connection steady, and have no problems, then you know it isn't the Cable box. If you have issues then, you know it isn't the router because you're directly connected to the cable box.

If that doesn't work, I would get a Static IP address and go from there. I've personally never worked with the router you have, but most of the newer model routers I have to manually setup my DHCP, and give it the Dynamic IP. But this was before I switched to Fiber Optic connection.

Second day - other than some delay in the response time, both the constant ping to the router and google seem to be good. However, this has been the case before where it can go for weeks without issue and then one morning, internet is down.

UPDATE: I was intrigued by one of the post about changing the modem's setting (ie DNS) so I inquired with Time Warner about gaining access. They don't allow clients to access their modem but they can "bridge" it to my router to "gain full access". I fully don't understand it but I decided to let him bridge it. He couldn't do it. He wasn't able to access my router. He rebooted the modem. He had me physically go through the power cycle and was not successful. He is sending out a technician to physically look at this modem. I am thinking this might have been the culprit for internet connection issue and me having to reboot the router.

QUESTION: Bridging the modem to the router. What is this and should I do this? At the end of the day, I will be perfectly fine without bridging it as long as I don't have to keep rebooting the router from time to time - leaving me to worry when I am away from the office that my staff is without internet.

I don't know what the TW tech will be doing, so I do not know if the TW tech is using the term bridging correctly. You can look at this Bridging (networking) - Wikipedia, the free encyclopedia for more info. I'm not sure if it matters if TW bridges the modem to your router or not. I'll leave that for others in this thread to comment on.

Excluding bridging from the discussion - let me see if I can ramble on coherently about DNS settings:

The modem* gets:
an IP address from TW.
and DNS IP addresses from TW.
(A main DNS IP and one or more backup DNS IP addresses.)

For simplicity, I'll only mention one of your two routers
Your router gets:
an IP address from the modem
and one or more DNS IP addresses from the modem.

Each computer on your network gets:
an IP address from the router
and one or more DNS IP addresses from the router.

Normally, you can manually change the DNS IP addresses for the modem and/or the router and/or each computer.



The router has two main IP addresses:
The one that faces the internet (or that faces the modem)
and one that faces your network (maybe 192.168.0.1).

The router might (probably will?) hand out its 192.168.0.1 IP address as the DNS IP address to each computer on your network.

When a computer wants to surf to sevenforums.com
The computer asks the router,
"What is the IP address for sevenforums.com?"
The router asks the modem,
"What is the IP address for sevenforums.com?"
The modem asks TW's DNS server,
"What is the IP address for sevenforums.com?"

TW's DNS servers gives the IP address for sevenforums.com to the modem. The modem passes info to the router. The router passes that info to the computer. Wasn't that fun?

If you were allowed to change the DNS IP addresses on the modem, nothing much would change in that chain of events except where the IP address for sevenforums.com came from. If you did manage to point the modem to OpenDNS's DNS servers. Then the IP address for sevenforums.com would come from their DNS servers.

You can tell the router to skip asking the modem and go straight to OpenDNS for all DNS queries.

You can manually tell each computer to skip both the router and the modem and go straight to OpenDNS for all DNS queries.

Or - you can tell the router to automatically tell each computer to skip both the router and the modem and go straight to OpenDNS for all DNS queries.



*definitions are a bit of a problem here. Many of TW's "modems" are also routers and wireless access points. I don't know the make/model of the modem involved, but looking at this page, I see lots of modem/router combos. Some of TW's simplest "modems" with only one Ethernet port also perform Network Address Translations, so I would call them a modem/router combo.


Caveats to the info above:
1) I think that is how stuff works - I could be wrong.
Corrections and/or criticisms are welcome.

2) For simplicity, several other configurations were not mentioned.

3) Even if the info above is correct, TW (and other ISPs) used to ignore your settings and force DNS traffic to go to its DNS servers. I do not think that any US based ISP still does that... but you can see this post for links to discussions about that. I'm just not sure that I would call that DNS hijacking.

Maybe it is just me, but I find it hard to keep up with your dozen or so active threads... so I did not comment on this. I figured that this was being handled in another thread.

So - sure, go back to using the Cisco WRVS4400N any time that you want. Your disconnects are not related to your E1200 or your WRVS4400N

Yep, that would have been my guess as to where the problem is since you have already swapped out a router on your side of the modem.