Server not visible on network

Discussion in 'Server Networking' started by Gurmit, Jul 21, 2004.

  1. Gurmit

    Gurmit Guest

    Hi All,
    I'm reposting my question here because I didn't get
    any response in General discussion. One of two domain
    controllers that was upgraded to windows server 2003 from
    2000 is not visible on network. All other windows 2003
    servers are visible in Network Places. I ran resource kit
    utility browsemon which show this serve as master browser.
    I can browse server using \\servername but not through My
    Network Places on any PC on local network. I need to fix
    it because I'm unable to backup this server using
    backupexec because it's not visible to the backup software
    Thanks for help in advance.
    Gurmit, Jul 21, 2004
    1. Advertisements

  2. Is Netbios enabled over TCP/IP? Are these on the same subnet?
    Scott Harding - MS MVP, Jul 21, 2004
    1. Advertisements

  3. Gurmit

    Gurmit Guest

    Yes, Netbios over TCP/IP is enabled and all machines are
    on the same subnet.
    Gurmit, Jul 21, 2004
  4. Are you using WINS? IS this machine pointing to the correct WINS Server? Is
    the address in WINS correct?
    Scott Harding - MS MVP, Jul 21, 2004
  5. Gurmit

    Gurmit Guest

    Yes, we are using wins. This invisible server is also wins
    server. Address in the wins server is correct. All
    machines can ping this server using netbios name, all
    machines can browse server using \\servername. Only issue
    is that I can't see this server in My network places from
    any machine and in Veritas Backup exec 9.0 backup
    selection. I appreciate your help on this matter.

    Gurmit, Jul 21, 2004
  6. Gurmit

    Bill Grant Guest

    I would suggest you run the browstat utility from the support tools and
    see what is happening. Are you sure that these machines all have the same
    down-level name for the domain? The browser service only uses the Netbios
    names, not DNS names. Browstat should show you what is going on.
    Bill Grant, Jul 22, 2004
  7. First open a dos prompt and run net config server
    and verify the hidden field says no. Next verify the
    server service is running; you may have to stop and
    restart the service to do this. Next open My Network
    Places on the server itself; does it show up? You may
    want to use a network sniffer to capture the host name
    announcement packets to find out which SMB or segment
    master browser the machine is registering with.
    Michael Giorgio - MS MVP, Jul 22, 2004
  8. Gurmit

    Gurmit Guest

    net config server command shows Hidden=no. Restarted
    the server service. Browstat show this server as master
    browser and 3 other servers as backup servers. no luck so
    far. Can I rerun os setup? will that help?

    Gurmit, Jul 22, 2004
  9. Disable the computer browser service
    Michael Giorgio - MS MVP, Jul 23, 2004
  10. Gurmit

    Gurmit Guest

    Thanks everyone for help. Problem was resolved by
    trasferring PDC emulator/master browser roles to another
    domain controller. Server wasn't willing to give up it's
    master browser role until I trasfer PDC emulator role to
    another server even the registry key was set to
    IsDomainMaster=False. I need to backup this server very
    badly so I end up paying microsoft $99. Not bad saves lot
    of time.
    Thanks again.

    server>-----Original Message-----
    Gurmit, Jul 23, 2004
  11. Gurmit

    Bill Grant Guest

    Yes, that is certainly true. The server holding the PDC emulator role
    must be the domain master browser. It does not explain why you could not see
    it in a browse list. Can you see the machine which is now the DMB in your
    browse list?

    Was the server you couldn't see mutihomed? Multihomed master browsers
    are a big no-no.
    Bill Grant, Jul 24, 2004
  12. Gurmit

    K Guest

    Is it supposed to be enabled? What does disabling it do?

    K, Jul 25, 2004
  13. Gurmit

    Bill Grant Guest

    That depends on your situation. Microsoft is phasing out the use of
    Netbios names. Active Directory doesn't require it as it is based on DNS for
    name resolution. If you have "down-level" machines like W9x or NT, or you
    have applications or devices which rely on Netbios names, you probably still
    need Netbios. The browser service is an NT legacy service so it still uses
    Netbios names.

    If you don't need it, disabling Netbios over TCP/IP (on all machines)
    will impove your LAN performance, because it eliminates the Netbios
    broadcast traffic.
    Bill Grant, Jul 26, 2004
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.