Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot browse Network Neighbourhood 1

Status
Not open for further replies.

darrynliew

Vendor
Jul 24, 2002
8
BN
Hi!

We had recently installed a WAN consist of Cisco & 3Com ( old network ). After we integrate the Cisco into the 3Com WAN. We could not browse the Network Neighbourhood after setup the whole thing. The network consist of MS Win95, 98 and server is NT4. Network Equipment consist of Cisco 3660 + remote site Cisco 1720. Connection established using Leased Line. 3Com network is Ok....Only the Cisco...

Can any one comments on this ??

Anyway, no matter you post a reply or not...thank you for your kind attention.
 
Sure- it's called port 137, 138 and 139 NB over TCP. In order for *browsing* to work properly, for WINS to work properly and to login to a remote PDC, you need to enable something called IP Helper which has a set of 10 types of boradcast packets to forward. Normally broadcasts will stop at the router or layer 3 boundry. You need to tell the router that it's ok to pass certain types. If you do not want the 10, you can enable only what you need by using UDP forwarding for each protocol you do want.

IP helper goes on the interface closest to the client.

Cisco's design notes:
Windows Networking Design Implementation Guide

Here is MS's own page on it:


MikeS

Find me at
"Take advantage of the enemy's unreadiness, make your way by unexpected routes, and attack unguarded spots."
Sun Tzu
 
Or you could configure wins replication between the two remote sites.

WINS can be a very tricky thing to get working over a routed link. -Danny
dan@snoboarder.net






 
Wy had it right... Netbios over TCP/IP is the way... but it is a major league security hole... probably want to install Zonealarm or Blackice on all of the PCs in such a network to cut down on "incidents"... JTB
Solutions Architect
MCSE-NT4, MCP+I, MCP-W2K, CCNA, CCDA,
CTE, MCIWD, i-Net+, Network+
(MCSA, MCSE-W2K, MCIWA, SCSA, SCNA in progress)
 
2 solutions to this, 1 you implement WINS which is the recommended way if you have NT4 server, OR enable the IP Helper function. The second way tends to clog up networks if your not careful with excesive broadcast traffic but is an easy way to get this to work.

For the wins method, get wins going on nt server, point your remote clients to use this server by configuring WINS server address in Client's TCPIP properties. Bit more complex if your using DHCP. Get back to the forum if you've still got problems.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top