"The following error occurred atempting to join the domain: <domain_name>: The network path was not found"

My DC server is on external ip address. It is also the DNS.
My Fileserver1 is behind Cisco Adsl annex M router and has open ports 3389 (RD) and 443
My Fileserver2 is behind Noname Adsl router and has open ports 3389 (RS)

I had no problem adding Fileserver1 to my domain
But when I try to add Fileserver2  to my domain I get this error:

"The following error occurred atempting to join the domain: <domain_name>:
 The network path was not found"

Fileserver2 is using right DNS and is running DHCP just like Fileserver1
soffcecManagerAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Ben HartConnect With a Mentor Commented:
I wouldnt think that'd be related..
0
 
Ben HartCommented:
Did you use the short name or the FQDN?  Usually when I have this issue (randomly) by using the FQDN it works just fine.
0
 
soffcecManagerAuthor Commented:
Same thing happens if I try to add workstations who are on the same network as Fileserver2 to the domain.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
soffcecManagerAuthor Commented:
I did use the FQDN the computer could not resolve the short name.
0
 
soffcecManagerAuthor Commented:
When I try to join the machine to the domain I am prompted for credentials by the server, but the process never completes and ends with the 'network path not found' error.
0
 
Ben HartCommented:
I think you might need more port opened.. 53 to name one.  Can you nslookup your DC from FS2?
0
 
Ben HartCommented:
Are these servers, by chance, located in different places tied together over the internets?
0
 
soffcecManagerAuthor Commented:
nslookup is ok

Those server are all long way from each other. All behind different connections and different ISP's
But the DC and fileserver1 has no problem.
0
 
Ben HartCommented:
Do you have windows firewall running on the servers?  And the ports you listed are indeed the ONLY ones open for either file server?  The routers forming a VPN connection to the site with the dc?
0
 
soffcecManagerAuthor Commented:
I am not using VPN connection. I have disabled all firewalls

All ports are open on the DC but only port 3389 and 443 on fileserver1 and 3389 on fileserver2

I am using port forwarding for fileserver1 & 2
But the DC has it's own external ip address
0
 
soffcecManagerAuthor Commented:
Fileservers1 & 2 are running on local addresses 192.168.1.200 and 192.168.11.200
0
 
Ben HartCommented:
Point to point circuits?
0
 
soffcecManagerAuthor Commented:
?? Point to point circuits? If I understand you right then the answar is no.
There are no VPN or VLAN in this network.

I have several networks like this one running. But it is the first time I get error like this.
And as I said Fileserver1 did join the domain without any errors.
0
 
Ben HartCommented:
I fail to understand how your fileserver 1 joined successfully to a domain when the connection is just across the internet unsecured.. and with only those two ports open.  If nslookup worked then I highly doubt only RDP's port is open.  This situation just doesn't register with my brain.
0
 
soffcecManagerAuthor Commented:
Here is dcdiag from fileserver1

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests
   
   Testing server: Default-First-Site-Name\SAMHJALP-ADS
      Starting test: Connectivity
         ......................... SAMHJALP-ADS passed test Connectivity

Doing primary tests
   
   Testing server: Default-First-Site-Name\SAMHJALP-ADS
      Starting test: Replications
         ......................... SAMHJALP-ADS passed test Replications
      Starting test: NCSecDesc
         ......................... SAMHJALP-ADS passed test NCSecDesc
      Starting test: NetLogons
         ......................... SAMHJALP-ADS passed test NetLogons
      Starting test: Advertising
         ......................... SAMHJALP-ADS passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... SAMHJALP-ADS passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... SAMHJALP-ADS passed test RidManager
      Starting test: MachineAccount
         ......................... SAMHJALP-ADS passed test MachineAccount
      Starting test: Services
         ......................... SAMHJALP-ADS passed test Services
      Starting test: ObjectsReplicated
         ......................... SAMHJALP-ADS passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... SAMHJALP-ADS passed test frssysvol
      Starting test: frsevent
         ......................... SAMHJALP-ADS passed test frsevent
      Starting test: kccevent
         ......................... SAMHJALP-ADS passed test kccevent
      Starting test: systemlog
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 05/10/2013   13:35:26
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 05/10/2013   13:35:26
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 05/10/2013   13:54:40
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 05/10/2013   13:54:40
            (Event String could not be retrieved)
         ......................... SAMHJALP-ADS failed test systemlog
      Starting test: VerifyReferences
         ......................... SAMHJALP-ADS 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 : samhjalp
      Starting test: CrossRefValidation
         ......................... samhjalp passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... samhjalp passed test CheckSDRefDom
   
   Running enterprise tests on : samhjalp.ic
      Starting test: Intersite
         ......................... samhjalp.ic passed test Intersite
      Starting test: FsmoCheck
         Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1726
         A Good Time Server could not be located.
         ......................... samhjalp.ic failed test FsmoCheck

Open in new window

0
 
soffcecManagerAuthor Commented:
And here is dcdiag from fileserver2
Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests
   
   Testing server: Default-First-Site-Name\SAMHJALP-ADS
      Starting test: Connectivity
         ......................... SAMHJALP-ADS passed test Connectivity

Doing primary tests
   
   Testing server: Default-First-Site-Name\SAMHJALP-ADS
      Starting test: Replications
         ......................... SAMHJALP-ADS passed test Replications
      Starting test: NCSecDesc
         ......................... SAMHJALP-ADS passed test NCSecDesc
      Starting test: NetLogons
         [SAMHJALP-ADS] An net use or LsaPolicy operation failed with error 1203, Win32 Error 1203.
         ......................... SAMHJALP-ADS failed test NetLogons
      Starting test: Advertising
         Fatal Error:DsGetDcName (SAMHJALP-ADS) call failed, error 1722
         The Locator could not find the server.
         ......................... SAMHJALP-ADS failed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... SAMHJALP-ADS passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... SAMHJALP-ADS passed test RidManager
      Starting test: MachineAccount
         Could not open pipe with [SAMHJALP-ADS]:failed with 1203: Win32 Error 1203
         Could not get NetBIOSDomainName
         Failed can not test for HOST SPN
         Failed can not test for HOST SPN
         * Missing SPN :(null)
         * Missing SPN :(null)
         ......................... SAMHJALP-ADS failed test MachineAccount
      Starting test: Services
         Could not open Remote ipc to [SAMHJALP-ADS]:failed with 1203: Win32 Error 1203
         ......................... SAMHJALP-ADS failed test Services
      Starting test: ObjectsReplicated
         ......................... SAMHJALP-ADS passed test ObjectsReplicated
      Starting test: frssysvol
         [SAMHJALP-ADS] An net use or LsaPolicy operation failed with error 1203, Win32 Error 1203.
         ......................... SAMHJALP-ADS failed test frssysvol
      Starting test: frsevent
         ......................... SAMHJALP-ADS failed test frsevent
      Starting test: kccevent
         Failed to enumerate event log records, error Win32 Error 1203
         ......................... SAMHJALP-ADS failed test kccevent
      Starting test: systemlog
         Failed to enumerate event log records, error Win32 Error 1203
         ......................... SAMHJALP-ADS failed test systemlog
      Starting test: VerifyReferences
         ......................... SAMHJALP-ADS 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 : samhjalp
      Starting test: CrossRefValidation
         ......................... samhjalp passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... samhjalp passed test CheckSDRefDom
   
   Running enterprise tests on : samhjalp.ic
      Starting test: Intersite
         ......................... samhjalp.ic passed test Intersite
      Starting test: FsmoCheck
         Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1722
         A Global Catalog Server could not be located - All GC's are down.
         Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1722
         A Primary Domain Controller could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(TIME_SERVER) call failed, error 1722
         A Time Server could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1722
         A Good Time Server could not be located.
         Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1722
         A KDC could not be located - All the KDCs are down.
         ......................... samhjalp.ic failed test FsmoCheck

Open in new window

0
 
Ben HartCommented:
Im not doubting you that that one worked.. I just dont understand how it's working with the information provided :)
0
 
Ben HartCommented:
Post an unediting copy of ipconfig /all on fileserver2
0
 
soffcecManagerAuthor Commented:
Windows IP Configuration

   Host Name . . . . . . . . . . . . : kot
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
unediting copy of ipconfig /all on fileserver2
Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
   Physical Address. . . . . . . . . : 00-13-21-62-A6-8F
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.11.200
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.11.1
   DNS Servers . . . . . . . . . . . : 157.157.162.166

Open in new window

0
 
Ben HartCommented:
Populate your DNS suffix field on Fileserver2... also anything in the event logs on fileserver 2 when you attempt to join it?
0
 
soffcecManagerAuthor Commented:
Change primary DNS suffix when domain membership changes is selected
Primary DNS suffix of this computer is blank

Nothing is written to the event log after I try join domain.
0
 
Ben HartCommented:
What about in the event logs on the DC?  Are these boxes running Server 2008?
0
 
soffcecManagerAuthor Commented:
All boxes are Windows 2003 R2

This was the only error I found on the DC
Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=samhjalp,DC=ic. The file must be present at the location <\\samhjalp.ic\sysvol\samhjalp.ic\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied. ). Group Policy processing aborted. 

Open in new window

0
 
soffcecManagerAuthor Commented:
?
0
 
soffcecManagerAuthor Commented:
Soulution found.
The ISP had the port 445 blocked. When he did allow the port everything star working.
0
 
Ben HartCommented:
HA! I knew there had to be something that should be open but wasn't.  Glad you found it!
0
All Courses

From novice to tech pro — start learning today.