Announcement

Collapse
No announcement yet.

Problem joining the domain

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problem joining the domain

    Hey there! Iīm quite a noob in the windows 2003 server enviroment. Itīs the first time iīve installed it. Iīve already had a linux gentoo server before and used it as a domain controler with roaming profile.

    Iīm having a weird problem on my server: I can ping it from the workstations, and services like ftp, svn and apache are working fine, but i canīt make my workstations to join the domain, neither map a network drive of the server!

    When I try to join the domain, the netbios name isnīt even found, and using the server.mydomain.com it asks for a password witch i put the administrator one, seconds later it returns an error msg: "Windows cannot find network path"

    Iīve instaled the dns controler, an AD and a file server, just like the tutorials here on this site, witch i found complete and great.

    Any clue? Plz! I would apreciate any help, since Iīve been trying to figure it out by my self and i canīt find a solution. I know itīs probally something silly that I am missing.

    Thanks!!

  • #2
    Re: Problem joining the domain

    Post IPCONFIG /ALL from the workstation AND server.
    1 1 was a racehorse.
    2 2 was 1 2.
    1 1 1 1 race 1 day,
    2 2 1 1 2

    Comment


    • #3
      Re: Problem joining the domain

      Tnx for the help. here it goes:

      Server:

      Windows IP Configuration

      Host Name . . . . . . . . . . . . : farm
      Primary Dns Suffix . . . . . . . : domain.dom
      Node Type . . . . . . . . . . . . : Unknown
      IP Routing Enabled. . . . . . . . : No
      WINS Proxy Enabled. . . . . . . . : No
      DNS Suffix Search List. . . . . . : domain.dom

      Ethernet adapter Local Area Connection:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
      Physical Address. . . . . . . . . : 00-15-F2-C2-86-31
      DHCP Enabled. . . . . . . . . . . : No
      IP Address. . . . . . . . . . . . : 10.90.150.90
      Subnet Mask . . . . . . . . . . . : 255.255.254.0
      Default Gateway . . . . . . . . . : 10.90.150.1
      DNS Servers . . . . . . . . . . . : 127.0.0.1
      NetBIOS over Tcpip. . . . . . . . : Disabled

      Workstation


      Host Name . . . . . . . . . . . . : pig
      Primary Dns Suffix . . . . . . . :
      Node Type . . . . . . . . . . . . : Unknown
      IP Routing Enabled. . . . . . . . : No
      WINS Proxy Enabled. . . . . . . . : No

      Ethernet adapter Local Area Connection:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
      Physical Address. . . . . . . . . : 00-08-74-B5-BC-81
      DHCP Enabled. . . . . . . . . . . : No
      IP Address. . . . . . . . . . . . : 10.90.150.92
      Subnet Mask . . . . . . . . . . . : 255.255.254.0
      Default Gateway . . . . . . . . . : 10.90.150.1
      DNS Servers . . . . . . . . . . . : 10.90.150.90
      WINS . . . . . . . . . . . . . . : 10.90.150.90
      NetBIOS over Tcpip. . . . . . . . : Disabled


      ps: My workstation machines languages are portuguese, so iīve translated the comand result to english

      And just a new information, when i try to run nslookup:

      *** Can't find server name for address 10.90.150.90: Non-existent domain
      *** Default servers are not available
      Default Server: UnKnown
      Address: 10.90.150.90

      > google.com
      Server: UnKnown
      Address: 10.90.150.90

      Name: google.com
      Addresses: 64.233.167.99, 72.14.207.99, 64.233.187.99

      I also have checked if the services NetLogon and RPC are started.

      Thanks again!

      Comment


      • #4
        Re: Problem joining the domain

        Does the server have it's firewall turned on?
        Regards,
        Jeremy

        Network Consultant/Engineer
        Baltimore - Washington area and beyond
        www.gma-cpa.com

        Comment


        • #5
          Re: Problem joining the domain

          Definately strange. If he can ping server from a workstation then the firewall is off. Try flushing the DNS (ipconfig /flushdns from command prompt) and configure a completely new static ip address.

          What are you using for a gateway? Can you have that hand out DHCP? Can you access the internet from the server console?

          Comment


          • #6
            Re: Problem joining the domain

            When trying to join a Windows 2003 domain do not use .com, .net, or .local. Use only the domain name itself, in this case domain, leave out .com

            Hope this helps.

            Comment


            • #7
              Re: Problem joining the domain

              Originally posted by thetsg View Post
              If he can ping server from a workstation then the firewall is off.
              By default Windows Firewall allows ICMP echo requests. So even if the firewall is enabled you will still get a response from the server.
              Regards,
              Jeremy

              Network Consultant/Engineer
              Baltimore - Washington area and beyond
              www.gma-cpa.com

              Comment


              • #8
                Re: Problem joining the domain

                Originally posted by JeremyW View Post
                By default Windows Firewall allows ICMP echo requests. So even if the firewall is enabled you will still get a response from the server.
                Also, by default, ICS and Windows firewall are turned off on 2K3. They must be manually installed & enabled.

                Comment


                • #9
                  Re: Problem joining the domain

                  Really apreciated the help!!

                  I have just reinstalled the server and aplied just the tutorial bellowstill with the same problem.

                  There is no firewall, on both server and workstation. And my server canīt even access the workstations trought windows explorer typing "\\machine" or "\\xx.xx.xx.xx", but i can ping then by ip!

                  I think there might be a problem with netbios on the server, since i canīt ping the machines by name.

                  What are you using for a gateway? Can you have that hand out DHCP? Can you access the internet from the server console?
                  I on an university LAN, so there is already a domain controler on the network witch i will completely ignore. The gateway is done trought the university server.

                  There is no dhcp option since I am already on another network, and i donīt want to start give ips to someone elses computer.

                  Yes, i can access internet.

                  When trying to join a Windows 2003 domain do not use .com, .net, or .local. Use only the domain name itself, in this case domain, leave out .com
                  It didnt worked. The diference is that with the .local, is asks for a password and then reports the error, and with the domain name itself it reports the error right away.

                  Thanks again! You guys have been very supportive!

                  Comment


                  • #10
                    Re: Problem joining the domain

                    Run netdiag and dcdiag on the server and note any errors or post the results here.
                    Regards,
                    Jeremy

                    Network Consultant/Engineer
                    Baltimore - Washington area and beyond
                    www.gma-cpa.com

                    Comment


                    • #11
                      Re: Problem joining the domain

                      NetDiag

                      ....................................

                      Computer Name: FARM
                      DNS Host Name: farm.flockin.local
                      System info : Microsoft Windows Server 2003 R2 (Build 3790)
                      Processor : x86 Family 15 Model 47 Stepping 2, AuthenticAMD
                      List of installed hotfixes :
                      KB907265
                      Q147222


                      Netcard queries test . . . . . . . : Passed



                      Per interface results:

                      Adapter : Local Area Connection

                      Netcard queries test . . . : Passed

                      Host Name. . . . . . . . . : farm
                      IP Address . . . . . . . . : 10.90.150.90
                      Subnet Mask. . . . . . . . : 255.255.254.0
                      Default Gateway. . . . . . : 10.90.150.1
                      Dns Servers. . . . . . . . : 127.0.0.1


                      AutoConfiguration results. . . . . . : Passed

                      Default gateway test . . . : Passed


                      WINS service test. . . . . : Skipped
                      There are no WINS servers configured for this interface.


                      Global results:


                      Domain membership test . . . . . . : Passed


                      NetBT transports test. . . . . . . : Failed
                      List of NetBt transports currently configured:
                      [FATAL] Unable to retrieve transport list from Redir. [ERROR_NETWORK_UNREACH
                      ABLE]


                      Autonet address test . . . . . . . : Passed


                      IP loopback ping test. . . . . . . : Passed


                      Default gateway test . . . . . . . : Passed


                      NetBT name test. . . . . . . . . . : Failed
                      [FATAL] Failed to read NBT interface info from the registry.


                      Winsock test . . . . . . . . . . . : Passed


                      DNS test . . . . . . . . . . . . . : Passed
                      PASS - All the DNS entries for DC are registered on DNS server '127.0.0.1'.


                      Redir and Browser test . . . . . . : Failed
                      List of NetBt transports currently bound to the Redir
                      [FATAL] Unable to retrieve transport list from Redir. [ERROR_NETWORK_UNREACH
                      ABLE]

                      List of NetBt transports currently bound to the browser
                      [FATAL] The browser isn't bound to any NetBt transports.
                      [FATAL] Cannot send mailslot message to '\\FLOCKIN*\MAILSLOT\NET\NETLOGON' v
                      ia redir. [ERROR_NETWORK_UNREACHABLE]


                      DC discovery test. . . . . . . . . : Passed


                      DC list test . . . . . . . . . . . : Passed


                      Trust relationship test. . . . . . : Skipped


                      Kerberos test. . . . . . . . . . . : Passed


                      LDAP test. . . . . . . . . . . . . : Passed


                      Bindings test. . . . . . . . . . . : Passed


                      WAN configuration test . . . . . . : Skipped
                      No active remote access connections.


                      Modem diagnostics test . . . . . . : Passed

                      IP Security test . . . . . . . . . : Skipped

                      Note: run "netsh ipsec dynamic show /?" for more detailed information


                      The command completed successfully


                      dcdiag

                      Domain Controller Diagnosis

                      Performing initial setup:
                      Done gathering initial info.

                      Doing initial required tests

                      Testing server: Default-First-Site-Name\FARM
                      Starting test: Connectivity
                      ......................... FARM passed test Connectivity

                      Doing primary tests

                      Testing server: Default-First-Site-Name\FARM
                      Starting test: Replications
                      ......................... FARM passed test Replications
                      Starting test: NCSecDesc
                      ......................... FARM passed test NCSecDesc
                      Starting test: NetLogons
                      [FARM] An net use or LsaPolicy operation failed with error 1231, The ne
                      twork location cannot be reached. For information about network troubleshooting,
                      see Windows Help..
                      ......................... FARM failed test NetLogons
                      Starting test: Advertising
                      ......................... FARM passed test Advertising
                      Starting test: KnowsOfRoleHolders
                      ......................... FARM passed test KnowsOfRoleHolders
                      Starting test: RidManager
                      ......................... FARM passed test RidManager
                      Starting test: MachineAccount
                      Could not open pipe with [FARM]:failed with 1231: The network location
                      cannot be reached. For information about network troubleshooting, see Windows He
                      lp.
                      Could not get NetBIOSDomainName
                      Failed can not test for HOST SPN
                      Failed can not test for HOST SPN
                      * Missing SPN null)
                      * Missing SPN null)
                      ......................... FARM failed test MachineAccount
                      Starting test: Services
                      Could not open Remote ipc to [FARM]:failed with 1231: The network locat
                      ion cannot be reached. For information about network troubleshooting, see Window
                      s Help.
                      ......................... FARM failed test Services
                      Starting test: ObjectsReplicated
                      ......................... FARM passed test ObjectsReplicated
                      Starting test: frssysvol
                      [FARM] An net use or LsaPolicy operation failed with error 1231, The ne
                      twork location cannot be reached. For information about network troubleshooting,
                      see Windows Help..
                      ......................... FARM failed test frssysvol
                      Starting test: frsevent
                      ......................... FARM failed test frsevent
                      Starting test: kccevent
                      Failed to enumerate event log records, error The network location canno
                      t be reached. For information about network troubleshooting, see Windows Help.
                      ......................... FARM failed test kccevent
                      Starting test: systemlog
                      Failed to enumerate event log records, error The network location canno
                      t be reached. For information about network troubleshooting, see Windows Help.
                      ......................... FARM failed test systemlog
                      Starting test: VerifyReferences
                      ......................... FARM passed test VerifyReferences

                      Running partition tests on : ForestDnsZones
                      Starting test: CrossRefValidation
                      ......................... ForestDnsZones passed test CrossRefValidation

                      Starting test: CheckSDRefDom
                      ......................... ForestDnsZones passed test CheckSDRefDom

                      Running partition tests on : DomainDnsZones
                      Starting test: CrossRefValidation
                      ......................... DomainDnsZones passed test CrossRefValidation

                      Starting test: CheckSDRefDom
                      ......................... DomainDnsZones passed test CheckSDRefDom

                      Running partition tests on : Schema
                      Starting test: CrossRefValidation
                      ......................... Schema passed test CrossRefValidation
                      Starting test: CheckSDRefDom
                      ......................... Schema passed test CheckSDRefDom

                      Running partition tests on : Configuration
                      Starting test: CrossRefValidation
                      ......................... Configuration passed test CrossRefValidation
                      Starting test: CheckSDRefDom
                      ......................... Configuration passed test CheckSDRefDom

                      Running partition tests on : flockin
                      Starting test: CrossRefValidation
                      ......................... flockin passed test CrossRefValidation
                      Starting test: CheckSDRefDom
                      ......................... flockin passed test CheckSDRefDom

                      Running enterprise tests on : flockin.local
                      Starting test: Intersite
                      ......................... flockin.local passed test Intersite
                      Starting test: FsmoCheck
                      ......................... flockin.local passed test FsmoCheck

                      By the log i believe there is something wrong with my netbios service. At the event viewer i got the following error:

                      Error, Source: NetBT, ID: 4311
                      Initialization failed because the driver device could not be created.

                      Just a question? Shoud i enable netbios over TCP?

                      About wins? its the systems that stands for names in windows enviroments right? By the tutorial i've followed, it says to put the server ip as the primary wins, but i didn't had any wins server running on my server, witch i have installed just a moment ago. But as i try to manage it trought the Administrative tool i got the following error:
                      "The WINS server you especified cannot be located ..... The error was: The network path was not found" FARM[10.90.150.90]

                      Thanks again!

                      Comment


                      • #12
                        Re: Problem joining the domain

                        Yes, enable NetBIOS over TCP/IP. Run netdiag again and note any errors.
                        Regards,
                        Jeremy

                        Network Consultant/Engineer
                        Baltimore - Washington area and beyond
                        www.gma-cpa.com

                        Comment


                        • #13
                          Re: Problem joining the domain

                          Netbios is enabled trought the TCP in the GUI configuration, but it's not showing on the ipconfig
                          Windows IP Configuration

                          Host Name . . . . . . . . . . . . : farm
                          Primary Dns Suffix . . . . . . . : flockin.local
                          Node Type . . . . . . . . . . . . : Unknown
                          IP Routing Enabled. . . . . . . . : No
                          WINS Proxy Enabled. . . . . . . . : No
                          DNS Suffix Search List. . . . . . : flockin.local

                          Ethernet adapter Local Area Connection:

                          Connection-specific DNS Suffix . :
                          Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
                          Physical Address. . . . . . . . . : 00-15-F2-C2-86-31
                          DHCP Enabled. . . . . . . . . . . : No
                          IP Address. . . . . . . . . . . . : 10.90.150.90
                          Subnet Mask . . . . . . . . . . . : 255.255.254.0
                          Default Gateway . . . . . . . . . : 10.90.150.1
                          DNS Servers . . . . . . . . . . . : 127.0.0.1
                          NetBIOS over Tcpip. . . . . . . . : Disabled

                          And is causing an error on the event viewer:
                          Error, Source: NetBT, ID: 4311
                          Initialization failed because the driver device could not be created.

                          Any clue? What is odd is that it is a fresh windows server instalation.

                          Thanks!

                          Comment


                          • #14
                            Re: Problem joining the domain

                            I would install the latest drivers for your NIC.
                            You also might want to check to see if your hardware is listed here
                            http://www.windowsservercatalog.com/
                            Regards,
                            Jeremy

                            Network Consultant/Engineer
                            Baltimore - Washington area and beyond
                            www.gma-cpa.com

                            Comment


                            • #15
                              Re: Problem joining the domain

                              Never liked the Rhine II cards.

                              Why is the DNS set to the loopback IP? (127.0.0.1)
                              1 1 was a racehorse.
                              2 2 was 1 2.
                              1 1 1 1 race 1 day,
                              2 2 1 1 2

                              Comment

                              Working...
                              X