Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Have domain running on windows 2000 server.
When try to connect to the domain with a windows 2000 professional machine it states " Your computer could not be joined to the domain because the following error has occurred: The network path was not found."
Please help, I can supply more information.
G
Hi ya,
The pc can't see the domain, could be one of many things!!
Is the NIC installed ok? are u using DHCP or have u got a static IP? can you ping any of the other clients of the network?
More info would be good!
Cheers
0 
Using DHCP.
Network is fine, I can browse the server from the client machine. But cannot connect to the domain?!
0
DNS problem, check the tcp/ip settings and look for DNS server address(s), this needs to be a DNS server that is responsible for the domain you are trying to join, (the windows professional PC needs DNS to find an SRV record for the nearest domain controller)
0
Sounds like you are connected as a workgroup. If you remove from the network and rejoin does this still happen? Also, make sure you have the right primary dns suffix in the network identification. I've had problems similar but that was with duplicate sids and a different go around as well.
0
Using SMC Barricade ADSL router.
Currenty all machines get their IP's from this.
Do I need static IP's?
0
On the 2000 prof machine, get a command prompt and run "ipconfig /all" without the quotes, see what is listed for DNS servers
0
10/30 15:41:41 NetpDoDomainJoin
10/30 15:41:41 NetpMachineValidToJoin: 'GOLIATH'
10/30 15:41:41 NetpGetLsaPrimaryDomain: status: 0x0
10/30 15:41:41 NetpMachineValidToJoin: status: 0x0
10/30 15:41:41 NetpJoinDomain
10/30 15:41:41 Machine: GOLIATH
10/30 15:41:41 Domain: SERVERDOMAIN
10/30 15:41:41 MachineAccountOU: (NULL)
10/30 15:41:41 Account: SERVERDOMAIN\Administrator
10/30 15:41:41 Options: 0x23
10/30 15:41:41 OS Version: 5.0
10/30 15:41:41 Build number: 2195
10/30 15:41:41 NetpValidateName: checking to see if 'SERVERDOMAIN' is valid as type 3 name
10/30 15:41:41 NetpCheckDomainNameIsValid [ Exists ] for 'SERVERDOMAIN' returned 0x0
10/30 15:41:41 NetpValidateName: name 'SERVERDOMAIN' is valid for type 3
10/30 15:41:41 NetpDsGetDcName: trying to find DC in domain 'SERVERDOMAIN', flags: 0x1020
10/30 15:41:56 NetpDsGetDcName: failed to find a DC having account 'GOLIATH$': 0x525
10/30 15:41:56 NetpDsGetDcName: found DC '\\euclid.serverdomain' in the specified domain
10/30 15:41:56 NetUseAdd to \\euclid.serverdomain\IPC$ returned 53
10/30 15:41:56 NetpJoinDomain: status of connecting to dc '\\euclid.serverdomain': 0x35
10/30 15:41:56 NetpDoDomainJoin: status: 0x35All seems OK doesn't it?
0
Go into your DNS properties and expand Forward Lookup Zones
Right click _tcp
Choose > Add other record
Type = SRV
Service = ldap
port = 389
host offering this service = your domain controller IP address.
Try adding W2K Pro to domain now. You owe me a beer! :)
0
hello i have the same problem with my Win XP pro on my school's network, it uses a SHCP server and when i try to change my network id to that of the shcool it gives me the error message!!
thanks
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
