My ISP provided a BEC 7800 TN R2 router with wireless capability for my home. I have a Windows desktop computer connected via Ethernet cable to the router. I have no problems with my desktop computer. I also have a Windows laptop. Both are running Windows 7.
When I connect my laptop via Ethernet cable, I can…
- Connect to the Internet
- Connect to router admin page
- Ping the desktop computer
- Access the desktop computer's shared drive
- Remote Desktop Connection to the desktop using either its Windows name or IP address.
- Print to the network-connected printer
When I connect my laptop to the router via wireless, I can..
- Connect to the Internet
- Connect to router admin page
- (but nothing else)
I would like to access LAN resources (desktop computer and printer) when connected wirelessly.
The wireless page on the router, looks like this:
You can see that my router supports "Client Isolation." However, I do not have that feature enabled. Just for testing, I enabled it. It made no difference. I disabled it again. No difference.
When I connect my laptop via Ethernet cable, I get…
ipconfig
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : RanDSLV.gateway
Link-local IPv6 Address . . . . . : fe80::396e:db30:d39e:cea0%11
IPv4 Address. . . . . . . . . . . : 192.168.50.58
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.50.254
tracert 192.168.50.70
Tracing route to Abednego [192.168.50.70] (the desktop computer)
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms Abednego [192.168.50.70]
Trace complete.
route print
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.50.254 192.168.50.58 20
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.50.0 255.255.255.0 On-link 192.168.50.58 276
192.168.50.58 255.255.255.255 On-link 192.168.50.58 276
192.168.50.255 255.255.255.255 On-link 192.168.50.58 276
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.50.58 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.50.58 276
===========================================================================
Persistent Routes:
None
When I connect my laptop to the router via wireless, I get..
ipconfig
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : RanDSLV.gateway
Link-local IPv6 Address . . . . . : fe80::d4b3:cc8a:b4d9:1944%10
IPv4 Address. . . . . . . . . . . : 192.168.50.59
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.50.254
tracert 192.168.50.70
Tracing route to Abednego [192.168.50.70] over a maximum of 30 hops:
1 Mishael.RanDSLV.gateway [192.168.50.59] reports: Destination host unreachable.
Trace complete.
route print
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.50.254 192.168.50.59 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.50.0 255.255.255.0 On-link 192.168.50.59 281
192.168.50.59 255.255.255.255 On-link 192.168.50.59 281
192.168.50.255 255.255.255.255 On-link 192.168.50.59 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.50.59 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.50.59 281
===========================================================================
Persistent Routes:
None
With regard to Windows networking, both networks are set as "Home networks."
Question: Can you suggest what configuration change I need to make so that I can access LAN resources when connected wirelessly?
Best Answer
I posted the original question four years ago. In the eight years that we owned the router, I never was able to find a solution. Last week, we replaced the router and the new router worked perfectly without any special configuration changes.
One possible workaround was suggested yesterday by @Kinnectus, "...a configuration where you have to VLAN the wireless to the LAN." That may work, but I cannot try it any longer since we upgraded.
My conclusion is that it was a shortcoming of that old router. The solution for us was to replace the router.