D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DGL-4500 => Topic started by: Mogorain on October 02, 2010, 07:45:02 PM
-
Hello. I've had some issues before, so I figured I'd come back and try again. Trikein! Furry! Heeelp!
Here's the thing: I have a problem with the router intermittently losing internet access. It will have no problems with pinging local IPs, but when I lose internet Windows says there's a DNS problem and the router cannot ping the DNS I have it set to.
Some background info: I called Time Warner Cable and had them help me set it up. I removed the router, got the DNS servers listed for Time Warner (they confirmed those were it), and set those up in the router's options for Primary and Secondary. I've also tried using the Advanced DNS though, and it loses those DNS servers as well -- intermittently. Here's the setup right now:
Connection Type: DHCP Client
QoS Engine : Active
Cable Status : Connected
DNS Status : Online
Network Status : Established
Connection Up Time : 0 Day 0 Hour 17 Min 44 Sec
Authentication & Security :
IP Address : 76.174.198.215
Subnet Mask : 255.255.240.0
Default Gateway : 76.174.192.1
Primary DNS Server : 209.18.47.61
Secondary DNS Server : 209.18.47.62
Advanced DNS : Disabled
Another issue I'm having is the wireless laptop is suddenly having some serious issues staying connected, even if my desktop is fine. Another example, not sure if the two problems are related...
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
No response from host, retrying...
No response from host, retrying...
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
No response from host, retrying...
No response from host, retrying...
Response from 192.168.0.197 received in 3 milliseconds. TTL = 128
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
Response from 192.168.0.197 received in 3 milliseconds. TTL = 128
No response from host, retrying...
No response from host, retrying...
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
No response from host, retrying...
No response from host, retrying...
Response from 192.168.0.197 received in 81 milliseconds. TTL = 128
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
No response from host, retrying...
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
No response from host, retrying...
User stopped
Pings sent: 27
Pings received: 17
Pings lost: 10 (37% loss)
Shortest ping time (in milliseconds): 1
Longest ping time (in milliseconds): 81
Average ping time (in milliseconds): 6
Also not sure what caused the bolded anomaly of 80ms difference. Insight? Derision?
-
Well I will need to research your previous post to freshen up a bit, but yea..Welcome back :-)
Ok, well a DNS issue atleast is a defined problem, so thats good. After reading what you said, here are my questions:
1. "but when I lose internet Windows says there's a DNS problem and the router cannot ping the DNS I have it set to." Could you provide the exact error verbatim?
2. "Another example, not sure if the two problems are related..." What is that ping from and to? Router to laptop?
3. "Also not sure what caused the bolded anomaly of 80ms difference. "A latency spike can be caused by several things. Do you just see this from router to laptop? What about wired connections? It could be how the router is prioritizing DNS traffic. I found a bug with DNS relay a while ago with something similar. I think DNS goes from TCP to UDP when the response is over 512b. I don't want to start giving randoms things to try though without know the info above, but yea, I have some idea's
-
1. "There may be a problem with your Domain Name Server (DNS) configuration. Windows failed to find the well known host "www.microsoft.com" using DNS. The server may be down." When I see that, I cannot get the router to ping the DNS address, but it can still ping my wired and wireless connection.
2 and 3. The ping I displayed was from the router to the laptop (wireless). It does not display the spikes toward the LAN, nor does it have ANY failed attempts.
-
Part of me wants to suggest turning off DNS relay, since if thats failing, that might explain why you lose connection to your DNS servers. However, DNS traffic is usually TCP over port 53, while a ping is ICMP traffic. I could see DNS relay blocking or delaying TCP, but ICMP? Then again, theres another bug which effects domain look up on tracert when DNS relay is enabled so...they could be related. I just don't know how. Oooh, this is a good one. I am going to have to chew on this one. Good info though. Maybe some sleep will help. I will look at it tommorow morning.
-
Wonders when tomorrow morning comes... :p
-
Oh, and I've also noticed that sometimes my computer displays that I do have a full connection. It clearly states "Local and Internet"... however it doesn't actually have internet. I can try to hop on a website and it'll time out. And I can go into the 4500's Tools and ping anything outside without getting a response. But the router can still ping the IPs of the local comps.
-
Sorry, I am actually doing the testing for a piece of Dlink hardware. Cant say much more but it has me very busy. In a good way :-)
Anyway my thoughts:
1. Local is when it connects to a DHCP server, and Internet is when it has a DNS suffix. So that might mean your connecting to DNS, but you can not query it.
2. Next time it happens try to
A. Ping a known IP (IE 173.194.34.104) from the router
B. Ping that same IP from your computer.
C. Ping your DNS from your router
D. Ping that same DNS from your computer.
3. I could see using static DNS causing problems, since technically they could change at any time. Granted, it usually doesn't happen all that often. But if your ISP is doing who knows what, it could cause issues like that. However, if your having the same problems with AdvancedDNS, I doabt its that.
4. When I did a google search, it seems thats a problem alot of people get when their winsock needs resetting, or dns cache needs to be flushed or some other problem inside your computer. But before we do a 180, and go down that road, are you having the problem with all computers, or just that one?
-
Cool beans on the new hardware! Hope it comes out well!
Ok, the internet loss is happening with both computers, though more frequently when both computers are online at the same time. For instance, I can play World of Warcraft or StarCraft 2 alone and only disconnect a few times, but if my girlfriend logs in as well we start losing internet more frequently.
The other portion of my message, where I ping the computers' IPs, only has an issue with the wireless connection. Pinging my wired connection shows no issues, but pinging the wireless has those anomalies. Here's another one I did right now for it.
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128 (5 times, then it starts...)
No response from host, retrying...
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
No response from host, retrying...
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
Response from 192.168.0.197 received in 3 milliseconds. TTL = 128
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
No response from host, retrying...
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
No response from host, retrying...
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
Response from 192.168.0.197 received in 365 milliseconds. TTL = 128
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
Response from 192.168.0.197 received in 3 milliseconds. TTL = 128
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
Response from 192.168.0.197 received in 1197 milliseconds. TTL = 128
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
Response from 192.168.0.197 received in 1 milliseconds. TTL = 128
No response from host, retrying...
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
Response from 192.168.0.197 received in 2 milliseconds. TTL = 128
User stopped
Pings sent: 33
Pings received: 28
Pings lost: 5 (15% loss)
Shortest ping time (in milliseconds): 1
Longest ping time (in milliseconds): 1197
Average ping time (in milliseconds): 57
I should point out that the wireless is in the same room as the router, as is my desktop. We about 4 feet from each other, the router mounted up on the wall.
-
What FW version is loaded on the 4500?
-
v1.22NA
-
Do you have this problem if you save off your current configuration to file and do a factory reset? Your on good FW. I don't see a need for upgrading FW right now.
-
Ok, sorry for the delay -- I did a factory reset and then reloaded my configuration. Gave it a few days, and I haven't seen us lose internet and end up "Local Only", but I'm right back to us disconnecting incessantly on World of Warcraft (see http://forums.dlink.com/index.php?topic=14325.0 (http://forums.dlink.com/index.php?topic=14325.0) for reference). Grrr
-
Sounds good on the Internet disconnection. Hope it stays working. I'm wondering if there is a possible setup configuration issue having to do with the WoW gaming though. Have you gone thru all the settings and made sure they are set up correctly? I presume you have been using Gaming and or Gamefuel? Wheres Tricky when you need him. ::)
-
Actually, no I haven't been using Gamefuel or Gaming. The problem we ran into with that is it couldn't handle having the same info going to two separate computers at the same time (like when my girlfriend and I were in a raid instance together) and we'd get repeatedly dropped.
-
What happens if you put both PCs on Game fuel and put one of the PCs on Gaming? Gamefuel should be able to hand both PCs however you can only use one PC in gaming...
-
Reading what Trike said on another post, what seems to be happening is a little like his analogy of trying to forward a house line to two cell phones at the same time. :-/ I can't get two static IPs, though, 'cause Time Warner charges for them.
Btw, I came across this today shortly before I ended up Disconnected from the internet with no access again.
[INFO] Wed Oct 13 22:19:17 2010 Blocked incoming TCP packet from 12.129.254.188:4000 to 76.xx.xx.215:52083 as PSH:ACK received but there is no active connection
[INFO] Wed Oct 13 22:17:36 2010 Blocked incoming TCP packet from 99.34.169.134:51294 to 76.xx.xx.215:3724 as RST:ACK received but there is no active connection
[INFO] Wed Oct 13 22:16:58 2010 Blocked incoming TCP packet from 76.168.251.107:3724 to 76.xx.xx.215:51957 as RST received but there is no active connection
[INFO] Wed Oct 13 22:16:48 2010 Blocked incoming TCP packet from 24.60.53.109:54649 to 76.xx.xx.215:3724 as RST received but there is no active connection
[INFO] Wed Oct 13 22:16:11 2010 Blocked incoming TCP packet from 86.176.144.16:59607 to 76.xx.xx.215:3724 as RST:ACK received but there is no active connection
[INFO] Wed Oct 13 22:14:34 2010 Blocked incoming TCP packet from 70.225.132.190:58327 to 76.xx.xx.215:3724 as RST:ACK received but there is no active connection
[INFO] Wed Oct 13 22:14:06 2010 Blocked incoming TCP packet from 68.202.179.164:58694 to 76.xx.xx.215:3724 as RST received but there is no active connection
[INFO] Wed Oct 13 22:11:34 2010 Blocked incoming TCP packet from 71.1.99.114:24202 to 76.xx.xx.215:3724 as RST received but there is no active connection
[INFO] Wed Oct 13 22:08:48 2010 Blocked incoming TCP packet from 209.18.36.34:80 to 76.xx.xx.215:51881 as FIN:ACK received but there is no active connection
[INFO] Wed Oct 13 22:08:46 2010 Above message repeated 2 times
[INFO] Wed Oct 13 22:08:33 2010 Blocked incoming UDP packet from 96.56.197.3:17941 to 76.xx.xx.215:54451
[INFO] Wed Oct 13 22:08:27 2010 Above message repeated 2 times
[INFO] Wed Oct 13 22:08:21 2010 Blocked incoming ICMP error message (ICMP type 3) from 24.16.84.120 to 76.xx.xx.215 as there is no TCP connection active between 76.xx.xx.215:52061 and 192.168.1.133:3724 <== That address is not part of my router network
[INFO] Wed Oct 13 22:08:12 2010 Above message repeated 2 times
And I know that the 3724 port that is prevalent on a lot of those is a heavily used port for WoW.
-
Interesting, what is your DHCP address range? Default is 192.168.0.100 to 192.168.0.199. I assume your router is secure with WPA atleast yes?
-
Yeah, the range is what the default is, and the router is secure with WPA. What does it mean when it gives that message?
Also, for further information about what I've been doing total: Aside from hitting a dead-end with Time Warner about securing two IP addresses (extra cost), I've begun suffering from the random Disconnections from the internet again -- which is the part I'm trying to solve.
- It's happening whether the wireless laptop is online or not -- or for that matter even turned ON -- so it doesn't appear to be related to the routing of two computers.
- It's happening whether or not I'm in World of Warcraft, but it's most annoying during those times simply because of the nature of the game. Not being able to click the next page in a web article isn't as frustrating as having to log back in and resurrect because I disconnected in the middle of combat or while tanking a raid. It also appears to happen more often while in-game.
- It lasts anywhere from two to about ten minutes at a time. Windows usually states there is a problem with the DNS since it "cannot connect to Microsoft's well-known..." etc.
- A factory reset doesn't solve it.
*Begins beating head on keyboard*
-
Ok, so I'm now seeing these ICMP Errors quite frequently, but I never saw them before. :(
-
There is incoming ICMP traffic from 24.16.84.120. That IP is in Comcasts network in WA falls behind a firewall someplace in Seatle. Its being directed toward your PC's private IP on port 52061. Any port from 49152 to 6553 is a private IP that can only be used locally. Think of them as the 192's of ports. The router (the owner of the 76.xx.xx.215 IP) is recieving that traffic and trying to router it a IP outside the range of your DHCP server on port 3724. Now 3724 is a public port used by WoW. So thats a clue.
Not ICMP traffic is misunderstood alot, because its a jack of all trades. I won't even go into the TCP vs UDP thing, but it used for different things. Port scans, latency tests, route tracing, route finding, etc. The way a traceroute works for instance is your computer sends a packet of ICMP traffic of a certian size marked with a tag that tells it how long to stay around.This is known as the Time to Live (TTL) The packet bounces from your computer, to the router, to the modem, to the ISP, and so on. Each time it gets to one of those places, that device takes the packet, decreases the TTL by 1, replicates it, and sends one to it's next desitionation, and sends the other back to the original sender(your PC). So after your computer sends out a ICMP packet, it waits to hear the returning packets, and like dropping a rock down a well and listening for the splash, it can determine where each connection is, how long it takes to get there, and so on. Its more complicated then that actually, but thats a simplified version.
So why did I say that? I think the returning ICMP packets are being misrouted by your router to a DHCP range that is incorrect. If I had to guess, you were writing a rule and did 192.168.1.133 instead of 192.168.0.133. No why is that important? I think the WoW game client is the one sending those ICMP packets, and its the return packets which are being misrouted. WoW needs those packets to use UPnP, to find servers, and so on. Is that your only problem? Probably not. It doesn't explain all your symtoms. But I think it MAY define that odd log error.
-
Wait..I just realized your on Time warner..a WoW server wouldnt be on a residential ISP server. And you wouldnt have any reason to be on a Comcast Server. So now I am back to being stumped. Does that 24.16.84.120 mean anything to you?
-
Hmm... new oddity happened. Girlfriend and I were online, on WoW -- setting EVERYTHING back up since they completely changed the friggin' game, but that's a different story -- for quite a while before we were disconnected. Total loss of internet again, and the log shows:
[INFO] Sat Oct 16 22:27:24 2010 Blocked incoming TCP packet from 12.129.254.187:6112 to 76.***.***.215:52511 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat Oct 16 22:27:24 2010 Blocked incoming TCP packet from 12.129.254.187:6112 to 76.***.***.215:52511 as ACK received but there is no active connection
[INFO] Sat Oct 16 22:27:24 2010 Above message repeated 3 times
[INFO] Sat Oct 16 22:27:24 2010 WAN interface speed measurement completed. Upstream speed is 1477 kbps
[INFO] Sat Oct 16 22:26:56 2010 Estimating speed of WAN interface
[INFO] Sat Oct 16 22:26:54 2010 Obtained IP Address using DHCP. IP address is 76.***.***.215
[INFO] Sat Oct 16 22:26:53 2010 Lost lease on IP Address
[INFO] Sat Oct 16 22:26:51 2010 WAN interface speed measurement aborted as they did not converge
[INFO] Sat Oct 16 22:26:17 2010 Estimating speed of WAN interface
[INFO] Sat Oct 16 22:26:16 2010 Obtained IP Address using DHCP. IP address is 192.168.100.10
[INFO] Sat Oct 16 22:26:14 2010 Bringing up WAN using DHCP
[INFO] Sat Oct 16 22:26:14 2010 WAN interface cable has been connected
[INFO] Sat Oct 16 22:26:12 2010 WAN interface cable has been disconnected
What the heck caused THAT one? No cables were touched in any way, and they are secure. I'm cornfuzzled. Also, that IP you mentioned means nothing to me -- though I see it's Comcast and from Washington. :-/
-
Well its registering the WAN port as disco then reco. To me that means
1. Your modem is resettin(Power cycling, T3, T4, etc)
2. Your ethernet is going
3. Issue with ethernet port on modem
4. Issue with WAN port on router
So....
1. Check modem logs for that same time
2. Try a new ethernet
3. Bypass the router and see if every happens.
4. If the answer: No, tried and No, then it could be the WAN port on the router
I cant think of anything else. You may have other issues, but thats the only thing I can think of that would cause a WAN interface has been disco. I feel as if your going to find T3 on the modem logs.
Last what changes were made in Wow? Maybe not relevant here, but for be handy to know for professional reasons.
-
How do you check the modem's logs? I'm a bit (lots) of a newb there. *Nevermind, I figured it out* One thing I just thought of, when a patch comes out WoW uses a lot of peer-to-peer uploading to speed up the patch process. Could WoW be attempting to get info from my comp for someone else downloading the patch, and my router's getting confused somehow.
I haven't set up any rules for the router, so there's no rules that could have mixed a 0 and 1 in the IP address range. :(
WoW is gearing up for the release of the next expansion, Cataclysm. As a result, they've completely overhauled the game systems, including all spells/abilities, coefficients of said abilities, and such. So we're having to reset our macros, action bars, etc. Nothing spectacular. :-/
-
Ok..well here is a question. Can you ping that 192 IP? Maybe its a subnet of your modem? Or a printer on your network? I agree its probably something to do with the P2P of the patch, but wouldnt that mean it would only happen when your running the game client? (And looks like the forum say they removed the option to turn it off?) Or does WoW install a stand alone silent (not in your task bar) client?
So the question are
1. Does the 192 issue have anything to do with your loss of connection?
A. Do you loose connection around the time those issues appear in the log?
B. Do those issues occur ever when not using WoW?
C. Can you ping the 192 IP?
2. What is causing the "WAN interface cable has been disconnected" error?
A. What does it say in the modem logs around the same time the router logs time stamp it?
B. How often do you see it? If once a day, could you bypass the router and go direct to the modem and play WoW heavily and see if you have issues?
C. Do you ever notice any change on the modem's lights?
-
Ok... so update:
According to Blizzard's forums, some people have experienced random disconnections with Checksum Offload selected in the Network Properties for the comp, so I disabled that like they suggested.
I've been disconnected from WoW on both computers simultaneously four times since we first logged in three hours prior. I've tried having her laptop in the DMZ of the router, but it doesn't seem to have an affect on the frequency.
1. Does the 192 issue have anything to do with your loss of connection?
A. The router doesn't show anything in the logs. My other problem is the router displays the time as Fri, Oct 22, 21:43 and the modem logs display it as Sat, Oct 23, 04:45:56. Serious time difference there, but there seems to be no way to configure the time of my modem (an old Ambit).
B. I haven't noticed the disconnections at all lately when not in WoW, and I haven't been playing other games lately to see if it's gaming related. But as of 11:20pm tonight, I did experience a random DC from WoW when my girlfriend's computer wasn't even on. Odd thing is, it displays that I have internet connection in the little icon on my taskbar, but it doesn't actually allow me to go onto any websites or log in to WoW. Windows discovers nothing wrong with the connection, but I can't view any webpages and pinging things times out. Again, nothing mentioned in router logs.
C. I cannot ping the 192.168.1.133 IP from the router right now, so it doesn't appear to be part of the network in any way. That ICMP error hasn't appeared again since that day, leaving me to assume it must've been because of the P2P uploading that Blizzard does (and yes, they disabled the ability to toggle it as of this last patch -- Grrr).
2. What is causing the "WAN interface cable has been disconnected" error?
Unable to answer this as that hasn't happened again. Must've been an anomaly for now. :-/ I feel like I'm part of a Cold Case investigation... no viable leads!!
Edit: added info
-
On an unrelated note... play ya SC2 Trike!!
-
I feel like I'm part of a Cold Case investigation... no viable leads!!
Welcome to my world. Now try handling 60 cases for 12 hours a day. ::grin:: Sometimes I have to go back and remeber the details of the issue. But yea, more data would help everyone.
1
A. Don't worry about the time difference. Its a pain, but theres nothing you can do about it. The modem doesn't have a clock, and it only gets a time by the Time of Day (TOD) signal sent by the CMTS. That can be wrong, or misread alot, since it depends on sync. Imagine a alarm clock your unplugging and replugging and resetting 20times a second, with no reference for the correct time. Gets messed up quick. Whats really odd is if it doesnt have any DOT(say after a full boot) it will default the time to the 1970's. Yea..go figure.
B. Good, were probably dealing with multiple issues. The WoW is probably just more frequent and dependent on how often you or someone plays WoW.
C. Good. So thats one door we can close.
2
I think this is the second issue your having, and I thinks it caused by the modem resetting, or atleast getting out of sync. When it does, it resets, which turns the modem off, which means no current going through the ethernet, and thus making the router think its disconnected. Could also be packet loss with intermident severe packet loss. Once it gets above 40-50%PL you start having duplexing problems which can make the router not see the connection anymore.
Going forward: Lets work on the WoW issue. Its not going to be a perfect solution, since there will be unknown elements outside what we will be working on, but without data on those elements, we have no choice. As for what to address first, lets forget the check sum and all that stuff. The WoW forums have so many theories on the best way to configure your PC for WoW its just funny. The point is, except the not being to play at the same time, WoW used to work great right? So I am going to assume its something that has changed. That would be a incorrect assumption, but its the best we have right now. So if the most change factor is the P2P protocoll, lets try to find a way to shut it off, or make it not cause the problem(make it work better). I tried to look through the WoW forums but...::gag:: Soooooo much misinformation. Do the Mods fact check any of their data? Reminds me of the "Official How to make Starcraft run better" threat on SC2 forums. It says if running hot, take the side of your case of. ::facepalm:: I will talk to some friends at work and get the real answer for you.
PS. Might take a couple of days. Its my brothers wedding. :-) Off for days. If I hear something though, I will post.
-
Tell your brother we send our congrats! And yeah, I wish the Blizzard mods prevented bad information. But they don't. It was, however, a Blizzard employee that posted it under the common issues thread as a possible solution. It didn't seem to affect anything one way or the other.
What could be causing the computer to display I still have an internet connection (i.e. not saying "Local Only"), but still being unable to get to a website or log into a game? Would that be the modem? I know that Time Warner has the Motorola modem, should I request a tradeout?
-
The reason for not seeing Local Only is that Windows and the Lan is still getting a signal and data from the router and from the WAN modem and DNS I believe. The LAN is seeing generic internet data so windows or the networking part of windows deems it a correct connection. I believe it DHCP or DNS data fails then it will post a Local Only message. You will also see this if the PC was just connected to a switch and the switch wasn't connected to any router or modem.
One thing you can do is to do a ipconfig /flushdns at a command prompt to clear out any issues there. Might even do a ipconfig /release then ipconfig /renew if your not on static IP. However this will not resolve your WoW issues.
If your ISP supports DOCSIS 3 and or the Motorola SB6120 modem I would check it out if you can. Let us know how it goes.
-
Tell your brother we send our congrats!
I will, Thanks!
What could be causing the computer to display I still have an internet connection (i.e. not saying "Local Only"), but still being unable to get to a website or log into a game? Would that be the modem? I know that Time Warner has the Motorola modem, should I request a tradeout?
Well I can say whats causing it technically. A "discovering Network" is when it cant reach or aquire the default gateway. A Local only, Limited or no connectivity, or 169, is when it can't get a IP. And when it can get a IP, DNS and DNS suffix, it will show a internet connection. However, if you obtain those things and then the connections faults, it doesn't know it cant use what it has. It only check the connection during startup of the connection. No doabt if when it happened you disabled the connection and enabled it, it wouldn't work.
As for what is "causing" that to happen, don't know yet. Could be a problem with DHCP renewing the IP lease, but if the IP is set with a DHCP reseveration, then DHCP on the LAN doesn't play a role for that computer. Could be a DHCP failure on part of the ISP on IP renewal of the router's IP, or a DHCP failure on the routers part. I think its the former, because thats probably when the modem resets and looses sync. Boots up, tries to renew or confirm the lease on the IP the modem is giving out and fails. You reboot the router, it tries again, this time with it releasing the IP so it forces a renew(as compared to a lease check) and it aquires. But all of this is quess work. It could be countless other things. Maybe the router won't release the IP when the modem asks(without a power cycle) to renew because it has active sessions via the WoW torrent that it can't close? Improper handling of PSK and ACK? I just don't know :-(
-
Ok... new information I've obtained. My router shows hardly any issues when I lose connection -- which is happening incessantly now -- but my modem does. Take a look. This is only a small part of the log. Keep in mind that this was at about 8:30pm Fri Oct 29. The time on the modem is WAY off, by about 15 hours or so. It reads from bottom to top (newest on top).
Last Time Priority Description
Sat Oct 30 04:30:47 2010 Info (7) Authorized
Sat Oct 30 04:30:46 2010 Info (7) Registration complete!
Sat Oct 30 04:30:46 2010 Info (7) We registered with a DOCSIS 1.1 config file!
Sat Oct 30 04:30:46 2010 Info (7) Received a REG-RSP message from the CMTS...
Sat Oct 30 04:30:46 2010 Info (7) Sending a REG-REQ to the CMTS...
Sat Oct 30 04:30:46 2010 Info (7) CableModem SNMP configure complete
Sat Oct 30 04:30:46 2010 Notice (6) TLV-11 - unrecognized OID
Sat Oct 30 04:30:43 2010 Info (7) IP init completed ok
Sat Oct 30 04:30:43 2010 Info (7) CableModem TFTP init ok
Sat Oct 30 04:30:40 2010 Info (7) CableModem DHCP client init ok
Sat Oct 30 04:30:40 2010 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Sat Oct 30 04:30:29 2010 Info (7) MAP w/initial maintenance region received
Sat Oct 30 04:30:04 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Oct 30 04:30:04 2010 Info (7) MAP w/initial maintenance region received
Sat Oct 30 04:30:01 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Oct 30 04:30:01 2010 Info (7) MAP w/initial maintenance region received
Sat Oct 30 04:30:01 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Oct 30 04:30:01 2010 Info (7) MAP w/initial maintenance region received
Sat Oct 30 04:30:00 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Oct 30 04:30:00 2010 Info (7) MAP w/initial maintenance region received
Sat Oct 30 04:30:00 2010 Info (7) Downstream sync ok
Sat Oct 30 04:30:00 2010 Info (7) Beginning initial ranging...
Sat Oct 30 04:30:00 2010 Info (7) downstream time sync acquired...
Sat Oct 30 04:30:00 2010 Info (7) Downstream sync ok
Sat Oct 30 04:29:59 2010 Info (7) starting ds time sync acquisition...
Sat Oct 30 04:29:59 2010 Info (7) Received a UCD message!
Sat Oct 30 04:29:57 2010 Info (7) Locked on the downstream. Waiting for UCDs...
Sat Oct 30 04:29:57 2010 Info (7) Downstream lock ok
Sat Oct 30 04:29:56 2010 Info (7) Sync Start
Sat Oct 30 04:29:55 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no
Un...
Sat Oct 30 04:29:55 2010 Reset downstream scanning state!
Sat Oct 30 04:29:23 2010 Critical (3) Started Unicast Maintenance Ranging - No response received..
This exact sequence appears in the modem every time I lose connection and have to wait for it to reacquire. While googling the "T3 Timeout" and "Broadcast Maintenance Request no response" I came across a thread with many people experiencing this. Someone who claims to have been a Senior Tech for a cable company (I think Charter, if I'm not mistaken) said that happens when there's a problem with the line somewhere. It has nothing to do with my router or modem, though the cable company will insist it does. What's your take on this, Trike and/or Furry??
-
Ok, really looks like them logs are capturing the signal loss and the modem logs are reporting whats going on afterwards. Seems like the Ranging is not getting a response for a period of time. Have you showed the ISP these logs?
First thing I would do is check the Cable going into the ISP modem and make sure it's good, no breaks or cracks in the line. Then make sure there are as few to no cable splitters as possible as these will degrade the signal the more you have on the line, if you have any.
2ndly, I would get the ISP to send out a tech guy. Most of the CS people only look and the surface and aren't much help. Demand a tech to come out and so you can show him and he can look and see and test everything.
All this that your saying is pointing to the signal on the lines and the ISP modem. Once the signal can be stabilized then all of your disconnect issues should go away. Let us know how it goes. Hope they find the issue.
-
Disconnects are happening more frequently. I do have a splitter because I have cable TV as well, and it's in the other room. There's only one cable outlet in this apartment and it's not possible to get one elsewhere without permission -- which would be a battle to obtain -- so I'm stuck with the splitter.
However, I called Time Warner and they checked. Found errors on the modem that they cannot correct remotely, so a technician will be sent out on Tuesday. They also do not believe it's the modem, but the lines outside that are causing the constant issues, so they'll be testing those as well. Score!
-
T3...::Scary music::. Now your talking my man, how deep do you want to go? Lets get started with some links.
http://homepage.ntlworld.com/robin.d.h.walker/cmtips/signal.html
"Fundamentally, a T3 timeout occurs when the cable modem fails to receive a RNG-RSP from the CMTS within 200 msec (after sending a RNG-REQ). A T4 timeout occurs when a cable modem fails to receive a RNG-REQ transmit grant MAP from the CMTS within 35 sec on the downstream channel (after receiving the previous RNG-RSP). There are number of reasons that these could occur and I will list a couple below for each and help guide you the root cause, but understand this is not and exhaustive list."
Quote from http://bradyvolpe.com/docsis-101/docsis101_station-maintenance/
So what does that all mean? Think of your modem as a record player, and your internet like the music, and the signal coming in through the cable wire like the record. Now, a T3 is like the music skipping. It could be a scratch in the record(signal issue), the record player wobbling (modem firmware), a issue with the needle (modem hardware), or someone bumps the player (electrical). Now like in real life, the most likly cause is a scratch in the record or someone bumping the table. So is the most likly cause of T3 electrical or signal. Much more so with modems, its likly to be signal. Now that isn't really accurate when it comes to the complexity, because as you see in the links, DOCSIS is a pretty heavy, and doesn't translate all that well into simple talk. (Not that anyone here is a laymen, just going into the thick of it would only complicate things)
Anyway, yes, I agree, likly signal related. To be honest, I think its going to take them a couple trips maybe to find the problem. Unless you get a above adverage tech on the first try, or unless you get lucky and its something straight forward like signal ingress from a splitter outside or something. Because if its not that, its probably something that going on your street's amp, and they won't see that unless they rule everything out first (and rightfully so). So fingers crossed, your on the right track, let us know how it goes or if you have any specific questions.
-
TL;DR -- We can rule out the router! Yay Dlink
Time Warner came out today. They swapped out the modem because they were getting some errors from it, and figured it was better safe than sorry... same modem type though; an Ambit.
He first tried to tell me it could be my computer's network card or my router, but I argued that the router is between the network card and the modem -- so if the router can't ping out it's not involving the network card. Besides, even with the router off the modem was displaying those issues. He was going to show me that the line was fine... but his tests weren't responding. hehe
Turns out their first problem is the main console outside. It's giving serious fluctuations in the tests, so he has a service call in to repair that. He also conceded that it must be the lines somewhere, and they may not have completely solved it with just this first step. Thank you guys for giving me at least a basic knowledge to prevent being told to replace something that didn't need to be replaced! :)
The IT guy at Time Warner was only able to detect that I'd lost connection five times in five days (which he still said was way too often), but I showed the service tech the records I had of it happening every ten or so minutes, and he forwarded that. They're pretty interested in resolving this now.
-
YAAAAAAAAAAAA ;D
Good to hear man. Sounds exactly like my buddy on his ATT DSL last year...They saw the disconnects on there side of the modem. They fixed it.
Good to hear man. Good to hear. Then this is resolved for you?
-
Wooohooo. Glad to hear man. I didn't know you had a underground drop though, so yea, pedistool is likely the issue. They can be a real mess sometimes. A bit of advice, unless you actually see someone out there working on it, call back in a day or two to see if a ticket or something was actually put in to get it fixed. Sometimes there will just be mention of it in the notes on your account or something, other times theres a actual ticket number you can reference to keep on top of it. Sometimes it gets overlooked though. The tech means well..puts it on his mental to do list to call it in, but doesn't.
Also, keep in mind we were having some issues with WoW in the beginning, and now that the big problem is being worked on, they might show their ugly face again. No reason to loose focus now that were in the home stretch. :-) Glad things are working out though. Wooot!!!
-
;D
-
>.>
<.<
Ya just had to rain on my parade, Trike. :p Yeah, I know there's still the underlying issue of the router and WoW. But now that we get the big issues resolved, the little ones will be easier to track since they're not being lost in the glare of the larger problems.
I got home from work (a second time) today, and my girlfriend said we're still getting internet drops, so they haven't come out yet. I'll call tomorrow and make sure they don't forget about it. :)
-
::ducks::
Its just when I sense the upcoming victory, THATS when I am driven to mercilesslyhunt down every little problem until the issue is dead. ::nod:: Take no prisoners!! For the muthaland!! Hehe
-
Yay, our old friend is back!
I have remained online for the entire night... my girlfriend hasn't been so lucky. In fact, when we logged into WoW is was most prevalent (since WoW is very unforgiving with dropped packets and such). I stayed online while she repeatedly dropped connection from WoW every 30 seconds or less. Some disconnections happened even before she could become fully connected. She would log in, handshake, drop...
I have changed no settings in my router. There were no specific settings in her computer that should be changed because of a new modem. There are no rules in the router... so nothing there is at fault. The router's log doesn't show anything, nor does the Ambit modem (since it isn't disconnecting)...
Hmm... upon looking at our past messages I must've missed some things when I did the factory reset. I have a few questions.
- Is Unicasting or Multicasting preferable?
I noticed that in the modem logs when it has errors it says "Init unicast blah blah" but that doesn't have anything to do with the router and my girlfriend's wireless. What's the difference between the two? I'm sure I could look it up but Trike's analogies are easier for me to explain to my girlfriend after I get it. hehe
- What is WISH and should it be on?
I could've sworn that I had read in one of the threads a suggestion to turn it off, but can't find it for the life of me. Would that affect her connection?
-
Well the second question is easy enough, if theres two wireless computers, and when you use one the other slows down(or otherwise doesn't work correctly), WISH can be used to adjust that. If its one wireless and one wired, its better to use gamefuel. The reason alot of people disable it is if your not using it, then by default, any wireless HTTP(Website) traffic gets priority. So if your on the laptop playing WoW, and your girlfriend starts watching Youtube, it slows down your WoW more then usual. However if left enable, you can priortize your traffic. We will go over that if needed, but first I have to look back (like you did) and see how your network is set up to see if its even needed.
As for your second question, about Unicasting vs Multicasting. I thought I knew the answer right off the top of my head, but it looks like it may be a bit more complicated then I thought. So I will have to do some more research and see exactly what the Pro/Cons are when in reference to WoW. Think of Unicasting as a IM while Multicasting is a chat room. Unicasting assumes the reciever of the information sent is correct by default based on the medium. With multicasting though, it must announce who it is and where the information is going on each broadcast. A modem is a unicast connection. The ISP and Modem are constantly checking to make sure that connection is stable, and when it isn't you get those T3 errors we were talking about before. Once that connection is established though, the modem doesn't have to broadcast who you are and give your username and password and stuff, the ISP just knows your allowed on. The question is, are those settings for the WAN or the LAN? Are they talking about the connection type of your internet or the network transmission type of the WoW server? If the latter, I will have to research exactly how WoW network connection work. Do you know of any support site for this? Maybe something with some real technical stuff on it? I don't know the WoW site as well as you probably do. Also, It would be helpful is there was a way to check the error logs of the game. Theres probably somewhere in the game files that will tell why she is having problems connecting.
Oh and speaking of which, if you have reset your router to default, you may have to go back in there and set up all the rules and settings we were working on before.
-
Before you reset the router, Save off the current configuration to file. So you can go back later on if you need to and not have to manually configure everything. ;D