General discussion

Locked

remote network connectivity problem

By webmaster ·
Got two Cisco routers to connect my workplace and the network implemented with a remote workspace trough a dedicated line. The problem is I can ping the other router and the machine attached to it but can't get it to show up on windows network neighbourhood. Had to assign a different ip number in the 3rd octet to get ping responses and traces to the router and the machine, also have both routers as gateways on TCP/IP properties being the local one set up by default. Do I have to expand the subnet mask to the next class?

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

remote network connectivity problem

by TechKid In reply to remote network connectivi ...

It won't show up in Network Neighborhood because routers don't pass broadcast packets. You would have to connect the two sites with a bridge/switch wich doesn't sound possible in your situation.

Collapse -

remote network connectivity problem

by webmaster In reply to remote network connectivi ...

Poster rated this answer

Collapse -

remote network connectivity problem

by cbeyer In reply to remote network connectivi ...

Your problem is not the range of ip addresses you are using, but the fact the segments are separated by routers that are blocking the UDP broadcasts your Windows clients are using to build the computer list in Network Neighborhood. There are two ways I can think of to solve this problem:

1) Make the two LANs one logical network segment by bridging them with your routers

OR

2) Implement WINS or LMHOsts files to assist your clients in browsing between segments.
-----------------------------------------------
More Detail for Option 1:

This will make the clients in your two locations function as if they were all plugged into one big switch... all broadcast traffic from one location will be transmitted over your deicated line. If you have a lot of clients on either end of the line this could impact the performance of your WAN. For more info on how to set this up, check out http://www.cisco.com/univercd/cc/td/doc/cisintwk/ics/cs006.htm.

-----------------------------------------------
More Detail for Option 2:

This is the option I would look at, if you are running a Windows NT/2000 server somewhere on your network. Run the Windows Internet Name Service on your server, then configure your clients to point to that server for WINS resolution. This server will keep a dynamic list of clients as they come on/off your network and allow them to find each other.
For more informatin on how WINS and browsing works, check out http://support.microsoft.com/default.aspx?scid=kb;en-us;Q150800.

Good Luck!

Collapse -

remote network connectivity problem

by webmaster In reply to remote network connectivi ...

Poster rated this answer

Collapse -

remote network connectivity problem

by webmaster In reply to remote network connectivi ...

This question was closed by the author

Back to Networks Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums