General discussion

Locked

Configuring WINS

By jhicks ·
We have a network set up with a Windows NT 4 PDC in 1 location and 2 others PCS in another location. The NT network is new (used to be Novell). The 2 PCs can ping the server and all the other PCs on the WAN and also use a unix server located in the same location as the NT server but cannot see anyone on network neighbor hood. The 2 PCs are going through a router and have a different subnet (Example 1.1.1.x is the NT location and 1.1.2.x is the Other 2 PCs). I set up WINS on the server. I set up the client PCs with the WINS server IP But I still Can't see anyone in Network Neighborhood. Although the Names and IP addresses of the 2 PCs show up in the WINS Database. What am I missing? Why can't the 2 remote PCs see anyone in Network Neighborhood?

This conversation is currently closed to new comments.

12 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Configuring WINS

by markb In reply to Configuring WINS

WINS is based on NetBeui and Net Beui is not routable. You will need to set up WINS 'proxy' Server (I believe that's the term MS uses) on the Subnet for the two PC's. This will replicate the WINS Database on the Subnet and keep the information from being ran through the router.. Point to the 'proxy' not the main server and it should work fine.

Collapse -

Configuring WINS

by jhicks In reply to Configuring WINS
Collapse -

Configuring WINS

by mark.tassin In reply to Configuring WINS

WINS is not based on NETBEUI, it is a methodology to map NETBIOS names to IP addresses within Windows NT/98/95/2000. If you're running NT workstation, I would first check that the WINS IP address is entered for both the primary and secondary WINS Server addresses in the TCP/IP properties. By not seeing anyone, do you mean that you cannot see even local nodes? If so are you using DHCP? You'll need to provide the WINS address to the clients by using option 44 to set the ip address and 46 to make the node a hybrix 0x8

Collapse -

Configuring WINS

by jhicks In reply to Configuring WINS
Collapse -

Configuring WINS

by darkbeard In reply to Configuring WINS

Assuming WINS is setup correctly. Your PCs are able to ping. Why not sart with some basics, such as checking your host and lmhost files?

Collapse -

Configuring WINS

by jhicks In reply to Configuring WINS
Collapse -

Configuring WINS

by aekland In reply to Configuring WINS

Network Neighborhood is based on browsers. Every system has the potential to be a browser and keep a list of all available resources. Each subnet will have a master browser and should eventually replicate with the domain master browser. You are probably hitting the local browser. Is the router blocking anything? Check Microsoft for browser issues.

Collapse -

Configuring WINS

by jhicks In reply to Configuring WINS
Collapse -

Configuring WINS

by wgillette In reply to Configuring WINS

The last answer discussed browsers. It is important to note here that what they are referencing is a browse list. That browse list is always maintained by the master browser. The master browser for a NT domain is always the PDC. There are also local master browsers on each subnet. The replication for the browse list to local master browsers can be slow and is effected by what your routers are blocking. Under normal circumstances it can take upwards of an hour for information to become available on a new machine added to the network (each time the machine is booted). I think that the network neighborhood is a very bad construct and incourage my users to avoid it if possible. If it is necessary to locate a computer it is far easier tostart-run then type \\<server-name>. That will use WINS to resolve the address and establish a connection to the server.

Collapse -

Configuring WINS

by jhicks In reply to Configuring WINS
Back to Windows Forum
12 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums