"WRT54GS v1.0"-based network problems

Discussion in 'Cisco/Linksys Wireless Routers' started by Maxx, Jan 20, 2005.

  1. Maxx

    Maxx Network Guru Member

    I am new to the forum but have read and re-read numerous posts and have been following this site since the days of early 802.11b devices. First used the internet in 1991. X/Y/Zmodem/Kermit, Hyperterminal, Unix, text-based browsing and 9600bps modems. Anyhow to make a long story short with the recent speed boost provided to Roadrunner customers (previously @ 3000/384, currently 5000/384 – no comments on the upload “boostâ€) my wireless network showed its limits. Up until the speed boost (simply new bin config files uploaded from one of RR’s servers to the cable modem) my (now old) wireless home network worked just fine. It consisted of (starting from the modem) a Toshiba PCX2500 (latest firmware, excellent SNR values, etc.), a Linksys BEFW11S4 v2.0 (latest v3.2 firmware revision 1.46), a Linksys WMP11 v2.0 (running under the latest v4.0 XP drivers) and two Linksys WPC11 v3.0 (again running under the latest v4.0 XP drivers). All client PCs scattered about the house sport Windows XP Professional (ISO-integrated SP2) and (as you can imagine) have all the latest windows update patches, fixes, device drivers, etc (disabled System Restore, Security Center, Windows Firewall, Remote Connections, Automatic Updates, etc).

    This 802.11b network performed flawlessly and when it came to web-browsing and downloading files I very often hit the cable modem’s caps (3000/384) on each and every machine. Nevertheless, the WEP encryption implemented into the router was rather poor and so I opted to disable WEP and instead enable the MAC filter to allow only PCs from my house to access the router. To further increase security I disabled SSID broadcasting and switched to a channel least populated (in terms of other local WiFi networks) by other devices. No need to mention the performance settings I’ve used (both on the Router and the NICs – as well as XP’s TCP/IP and registry settings) since the bottom line is that the signal levels were great throughout the house, no drops, no stalling, no noticeable router-routing lag, etc. File and printer sharing also worked like a charm (albeit it was slow due to the 802.11b specs).

    With the introduction of Roadrunner’s new standard speeds (5000/384) the 802.11b spec prohibited each and every PC from taking full advantage of the new download speeds. Regardless of the time or given node-saturation, regardless of current local roadrunner network status, with DHCP disabled or enabled, hard-coded business class DNS addresses or residential DNS addresses – each and every local speed test provided results on the level of 3500/360. I had no problem with the upload (the results were more than adequate for advertised 384kbps in a “real world†setting) but the download was most definitely hindered by the nature of 802.11b. To confirm my fears I re-enabled the desktops onboard NIC and connected the cable modem directly to that NIC. The speed tests confirmed my theory this time producing results in the range of 4700/350 – 4800/360.

    The layout of the house makes wired connections a royal pain and so I opted to take the plunge and shell out on a 802.11g setup (paid around $200 for all parts). As a side note - at work I’ve had experience with the products of many different networking equipment manufacturers and yet I decided to stick with Linksys/Cisco. I replaced the 802.11b hardware with the following: a Linksys WRT54GS v1.0 (first flashed to HyperWRT_2.0b4_GS.bin and currently re-flashed to WRT54GS_3.37.2_US_code.bin), two WPC54GS (driver v3.50.21) and a WMP54GS (driver v3.50.21.11).

    Connections between the NICs and the Router established themselves at 125Mbps. The first few speed tests produced results on par with those through the onboard NIC. My new wireless network was finally capable of delivering the full potential of Roadrunner’s new speeds. Transferring files between client machines (via file and printer sharing) was also (as should be expected) much faster. Nevertheless – I am still unsure about a few of the router’s and NIC settings (some of them are naturally new to me, others – I am unsure of how they affect performance – toying with them can as we know can go both ways). The biggest problem I encountered right “out of the box†was that each client machine took much longer to connect to the wireless network then in the case of the 802.11b setup. What is more, although the signal strength reported by Windows Network Connection was always “excellent†on most machines and “Very good†on only one – the connections would periodically drop and strangely enough wouldn’t even come back online. I also discovered that regardless of the client machine I was using – repairing the connection (or forcing a repair while connectivity was present) wouldn’t re-establish the link or in the case of an already present connection – would permanently sever it. This was very strange and annoying. Windows Event Log or Services provided no answers and showed no apparent problems. Restarting or rebooting the machines allowed them to re-establish their connections and again “forcing†a windows-based repair or using ipconfig /release and trying /renew caused the connections to sever. (/flushdns had no effect – nor did obtaining a new IP from both RR and via the Router’s DHCP server).

    I decided to flash the router to HyperWRT_2.0b4_GS.bin – which succeeded but the extra settings (although rather nice) did nothing to remedy the problem. With the router’s signal strength @50% or 100% - the symptoms were the same. In fact, @ 100% some downloads (of both files and website content would start off at a reasonable speed and stall about 75%-80% through the transfer process.

    Against my intuition I decided to leave the router’s DHCP server running, I also limited the number of DHCP clients to the number of PCs in my house, disabled the SSID broadcasting, set the signal strength to 50%, MTU to 1500, provided the router with Roadrunner’s local domain name “nyc.rr.comâ€, set the wireless network mode to G-only, disabled security modes, opted for MAC filtering, set authentication to auto, set basic rate to all, transmission rate to 54Mbps, disabled CTS protection, enabled frame burst, set the beacon interval to 50, DTIM, Fragmentation and RTS Thresholds remained at their default settings, disabled AP Isolation, disabled UPnP, etc.and switched to channel 1 (seemed least crowded).

    Speaking of channels – what is the use of 13 available channels via and with HyperWRT if only the router can choose these extra channels? Wouldn’t setting the router’s channel to (say) 13 and applying the settings destroy the connectivity as all of the NIC driver settings only allow the default US-spec 11 channels? Should I download the EU drivers for all NICs to switch both the NICs and the HyperWRT-flashed router to channel 12 or 13 in the US? What is the advantage of doing so – is it indeed the obvious one of being able to operate at a frequency that is unused by most (aka – bone-stock OEM) US-sold WiFi equipment?

    The problems outlined above continued and led me to reformat one of the machines – a clean install of SP2 with no tweaking and only the basic reinstallation of latest device drivers, chipset drivers, etc. showed no change. The problems persisted. At this point I decided to enable SSID broadcast and WPA security as I know how much SP2 and XP in general doesn’t “like†unprotected and hidden WiFi networks – even if you hardcore the IP configuration, DNS and Gateway info. With WPA-PSK (TKIP encryption) the connections take a while to shake- hands at boot-up but they are now “repairable†and won’t drop on any machine. I also disabled the built-in SPI Firewall (not sure if this was a good choice) and filtered out Port 113 and Multicast leaving NAT redirection and block anonymous internet requests unchecked. Should I do anything about the Group Key Renewal period?

    With WPA enabled, I disabled MAC-address filtering (seeing no use in having both as I am already limiting the number of Router distributed IPs to the number of PCs connected throughout the house and with WPA I doubt that anyone in my neighborhood will be able or interested in hacking my router or gaining access to my broadband connection on LAN).

    Connectivity is no longer a problem but the performance has suffered tremendously. I re-flash the router to the OEM WRT54GS_3.37.2_US_code.bin since HyperWRT was unluckily not doing anything but increasing the heat generated by the router’s internals. Don’t get me wrong – it’s a great firmware but the extra features didn’t magically solve the connectivity issue – once I addressed it (with my “hopefully only temporary†workaround) the performance was gone and just as bad with the HyperWRT as the OEM WRT56GS 3.37.2 firmware.

    Does anyone have any suggestions as to what I should try to bring back the performance without loosing connectivity? Why do I even have to ask these questions in the first place – it is strange to see these Router and NIC problems with Linksys hardware. Any and all comments will be much appreciated.

    Aha, I almost forgot to mention the “generic†NIC settings I’m using (I’ve tried a few other combinations – with no special luck). The Afterburner is enabled, Antenna Diversity on auto, Bluetooth collaboration disabled (I have enough Bluetooth v1.2 quirks with my V600 headset), BSS PLCP Header at auto, IBSS 54g mode at 54g auto, IBSS 54g protection is disabled (enabled made no difference), Power Output @ 100%, Rate @ 54, Roaming Decision on optimize bandwidth, XPress Technology (is this the Speedbooster?) on enabled – I assume the other settings are unimportant. Correct me if I’m wrong.


    PS – In the best case scenario I would like to disable WPA and all forms of security apart from MAC address filtering, I would like to hide the networks SSID and with the routers DHCP disabled (as currently) use the IP in the range from Not sure if this is “safe†– if not – please comment. Finally, why is the IP range a problem? Well, for some strange reason with DHCP disabled the router still suggests and seems to prefer IPs from the range of – very weird. I can hard-code but yet again such a connection becomes unstable. Browsing the router’s internal setup is currently also painfully slow and often stalls. Nonetheless if I run a speed test – I can still get 4700/360 but sometimes (when the limited connectivity problems occur) the results drop to below 1500/100. God - I hope somebody has the time, nerves and guts to read all of this.

    2005-01-20 17:09:29 EST: 4710 / 359
    Your download speed : 4823091 bps, or 4710 kbps.
    A 588.7 KB/sec transfer rate.
    Your upload speed : 368527 bps, or 359 kbps.

    TCP/Web100 Network Diagnostic Tool v5.3.3a
    click START to begin
    Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
    running 10s outbound test (client to server) . . . . . 340.24Kb/s
    running 10s inbound test (server to client) . . . . . . 4.87Mb/s
    Your PC is connected to a Cable/DSL modem
  2. Maxx

    Maxx Network Guru Member

    Sixty some views and not a single reply? Where are all the WiFi gurus? I am still fighting with the random disconnects (wth all signals reported as "excellent" or "very good" - machines are as close to the router now as 5m). Currently (no matter which firmware I use, with DHCP, WEP, WPA, MAC filtering (on or off), switching channels, hiding or broadcasting the SSID - the WiFi connection is lost randomly upon rebooting a given machine (all SP2, latest patches, drivers, etc. - fresh XP installs). Windows Firewall disabled, no antivirus (yet manuals scans with NOD32 come back empty) and no other firewall apps, no spyware, no adware, no trojans, etc.

    The router seems to be constantly connected to the internet. It is only each and every NIC that looses connectivity and ceases to either 1. see the network 2. connect to the network 3. "repair" itslef to re-connect to the network.

    At times the connection will (once actually present) stall and pages will not load. At this time rebooting results in loss of connection, reparing does the same, so does ipconfig.

    Why did Linksys remove the NIC option field to hard-code the SSID? Why does XP (especially SP2) love to hate non-protected (with encryption) WiFi networks? It would be so nice if "it" stopped bugging power-users with comments about security. If I could only get rock-solid performance and connectivity out of a hidden SSID, MAC-filtered, 2-IP-only Router... any suggestions?

    TCP/Web100 Network Diagnostic Tool v5.3.3a
    Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
    running 10s outbound test (client to server) . . . . . 408.42Kb/s
    running 10s inbound test (server to client) . . . . . . 4.85Mb/s
    Your PC is connected to a Cable/DSL modem

    2005-01-23 01:58:24 EST: 4790 / 360
    Your download speed : 4905828 bps, or 4790 kbps.
    A 598.8 KB/sec transfer rate.
    Your upload speed : 369230 bps, or 360 kbps.
  3. Esquire

    Esquire Mesquire Staff Member Member

    Probably a reason why no one has been replying is because this is too wordy! It even took me at least 5 reading sessions to extract info (or the lack thereof) from the lengthy paragraphs above, plus I'm not so sure if you had been following the right place prior as this forum has only been online since April last year - hardly "the days of early 802.11b devices"...... but enough of the teasing 8)

    1. NIC settings
    There is nothing to set since in infrastructure mode, the whole network is controlled by the router - you simply find the SSID on the client, apply the network/encryption key and that's it. It is THAT simple.

    If you are referring to the Advanced settings found in the driver's Properties in Device Manager (your so-called generic NIC settings), they come into effect only in an ad-hoc mode connection.

    XPress Technology - this is equivalent to Frame Bursting, not SpeedBooster.

    2. Channels 12, 13 (and 14)
    By the same token the extra 2 channels should be available to your network since it is the router that dictates network parameters. My experimentations with WMP54G and WPC54G US/EU drivers do suggest the driver's origin is irrelevant, with the exception of the Japanese driver which is required to work with channel 14, a topic that has been discussed briefly by myself and a few others during "the early days" of this forum.

    Note it may be illegal where you are to operate channels beyond channel 11 so check before you do.

    There is also another good reason for Channel 12/13/14 on the custom firmware - easy manageability by the programmer since every user is on the same footing. I also don't understand why you singled out HyperWRT in your complaint since a few other custom firmware support channels 12/13 if not channel 14!

    3. MAC Filtering
    This is not a secure method to protect your network as the data transmission has not been encrypted.

    4. SSID Disabled
    This is not a security feature contrary to popular belief. While the radio may not be broadcasting an identifier, the wireless signal carrying your data still contains such information - how else do devices know to receive and isolate signals sent to the right network to which they belong? The only true wireless invisibility is not to have a wireless network at all.

    Microsoft has documented this issue and is not recommending having SSID disabled.

    5. Encryption vs. Performance
    Generally speaking, there is a slight performance degradation when encyrption is in use since each data packet needs to carry the key so if all things being equal, there is less "room" to carry the actual data, so comparing network performance to a wired network is like apples vs. oranges. Also, the stronger the encryption, the larger the effect on network performance.

    6. Speed tests
    While the use of the Web100 based Network Diagnostic Tester (NDT) and other tests can help you gauge your speeds, it can be misleading.
    a) First of all you are testing your broadband connection as well as your wireless network.
    b) Internet is made up of nodes between the test server and your ISP, and performance can be affect by any number of nodes at any given time.

    It is best to conduct speed tests independent of the other type of connection. In addition, choose an Internet speed test closest to your ISP server. Some ISPs, like mine, offer speed testing services on local servers which eliminate influence from other nodes and bottlenecks on the Internet.

    7. Router's firewall
    I do not recommend disabling the router's firewall. It has no bearing on your wireless network, but it helps to protect your whole network from intruders/hackers. By the way, once you have disabled the router's firewall, all other related settings (port filtering, etc.) are also disabled.

    8. Channels revisited
    Have you tried changing channels on your router? Have you tried all available (and legal) channels?

    9. WZC vs. WCM
    When you install your wireless adapter, did you also install the wireless connection management software that comes with the adapter? If you did, remove it.

    10. WPA setting: Group Key Renewal
    Most people reported a shorter period helped connectivity. However, there are also a few who also reported longer periods improved the situation, so do experiment with the value a bit.
  4. Maxx

    Maxx Network Guru Member

    Strange you should think that my previous two posts lack information (I assume you mean to say they lack relevant info). Nevertheless, now that I look at my post I see the wordiness. In an attempt to break with the "problem threads" that span 15 pages of single-sentence replies and problem statements, I committed an overkill in the opposite direction. Could be a direct result of ESL. And yes, you are right - I must have been to another linksys forum. All in all, someone who's "addicted to LI.org" should understand my good intentions.
    Love the sarcasm... no matter - thanks for the explanation as this is new to me. I thought that if one hard-coded for example the channel in the driver's Properties in the Device Manager - that channel would be set for both ad-hoc and infrastructure modes.
    I called them "generic" (I guess it was a bad choice of words) because they were used on all wireless-g NICs I own that are connected to the router.
    Thanks - now this is clear.
    Great - I will re-flash the router with HyperWRT, set channel 12 or 13 and see if the NICs can re-establish their connection. If so - great - this might be a good solution if all other channels prove taken-up by other WiFi networks (could be the case).
    I did not single out HyperWRT. Albeit it was the only non-linksys firmware I tried and frankly I liked it a lot (made a note of this in the first post) - my "complaint" was not at all a complaint - more of a networking problem. I was simply looking for a solution and HyperWRT (just like the official Linksys firmware did not provide the solution - that is all I wanted to say). My question about the channels was linked directly to my lack of knowledge of the fact that the NIC settings found under properties in the device manager pertain to ad-hoc only. With HyperWRT on the router, I had the choice to switch to channel 12 or 13 but couldn't set it in the NIC's properties (this is why I wondered if it would be there with an EU or JAP driver). However, now that you've explained a few things - I see my fears were not well-grounded.
    Thanks - good to know. Data-interception is not my primary concern - the people who I seem to meet most are the ones that connect to a wireless network (sometimes by mistake) just because they can click on it's icon in windows or the ones who are looking for free local internet access.[/quote]
    Good information. Here again I was only thinking of making it more difficult for "regular" computer users to connect to the network.
    This makes perfect sense and is exactly the point why I initially wanted to disable all encryption, choose channel 12, 13 or 14, apply a MAC-filter, hide the SSID, disable DHCP and allow the router to provide only as many IPs as the number of PCs in my home. I thought this would keep out most of the people I am most concerned with (if at all). I guess I was wrong - I stand corrected. Thanks.
    All very true - I thought this was common knowledge. At any rate, I used an RIT-based NDT tester. Rather close to NYC if you ask me. The other speed test comes form nyc.speakeasy.net - also very close (node-wise). I don't take their numbers to be exact representations of my connections performance but when I compare the relative difference between results I obtain during similar hours, RR network status conditions, etc. - they give me a good idea and show if something is wrong.
    Thanks - especially for the information that disabling the router's firewall - disables all other related settings. Thus in my case (and probably most others) it is a definite no-no.
    Yes I have. The default of 6 proved "unstable" connection-wise. So far I've switched to 1 - same story - found even more networks co-existing on that channel. Finally (for now) I've switched to channel 10 and found no other networks, the connectivity problem seems to be gone. BTW - would you happen to know a freeware program I could use to scan the channels in my local area and see how many networks populate a given channel without actually re-applying a new one in the router's settings and then looking into Windows "Wireless Network Connection"? Speaking of which I think that windows shows networks on more than just a given channel. Anyhow, such a application would allow me to choose the most optimum channel.
    Good tip, but no - I did not install it that way. First the hardware, then the driver (changed the exes to rars and/or simply extracted the directory structure from the pre-existing zips/rars - waited for windows to detect the hardware and pointed the installers to the correct infs).
    Thanks - prior to reading your reply I set this to 7200s, now it is set to 1800s and situation does seem improved. Thanks again for your reply. Maxx
  5. Maxx

    Maxx Network Guru Member

    It looks like (thanks to Speedguide.net) I've found the true culprit of poor performance with WPA (and now I know - also without WPA). Although I understand I should only run LAN tests to test the performance of the WiFi network - the one that really matters to me (performance-wise) is the combination of WiFi + Cable. Below trace results prove that RR (once again) has network problems:

    Resolve/Reverse Lookup:
    68.173.xx.xxx resolved to 68-173-xx-xxx.nyc.rr.com
    DNS Query Results:
    68-173-xx-xxx.nyc.rr.com. 3538 IN A 68.173.xx.xxx
    PS - Instead I use RR's primary and business-class DNS IPs, namely:,,,,, I also hard-code the primary DNS as (in turn the router picks up these DNS IPs:, and
    Ping Results (I presume for Speedguide.net from host):
    PING 68.173.xx.xxx (68.173.xx.xxx) 56(84) bytes of data.
    64 bytes from 68.173.xx.xxx: icmp_seq=1 ttl=55 time=60.4 ms
    64 bytes from 68.173.xx.xxx: icmp_seq=2 ttl=55 time=46.6 ms
    64 bytes from 68.173.xx.xxx: icmp_seq=3 ttl=55 time=44.7 ms
    64 bytes from 68.173.xx.xxx: icmp_seq=4 ttl=55 time=38.1 ms
    64 bytes from 68.173.xx.xxx: icmp_seq=5 ttl=55 time=42.4 ms
    --- 68.173.xx.xxx ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4233ms
    rtt min/avg/max/mdev = 38.169/46.488/60.472/7.543 ms
    Traceroute Results (from Speedguide back to my Cable Modem):
    1 63-217-30-94.sdsl.cais.net ( 1.963 ms 0.262 ms 0.259 ms
    2 ge6-0.cr02.ash01.pccwbtn.net ( 0.394 ms 0.339 ms 0.211 ms
    3 pop2-ash-P12-0.atdn.net ( 28.606 ms 29.648 ms 27.827 ms (ATDN servers are always RRs source of problem)
    4 bb2-ash-P1-0.atdn.net ( 27.972 ms 31.277 ms 31.319 ms
    5 bb1-nye-P3-0.atdn.net ( 35.394 ms 34.657 ms 243.371 ms
    6 pop2-nye-P0-0.atdn.net ( 27.364 ms 26.143 ms 26.287 ms
    7 RR-Queens.atdn.net ( ) 28.259 ms 28.281 ms 28.532 ms
    8 pos1-0-nycmnyc-rtr2.nyc.rr.com ( 28.796 ms 31.365 ms 30.195 ms
    9 pos6-0.nycmnyc-rtr1.nyc.rr.com ( 30.134 ms 32.055 ms 32.063 ms
    10 pos1-0-nycmnyc-ubr7.nyc.rr.com ( 32.565 ms 29.229 ms 31.393 ms
    11 * * * (wonderful - just wonderful)
    12 * * *
    30 * * *
    Router's Built-in Ping Test To Cable Modem IP:
    PING 68.173.xx.xxx (68.173.xx.xxx): 56 data bytes
    64 bytes from 68.173.xx.xxx: icmp_seq=0 ttl=64 time=1.6 ms
    64 bytes from 68.173.xx.xxx: icmp_seq=1 ttl=64 time=0.9 ms
    64 bytes from 68.173.xx.xxx: icmp_seq=2 ttl=64 time=0.9 ms
    64 bytes from 68.173.xx.xxx: icmp_seq=3 ttl=64 time=0.9 ms
    64 bytes from 68.173.xx.xxx: icmp_seq=4 ttl=64 time=0.9 ms
    --- 68.173.xx.xxx ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max = 0.9/1.0/1.6 ms
    Router's Built-in Traceroute Test To Cable Modem IP:
    traceroute to 68.173.xx.xxx (68.173.xx.xxx), 30 hops max, 40 byte packets
    1 68-173-xx-xxx.nyc.rr.com (68.173.xx.xxx) 1.687 ms 1.078 ms 1.070 ms Trace complete
    Router's Built-in Traceroute Test to LI.org (proves ATDN problem outlined above):
    PING www.linksysinfo.org ( 56 data bytes
    64 bytes from icmp_seq=0 ttl=50 time=45.9 ms
    64 bytes from icmp_seq=1 ttl=50 time=45.0 ms
    64 bytes from icmp_seq=2 ttl=50 time=50.9 ms
    64 bytes from icmp_seq=3 ttl=50 time=46.4 ms
    64 bytes from icmp_seq=4 ttl=50 time=44.9 ms
    --- www.linksysinfo.org ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max = 44.9/46.6/50.9 ms

    I guess all I can do now is wait until RR pulls their network together and possibly call them (once again) for a refund... otherwise I will be forced to switch to aDSL or possibly FIOS (once it becomes available in NYC). TWC has a monopoly over cable internet access in Manhattan so unless I switch the method of access - I have to stick with TWC Roadrunner. Horrible.
  6. Maxx

    Maxx Network Guru Member

    WHOIS information for atdn.net: [whois.registrar.aol.com]

    Domain Name: ATDN.NET

    America Online, Inc.
    22000 AOL Way
    Dulles, VA 20166
    Created on..............: May 17 2004 12:34PM
    Expires on..............: Nov 15 2005 2:29PM
    Record Last Updated on..: Nov 16 2004 12:21AM
    Registrar...............: America Online, Inc.

    Administrative, Technical Contact:
    AOL Domain Administration (America Online, Inc.)
    22000 AOL Way
    Dulles, VA 20166
    Tel. 703 265 4670
    Email: domains@aol.net

    Domain servers:

    I love them already.
  7. Esquire

    Esquire Mesquire Staff Member Member

    Software to scan and measure signal quality: NetStumbler

    For your reference, my own rule of thumb in deciding on a channel:
    1. If all channels available to the router are in use, pick the one least occupied.
    2. Pick the channel with the maximum separation from the next best signal or signals.
    3. Be prepared to rate channels 1, 6, 11, with a low priority when it comes to deciding on a channel to switch to. Max separation between these 3 channels =/= best choice.

    By the way, you were correct in pointing out Windows displays networks on all channels (channel 14 may be an exception) - another indication that there is no settings restriction to limit the channel the adapter can connect to in infrastructure mode.
  8. Maxx

    Maxx Network Guru Member

    Thanks for your reply Esquire. Strangely enough once I set the Router's channel to 12 or 13 all client machines will NOT connect or detect a network (in infrastructure mode). I have no clue as to how I can make the NICs pickup the signal. Using Avenger's tip I installed the EU drivers for all WMP and WPC devices - still no luck. I was forced to reset the router and switch back to channels 1-11 for the network to be visible. Any tips?

    BTW - Last night I managed to force RR Tier-3 Techs to create 2 tickets concerning current connectivity problems. Look at the ATDN.NET (AOL) that form TWC RR's backbone. The lag is so horrible I can't even access my EU email account.

    traceroute to (, 30 hops max, 40 byte packets
    1 ( 8.110 ms 7.609 ms 5.955 ms
    2 pos0-3-nycmnyc-rtr1.nyc.rr.com ( 6.784 ms 6.656 ms 6.653 ms
    3 pos0-0-nycmnyrdc-rtr1.nyc.rr.com ( 7.718 ms 8.432 ms 8.262 ms
    4 pop2-nye-P10-0.atdn.net ( 6.256 ms 7.310 ms 6.217 ms
    5 bb1-nye-P1-0.atdn.net ( 165.849 ms 205.587 ms 204.612 ms
    6 bb2-ash-P10-0.atdn.net ( 13.208 ms 13.318 ms 13.703 ms
    7 pop2-ash-P1-0.atdn.net ( 12.254 ms 17.032 ms 13.626 ms
    8 BeyondTheNetwork.atdn.net ( 13.210 ms 13.348 ms 12.171 ms
    9 63-217-30-94.sdsl.cais.net ( 12.235 ms 14.886 ms 12.680 ms
    Trace complete

    PING ( 56 data bytes
    64 bytes from icmp_seq=0 ttl=246 time=14.5 ms
    64 bytes from icmp_seq=1 ttl=246 time=13.0 ms
    64 bytes from icmp_seq=2 ttl=246 time=12.8 ms
    64 bytes from icmp_seq=3 ttl=246 time=15.4 ms
    64 bytes from icmp_seq=4 ttl=246 time=11.9 ms
    --- ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max = 11.9/13.5/15.4 ms

    PING 68.173.xx.xxx (68.173.xx.xxx): 56 data bytes
    64 bytes from 68.173.xx.xxx: icmp_seq=0 ttl=64 time=1.2 ms
    64 bytes from 68.173.xx.xxx: icmp_seq=1 ttl=64 time=0.9 ms
    64 bytes from 68.173.xx.xxx: icmp_seq=2 ttl=64 time=0.9 ms
    64 bytes from 68.173.xx.xxx: icmp_seq=3 ttl=64 time=0.9 ms
    64 bytes from 68.173.xx.xxx: icmp_seq=4 ttl=64 time=0.9 ms
    --- 68.173.xx.xxx ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max = 0.9/0.9/1.2 ms

    traceroute to 68.173.xx.xxx (68.173.xx.xxx), 30 hops max, 40 byte packets
    1 68-173-xx-xxx.nyc.rr.com (68.173.xx.xxx) 1.532 ms 1.056 ms 1.044 ms
    Trace complete

    traceroute to www.google.akadns.net (, 30 hops max, 40 byte packets
    1 ( 6.732 ms 5.514 ms 6.232 ms
    2 pos0-3-nycmnyc-rtr1.nyc.rr.com ( 6.218 ms 6.268 ms 8.187 ms
    3 pos0-0-nycmnyrdc-rtr1.nyc.rr.com ( 7.566 ms 7.308 ms 5.786 ms
    4 pop2-nye-P10-0.atdn.net ( 6.218 ms 7.090 ms 6.601 ms
    5 bb1-nye-P1-0.atdn.net ( 7.208 ms 14.398 ms 6.170 ms
    6 bb2-ash-P10-0.atdn.net ( 110.182 ms 252.108 ms 207.032 ms
    7 pop2-ash-P1-0.atdn.net ( 200.241 ms 212.494 ms 208.442 ms
    8 ( 12.463 ms 14.399 ms 12.226 ms
    9 ( 14.207 ms 13.955 ms 14.265 ms
    10 ( 16.270 ms 18.502 ms 15.319 ms
    11 ( 14.194 ms 17.412 ms 14.060 ms
    Trace complete

    PING www.google.akadns.net ( 56 data bytes
    64 bytes from icmp_seq=0 ttl=244 time=13.1 ms
    64 bytes from icmp_seq=1 ttl=244 time=13.1 ms
    64 bytes from icmp_seq=2 ttl=244 time=14.1 ms
    64 bytes from icmp_seq=3 ttl=244 time=12.6 ms
    64 bytes from icmp_seq=4 ttl=244 time=15.6 ms
    --- www.google.akadns.net ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max = 12.6/13.7/15.6 ms

    PING www.tlen.pl ( 56 data bytes
    --- www.tlen.pl ping statistics ---
    5 packets transmitted, 0 packets received, 100% packet loss

    traceroute to www.tlen.pl (, 30 hops max, 40 byte packets
    1 ( 7.604 ms 7.047 ms 12.750 ms
    2 pos0-3-nycmnyc-rtr1.nyc.rr.com ( 5.471 ms 7.666 ms 7.256 ms
    3 pos0-0-nycmnyrdc-rtr1.nyc.rr.com ( 5.759 ms 6.427 ms 6.877 ms
    4 pop2-nye-P10-0.atdn.net ( 23.927 ms 7.327 ms 6.270 ms
    5 nyk-i2-pos10-0.telia.net ( 9.240 ms 7.269 ms 7.695 ms
    6 nyk-bb2-pos2-2-0.telia.net ( 8.169 ms 7.980 ms 12.252 ms
    7 ldn-bb2-pos7-1-0.telia.net ( 82.231 ms 80.896 ms 81.573 ms
    8 prs-bb2-pos6-0-0.telia.net ( 108.618 ms 90.934 ms 88.078 ms
    9 ffm-bb2-pos6-0-0.telia.net ( 98.301 ms 98.449 ms 98.858 ms
    10 war-b2-pos0-0.telia.net ( 123.333 ms 124.382 ms 127.245 ms
    11 crowley-data-108192-war-b2.c.telia.net ( ) 120.800 ms 120.894 ms 120.877 ms
    12 gsr3.oc12.atman.pl ( 122.198 ms 121.344 ms 122.810 ms
    13 gsr7-at-7-0-120.atman.pl ( 127.293 ms 127.100 ms 124.722 ms
    14 z-atman.o2.pl ( 122.853 ms 126.913 ms 121.916 ms
    15 * * * Request timed out.

    PING www.rr.com ( 56 data bytes
    64 bytes from icmp_seq=0 ttl=41 time=14.0 ms
    64 bytes from icmp_seq=1 ttl=41 time=14.0 ms
    64 bytes from icmp_seq=2 ttl=41 time=14.4 ms
    64 bytes from icmp_seq=3 ttl=41 time=13.4 ms
    64 bytes from icmp_seq=4 ttl=41 time=15.4 ms
    --- www.rr.com ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max = 13.4/14.2/15.4 ms

    traceroute to www.rr.com (, 30 hops max, 40 byte packets
    1 ( 7.147 ms 6.501 ms 6.835 ms
    2 pos0-3-nycmnyc-rtr1.nyc.rr.com ( 7.766 ms 8.129 ms 9.150 ms
    3 pos0-0-nycmnyrdc-rtr1.nyc.rr.com ( 7.288 ms 6.279 ms 6.203 ms
    4 pop2-nye-P10-0.atdn.net ( 6.826 ms 7.743 ms 6.309 ms
    5 bb2-nye-P1-0.atdn.net ( 7.845 ms 14.307 ms 7.723 ms
    6 bb2-vie-P12-0.atdn.net ( 18.310 ms 19.424 ms 28.230 ms
    7 bb2-rtc-P13-0.atdn.net ( 79.810 ms 212.050 ms 213.468 ms
    8 pop1-rtc-P15-0.atdn.net ( 11.768 ms 13.396 ms 12.583 ms
    9 rr-herndon.atdn.net ( 15.294 ms 14.260 ms 14.197 ms
    10 ffaxva-mtc-gsr2-pos3-0.her.rr.com ( 13.277 ms 12.822 ms 14.154 ms
    11 ( 13.286 ms 13.545 ms 13.737 ms
    12 * * * Request timed out.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice