First, make sure your Windows network runs only TCP/IP. There is not much reason any more to use the other protocols which are available mostly for compatibility with very old servers or clients. Using only one protocol is more efficient anyway.

The general problem with the Windows networking in a network containing (any sort of) routers is that it relies on broadcasts for name resolution and browse lists, and routers usually don't pass broadcasts. Communication of machine names and browse lists (i.e. the lists you can see in the "Network Neighborhood" windows) across subnets requires the use of machines which run special services:

* (at least) one WINS server in the network - must be configured; * one domain master browser for each Workgroup or Domain - must be configured; * one local master browser in each subnet - selected automatically among all active Windows (9x/NT) or Samba machines but can be configured to prefer a machine with long uptime for reliability.

It is possible to use Windows NT machines or Samba for each of these tasks. The file BROWSING.txt from the Samba documentation explains how this works and how to set it up.

It is also necessary that all machines participating in the Windows network are configured to use the WINS server for name resolution.

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum