RV220 host name resolution LAN<->WLAN stops working

[Jens Janssen]

Hi,

I'm running a Windows Server 2008 R2 connected via cable to my RV220. The server is hosting several websites running in separate virtual machines. These websites are accessible through a reverse proxy set up on the 2008 R2. In addition the 2008 R2 provides access to storage over Windows file sharing (client backup, file sharing ...). Most of the clients are connected via wireless.

My problem is that after some time (~24h) I lose the connection to the services provided by the 2008 R2 server as a result of (host) name resolution has stopped working. This only happens for wireless clients. Wired clients are not affected.

To give more details: Network clients connected via wireless can't see clients connected via Ethernet and the network shares are not accessible anymore (even by putting in manually "\\hostname\share", but "\\[IP address]\share" still works). Being connected via Ethernet the communication between client and server works flawlessly - the server appears immediately on the network device list. The other way around is also not possible: the server can’t see clients connected via wireless. The reverse proxy is still accessible through wireless connection by putting in the IP address, e.g. "http://192.168.1.123/homepage" but "http://hostname/homepage" won't work.

A restart of the router will fix things but only for the next couple of hours.

Any idea what is going on? Any help is appreciated.

[Jens Janssen]

In addition: I'm using FW 1.0.2.4. Before setting up the router the configuration was set to default values.

[linksysinfo]

Hi Jens,

what is your DHCP lease time?  sounds like DNS is not working or failing after a certain time.  try increasing the lease time for DHCP and see if that works.

Simon

http://www.linksysinfo.org

[Jens Janssen]

Hi,

this does not help. Again, after less than 24 hours I cannot see wired clients in the network sharing center from my wireless clients.

Anyway, the network host list (Status -> Available Local Network Hosts) is weird:

unknown	192.168.1.116	3C:4A:92:xx:xx:xx	Dynamic	Wired
unknown	192.168.1.158	00:1A:73:xx:xx:xx	Static	Wireless
unknown	192.168.1.235	98:4B:E1:xx:xx:xx	Dynamic	Wired
unknown	192.168.1.164	00:0C:29:xx:xx:xx	Dynamic	Wired

The second client is not static! And btw, the list is by far not showing all network clients and most of the host names are "unknown" (known bugs?).

The DHCP list (Networking -> DHCP leased clients) is also not showing all DHCP clients.

[Jens Janssen]

Fixed: Had trouble with Server 2008 R2. Network Discovery won't stay on because of missing services. Starting the right services fixed my problem with the missing hosts.