Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Mogorain]

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.

[Trikein]

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?

[Mogorain]

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*

[Mogorain]

Ok, so I'm now seeing these ICMP Errors quite frequently, but I never saw them before. 

[Trikein]

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.

[Trikein]

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?

[Mogorain]

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.  :-/

[Trikein]

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.

[Mogorain]

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.  :-/

[Trikein]

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?

[Mogorain]

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

[Mogorain]

On an unrelated note...  play ya SC2 Trike!!

[Trikein]

 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.

[Mogorain]

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?

[FurryNutz]

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.