Or another) but the VPN was able to manage these with a reconnect command. I have encountered other VPN related errors (all related to timeouts of one kind Update: There is always something trying to update software or otherwise force a reboot, but I have run a session as long as four days without an Error 692. I hope to let the computer run for a week without a reboot to further test the fix. With NO logs (Windows, router, cable modem) revealing entries during these disconnect events, I am still researching this.Īfter the hotfix, no failures have occurred following two successive 36 hour sessions. Time and will fail with an Error 692 within a few hours to 24 hours. My symptoms: For reasons unknown, my Internet connection is lost for about a minute or two, tens of times per day (laptop to wireless router to cable modem to cable provider). This hotfix appears to have fixed my problem with "Anonymizer Universal", a security product/service and also a VPN from running within Windows 7, 圆4. Tried it on 3 Systems and now i can´t reproduce the error even after >40 connect/disconnect cycles. solved the issue even it is supposed to fix something else. That's what tcp is for anyway, right? So we don't have to worry about "network issues" or "re-sending" data? Ha! -Michaelįor me it looks like installing the HotFix As an occasional code-tester, I wouldn't be suprised if causing multiple transport-error disconnects and subsequent reconnectes wasn't tested at all. As a programmer, my guess is that something wasn't properly tested in the Windows 7 build of these components. I haven't been able to find any decent documentation on changes to RAS from XP->Vista->Windows 7. I find this piece much more interesting and frustrating than crappy routers or bad nic drivers. The error messages generated are numerous and inconsistent when this happens. The issue is that after several disconnect / reconnect cycles Windows 7 RAS becomes despondent and flatly refuses to connect to ANY VPN until after a reboot. But hey, we all understand that things happen. Beyond these troubles, the original issue isn't that the VPN won't stay up. This happens on both the physical ethernet port and on the corresponding docking station port on multiple switches. The link flapping doesn't seem to correspond to the vpn disconnects. The driver flags the interface as up then down, then up and down repeatedly through the day. I have found that the Intel driver for Windows 7 圆4 for the 82XXX series chips is either buggy or not properly conforming to the Windows 7 driver model. ![]() The (seriously) offending machine is a Dell Latitude 6400N with integrated Intel 82567LM gigabit ethernet. A frame with a 1024 bytes of icmp junk might leave the router on the internal network as a proper frame, but with only 1023 bytes of data. the wan port buffer (I'm assuming it's actually buffered in hardware somehow) is not recording all data received. ![]() We removed the failing Linksys router after playing with network monitor and ping -l xxxx. As you mentioned, Windows 7 64 bit + ASA 55XX using Windows RAS components seems to be mysteriously troubled. My opinion is that the error trapping piece of RAS is missing some reset functionality that existed in the prior version.ĭon, The trouble continues. ![]() The OS trouble is not solved at this point and has only been dampened by having replaced the faulty router. Something in the Windows 7 RAS mechanism has changed significantly since Vista. Windows Vista 32 bit and Windows XP SP2 32bit worked in the same environment, and were able to reconnect successfully each time with no reboot requried.Ģ. This happened on two machines running the RTM build (Action Pack) of Windows 7 Pro 64bit. After two to three rounds of this trouble, RAS fails completely and required a reboot to reconnect to the vpn. Error 692 is one of many, many random RAS errors that have been displayed as a result of this. This dropped the L2TP tunnel, which in turn mangles the _ out of Windows 7's RAS subsystem (See #2). It was missing inbound bytes transmitted from the cable modem! When those incomplete frames arrived at the pc they were seriously malformed. It turns out (through some serious digging!) that the Linksys routers external interface has a bad ingress buffer. The internet access is cable service with a Linksys router. The described scenario above is a residential setting. If anyone is interested in what the trouble turned out to be:ġ. I've tried different driver versions and various options, but considering that this same exact set of circumstances happened on two different machines rules out most of these types of problems. The problem has actually be resolved (mostly), see below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |