>>>>If you suspect that DHCP maybe the cause of the lost connection why not turn it off? Either create a static IP for the desktop and test or turn on the a replacement DHCP on one of the servers.
>>>
>>>If it's the typical Linksys DHCP issues, I suspect what Michel is seeing is that the lease his WAN IP address gets from his ISP is the one that's misbehaving, not the IPs that the router DHCP server doles out to the LAN machines. If his ISP doesn't change his WAN IP very often he might get away with making it a static address (my IP address on my cable ISP has only changed 3 times in the 8 years I've had the account, others [especially ADSL] change more frequently)
>>>
>>>Besides, his router model supports dd-WRT firmware (and maybe others as well) so he might as well try it - I've had excellent results with it.
>>
>>Knowing very little about these things, why does one opt to use non-manufacturer fimware on these devices?
>>
>>What are the nature of the "excellent results" you've obtained with it?
>>
>>cheers
>
>Jim,
>I have 2 older LinkSys routers, and I wanted one to be a bridge to another - basically I wanted the 2nd router to connect to my main router wirelessly, but I wanted to allow wired connection into the 2nd router. This was not possible using the LinkSys firmware, but it was with the open source.
>
>Also, I was having problems using BitTorrent, and those were fixed with the open source firmware.
>
>It might be my imagination, but it seems like the wireless connection is more reliable and has a better range.

Thanks Mike. Interesting.

cheers