Hey Bro, I syphatise with you I have alos been experiencing this issue with a similiar model to what you have the wrvs4400n , every 3 days i have to reboot the router because both dns and file and print traffic gets booted, and after i reboot magically everything is normal , did firmware updates same issue , is anyone in linksys listening?????

I think they are, but their hands seem to be tied by Cisco's quality assurance procedures (always slow). I wish I could get a hold of the new firmware. I understand some are shipping with it already instaleld too.

Hi alegalle,

1. I'm running on standard channels (3,6,9) in mixed mode.

2. Cable, through local comcast provider

3. Gateway was not set per 4400 documentation that state it's not needed for static IP's on 4400. I set this anyway and problem still persisted.

Modem

  |

WRT350N (6)

    |                |

Wap1(3)   Wap2(9)

all conected through ethernet (wired backbone) so not doing WDS or range extending, otherwise they would have to all be on the same channel but those routers don't support that of course.

On both WAPs make sure you specify GW (like you already have) and also DNS. You can point DNS back to your GW or use OpenDNS (My preferred) 208.67.222.222 and  208.67.220.220.

Once you connected to one of the WAP do the following:

On XP, click Start > Run > type cmd and click OK or hit Enter

From the command prompt type "ipconfig /all" with out quotes

make sure that the IP Adddress, Gate Way and DNS servers are what you have specified in your routers.

Now again from the command prompt

type ping 4.2.2.2 (this should return a reply from 4.2.2.2)

now type ping google.com (the first return should be a resolved IP address, then reply from the resolved IP)

Let us know if this is working out.

According to the documentation you don't even need to specify the default gateway on the linksys wap or the dns settings. These are obtained directly from the dhcp server on the WRT350N suppled by comcast. That would make no sense unless there is some internal bug that won't pass dns settings if this isn't set already, and "only" for G clients. I can try it but I doubt that will make any difference, like specifying the gateway. Also I did specifiy alternative dns on nslookup with the same results to rule out problems with comcast dns directly from the command prompt. During this time all N clients were working fine.

Also all G clients are Vista 32 bit, and the N clients are Vista/OSX.

I was waiting on the latest firmware release to see if that would clear up the issues.. as they seem related to "G" clients only which are Lenovo Windows 32 bit systems. As that has been delayed I wanted to see if there were any other suggestions to try that might clear this up, maybe a wide band radio channel that might be more compatible, or some other wireless setting I hadn't thought of.. or worse yet I didn't have the network configured properly using the right linksys hardware.

Cisco contacted me and the only thing they could suggest is switching to G only from switched mode and testing. If that doesn't work I'm going to replace the hardware with proxim.

Jason, what are the ip settings you are receiving from your router.  Are you receiving dns from the router?

Yes, the clients are receiving DNS correctly and can release and renew ip information fine. I can also use nslookup to select a different dns server and do manual lookups, which is where I tracked down the issue to. DNS lookups won't return consistantly, and usually not at all. Disabling wirelss and rebooting doesn't fix the issue, and the issue fixes immediately after rebooting the WAP. After a few days we are back in the same situation.

Have you adjusted the wireless channel to see if that helps?  You could be getting wireless interference from something.  Is there any wireless other than yours in the vicinity?

No other wireless for miles at this location. I checked for other frequency interference with the Wi-Spy; nothing. It comes in handy, as I found harmonic distrotion once from some cheap wireless mics we use at another location.

I beleive we spoke a few days past, one thing that you may want to check is MTU size. I understand that the issue is on the WAPs and not the router as any client connected to the router performs as expected. Typically we adjust the MTU on DSL connections and not on cable which I beleive is what you have. Set the MTU to 1492 on the router and then also change the Advanced Wireless settings to force transmission for all G clients to 54Mbps. Let us know if that makes a difference.