Comments on: Connecting to a satellite uplink through a wireless link between two buildings.-2

By: mpkn3rd

mpkn3rd — Fri, 05 Nov 2004 20:36:54 +0000

I would like to indulge your patience a little more and have you describe the bridge link (devices and settings) and where the router (building B side) is located in the mix. It appears to be a DNS issue. That is why I would like to understand the network details a little better.

By: duckdude

duckdude — Fri, 05 Nov 2004 20:05:44 +0000

The connection is a bridge between the two buildings. We don’t have extra routing situations between the buildings, and they are not on different subnets. When we take out the extremities and have just a hub with the wireless bridge with a laptop connected to it(side B) and a hardwired workstation (Side A), we can ping freely between the two, connect and receive and send files. Now we attach a router (Side A). The workstation can get out over the internet but the laptop cannot through the wireless. There are no extra routers. When on the laptop (side B), I can ping through to the router (Side A) local IP address, the public IP address, and depending on the router I can ping the public gateway, however I cannot ping the DNS servers. The DHCP address that the laptop receives is correct. And when all of this is going &*($*# the workstation has no problem getting on. If I bring the laptop over from the wireless side and plug it directly into the hub or router (Side A), I have no problems getting anywhere on the internet or local network. The issue appears to me to be a problem between the wireless and the router. We have switched out 3 different routers to try and address an issue to see if it was that, but that didn’t work. Any help is appreciative. BTW thank you for the replies, but those were my first responses as well to the situation and do not address the issue at hand (unfortunately!)

By: jrgreenberg

jrgreenberg — Fri, 05 Nov 2004 19:55:55 +0000

Using the OSI layer to help t-shoot. Level 1 and 2 are good otherwise you couldn’t see building A’s PCs. If the buildings are on the same LAN segment, then the problem is that Building B devices cannot access devices outside of the segment, which sounds like a routing problem. The problem could possibly be the PC’s TCP/IP settings. Can you ping the internet router’s LAN IP? Wan IP? Trace the path using traceroute. Where is the point of faiulre? Compare Building B devices to Building A devices.

Hope this helps you get going in the right direction.

By: arrghoff2pillage

arrghoff2pillage — Fri, 05 Nov 2004 11:09:39 +0000

Sounds like a routing problem. If the two sides are on separate subnets, then it definately is and will probably require that a static route be placed in the internet gateway to let it know that traffic destined for the far end is to be sent to the wireless link. You may have to educate the ISP on putting in this static route. Many only deal with smaller businesses with one subnet, and the tech staff you usually get is not the level you will need. Then again, you may get lucky.