Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[JakeCallery]

Hey guys, anyone else having trouble seeing the wired network from the wireless side?
When I do a tracert from a wireless computer on the hostname of a wired computer, it ends up looking outside of the the local network, which is obviously not where I want the packets to go.

I think because of this I am having trouble sharing files and such.

The wired machine is connected to a 24port switch (unmanaged) which is connected to the DIR-825.  The wireless machines are connected to the 2.4Ghz radio.

The wired machine has a static IP 192.168.1.95, and the wireless machine is DHCP.  Both are using the router as the DHCP and DNS server.

The really strange thing I can do a tracert of any name (even machines that don't exist) and it resolves to the same IP address.  if I put in "tracert mybox" (from the wireless machine) I get:
Tracing route to mybox.wowway.com [64.158.56.38]

It eventually gets to that external address, which by the way is NOT my external address from WOW.  I currently have a 74.199.x.x address from them...

If I run the same tracert from the wired machine it correctly states "Unable to resolve target system name mybox"

I've tried the trace route from a window XP box, windows 7 box, and my android phone... all of which have the same results...

any ideas?  This is getting frustrating..

Thanks!

[smlunatick]

Several routers have "WLAN Protection" settings which is on.  This limits the wireless access to not be seen by other stations.

Also, the trace result is correct.  All traffic is routed to the DNS servers set up on the router first then comes back to the "local" network.  You will need to set up the HOST files.