Re: browser service

"Gabor Szemeredy"<gaborszem@xxxxxxxxxxxxx> wrote in
news:65fa1cf017c9496b8f4c28bba3e660f6@xxxxxxxxxxx:

Hello friends!
We have 3 subnets in our network.
192.168.42.xxx
192.168.52.xxx
192.168.62.xxx
Routing is Ok , so I can ping the workstation
on every segment from any other workstation.
Active directory is not activated.
On the windows 2003 server ( on the segment 62)
is IsDomainMaster in the registry set as True
hoping that it will become the domain master browser collecting
browser lists from master
browsers on the other segments.
We are still viewing only the workstations on the segment we are
on. Is it possible to set up the whole network to see all
workstations on all segments , or it is impossible without active
directory? Thanks


By design, Windows Networking does not span subnets.
To do this, you have two basic options:
1) Add all hosts to the "lmhosts" file
(usually c:\windows\system32\drivers\etc\lmhosts)
2) Use a WINS Server

For more info:
"MS Windows NT Server 4.0 - WINS Architecture and Capacity Planning"
<http://www.microsoft.com/technet/archive/winntas/plan/winswp.mspx>

HTH,
John
.

Relevant Pages

  • Re: For the AdaOS folks
    ... Mach's concept of thread migration seems inappropriate. ... Since priorities must be enforced by the AdaOS kernel at all times (to ... could be on any workstation in the network. ...
    (comp.lang.ada)
  • RE: Routing oddity on domain.
    ... The client workstation 's gateway should be the Router internal IP address ... >I. Please check DNS and Gateway settings. ... >II Please ensure proper binding order of the network adapter cards. ... Click Internet Protocl, and then click Properties. ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Also, Logon type of 3 is a network logon, this is considered a ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Slow Accessing a memo field on a network
    ... It's pretty normal for database access across the network to take as much as 10 times longer under multiuser. ... I just can't see being able to open a form in under one second and then if I have that same table open on a second workstation that it could then take some 5-10 seconds to open that same form. ... It must first ask Windows to poll the network to see if other users have cached changes that must be updated to the server and then updated to the local cache. ... I understand that the memofield access can be slow ...
    (microsoft.public.fox.programmer.exchange)