After removing NetBIOS Cannot connect WS to domain

Discussion in 'Server Setup' started by Peter-Paul Jansen, Jan 15, 2009.

  1. On my Windows Server 2003 R2, I have disabled NetBIOS according to procedure
    found in Technet:
    ------------------------------ Start
    procedure ------------------------------------------------
    To disable NetBIOS over TCP/IP
    1.From the Start menu, right-click My Computer, and then click Manage.
    2.Expand System Tools, and then clear the Device Manager check box.
    3.Right-click Device Manager, point to View, and then select Show hidden
    devices.
    4.Expand Non-Plug and Play Drivers.
    5.Right-click NetBios over TCP/IP, and then click Disable.

    Note: This disables the SMB direct host listener on TCP/445 and UDP 445.
    This procedure disables the netbt.sys driver. The WINS tab of the Advanced
    TCP/IP Settings dialog box contains a Disable NetBIOS over TCP/IP option.
    Selecting this option only disables the NetBIOS Session Service (which
    listens on TCP port 139). It does not disable NetBIOS completely.
    ------------------------------ End
    procedure ------------------------------------------------
    After I restarted the Server, a message came up saying that at least 1
    service was not started. To lose this message I wenjt to services and
    disabled the NetBIOS Helper service.


    My domain is like xxx.local. It´s NetBIOS name was XXXLOCAL.
    When I now try to connect a Workstation to the domain, it cannot find a
    domain controller.
    It did before, but even then, it connected to XXXLOCAL and not to eee.local
    The workstation´s DNS Server is pointed to 192.168.0.5, so it should be able
    to find it

    My network setup:
    1 Novell server: 192.168.0.250
    1 adsl router (this is the only gateway in this subnet): 192.168.0.1
    1 Windows 2003 R2 SP2 server I have setup as follows:
    Configured as DC, DNS, DHCP and File Server
    ------------------------
    LAN1:
    Domain suffix: --
    IP address: 192.168.0.5
    Gateway: 192.168.0.1
    DNS Servers: 192.168.0.5
    --------------------
    LAN2: Disabled
    -------------------

    Can anyone help, please?
    TIA

    Peter/Paul Jansen
    Rijswijk, The Netherlands
     
    Peter-Paul Jansen, Jan 15, 2009
    #1
    1. Advertisements

  2. Addition to previous post:

    When I run nslookup on my ws, I get the following response:
    Default Server: tesrv01.eee.local
    Address: 192.168.0.5

    On my Windows Server 2003 R2, I have disabled NetBIOS according to following
    procedure found in Technet:

    ------------------------------Start_procedure------------------------------------------------
    To disable NetBIOS over TCP/IP
    1.From the Start menu, right-click My Computer, and then click Manage.
    2.Expand System Tools, and then clear the Device Manager check box.
    3.Right-click Device Manager, point to View, and then select Show hidden
    devices.
    4.Expand Non-Plug and Play Drivers.
    5.Right-click NetBios over TCP/IP, and then click Disable.

    Note: This disables the SMB direct host listener on TCP/445 and UDP 445.
    This procedure disables the netbt.sys driver. The WINS tab of the Advanced
    TCP/IP Settings dialog box contains a Disable NetBIOS over TCP/IP option.
    Selecting this option only disables the NetBIOS Session Service (which
    listens on TCP port 139). It does not disable NetBIOS completely.
    ------------------------------End-procedure------------------------------------------------

    After I restarted the Server, a message came up saying that at least 1
    service was not started. To lose this message I wenjt to services and
    disabled the NetBIOS Helper service.

    My domain is eee.local. It´s NetBIOS name was EEELOCAL.
    When I now try to connect a Workstation to the domain,
    it asks for a user name and password of an account that is authorised to
    become member of the domain.
    I enter the administrator user name and password.

    Then it gives the message (in Dutch):
    The following error has occurred while becoming a member of the domain
    eee.local:
    Windows cannot find teh network path. Check whether the network path is
    correct and whether the target computer is not occupied or turned
    off.Contact your network adminstrator if Windows still cannot find the
    network path.

    It did connect before, but even then, it connected to EEELOCAL and not to
    eee.local
    The workstation´s DNS Server is pointed to 192.168.0.5, so it should be able
    to find it.

    My network setup:
    1 Novell server: 192.168.0.250
    1 adsl router (this is the only gateway in this subnet): 192.168.0.1
    1 Windows 2003 R2 SP2 server I have setup as follows:
    Configured as DC, DNS, DHCP and File Server
    ------------------------
    LAN1:
    Domain suffix: --
    IP address: 192.168.0.5
    Gateway: 192.168.0.1
    DNS Servers: 192.168.0.5
    --------------------
    LAN2: Disabled
    -------------------

    Can anyone help, please?
    TIA

    Peter-Paul Jansen
    Rijswijk, The Netherlands
     
    Peter-Paul Jansen, Jan 15, 2009
    #2
    1. Advertisements

  3. HI,
    you should post the ipconfig output of your w2k3 domain controller
    jk
     
    Juergen Kluth, Jan 22, 2009
    #3
    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.