Weird issue trying to get a laptop to join domain

[sshrum]

(I'm almost sure the issue is with the client PC but I figured I post here just in case)

I have a laptop running WinXP Pro SP3 that was joined to the domain but was unable to 'browse' any of the server resources.

Figuring the issue was a trust relationship issue, I decided to just rejoin it to the domain.

Now when I attempt to join the domain I get error messages of "connection lost" on a hard wired connection.

I went over to the server and deleted the computer name out of AD and when I tried to join the laptop to the domain I get a different error. If I manually create the computer name back in I get the first error msg again so I know that the laptop and server are kinda talking.

I can ping the server by name and IP....I just can't browse it from this laptop. Other PCs on the network can see the server just fine.

I ran WinSockFix (just in case) but still no go.

Here is the netsetup.log after I attempted to rejoin from the laptop:

======================
netsetup.log

09/11 11:34:49
-----------------------------------------------------------------
09/11 11:34:49 NetpDoDomainJoin
09/11 11:34:49 NetpMachineValidToJoin: 'SPLTXP3'
09/11 11:34:49 NetpGetLsaPrimaryDomain: status: 0x0
09/11 11:34:49 NetpMachineValidToJoin: status: 0x0
09/11 11:34:49 NetpJoinDomain
09/11 11:34:49 Machine: SPLTXP3
09/11 11:34:49 Domain: sp
09/11 11:34:49 MachineAccountOU: (NULL)
09/11 11:34:49 Account: sp\*********
09/11 11:34:49 Options: 0x25
09/11 11:34:49 OS Version: 5.1
09/11 11:34:49 Build number: 2600
09/11 11:34:49 ServicePack: Service Pack 3
09/11 11:34:49 NetpValidateName: checking to see if 'sp' is valid as type
3 name
09/11 11:34:49 NetpCheckDomainNameIsValid [ Exists ] for 'sp' returned 0x0
09/11 11:34:49 NetpValidateName: name 'sp' is valid for type 3
09/11 11:34:49 NetpDsGetDcName: trying to find DC in domain 'sp', flags:
0x1020
09/11 11:34:49 NetpDsGetDcName: found DC '\\SPDC' in the specified domain
09/11 11:34:49 NetUseAdd to \\SPDC\IPC$ returned 1214
09/11 11:34:49 NetpJoinDomain: status of connecting to dc '\\SPDC': 0x4be
09/11 11:34:49 NetpDoDomainJoin: status: 0x4be
09/11 11:34:49
-----------------------------------------------------------------
09/11 11:34:49 NetpDoDomainJoin
09/11 11:34:49 NetpMachineValidToJoin: 'SPLTXP3'
09/11 11:34:49 NetpGetLsaPrimaryDomain: status: 0x0
09/11 11:34:49 NetpMachineValidToJoin: status: 0x0
09/11 11:34:49 NetpJoinDomain
09/11 11:34:49 Machine: SPLTXP3
09/11 11:34:49 Domain: sp
09/11 11:34:49 MachineAccountOU: (NULL)
09/11 11:34:49 Account: sp\*********
09/11 11:34:49 Options: 0x27
09/11 11:34:49 OS Version: 5.1
09/11 11:34:49 Build number: 2600
09/11 11:34:49 ServicePack: Service Pack 3
09/11 11:34:49 NetpValidateName: checking to see if 'sp' is valid as type
3 name
09/11 11:34:49 NetpCheckDomainNameIsValid [ Exists ] for 'sp' returned 0x0
09/11 11:34:49 NetpValidateName: name 'sp' is valid for type 3
09/11 11:34:49 NetpDsGetDcName: trying to find DC in domain 'sp', flags:
0x1020
09/11 11:34:49 NetpDsGetDcName: found DC '\\SPDC' in the specified domain
09/11 11:34:49 NetUseAdd to \\SPDC\IPC$ returned 1214
09/11 11:34:49 NetpJoinDomain: status of connecting to dc '\\SPDC': 0x4be
09/11 11:34:49 NetpDoDomainJoin: status: 0x4be

=====================

Any ideas?

TIA

 

[GrimR]

I would remove it from the domain to a workgroup. Delete the computer account from AD. Make sure you replicate the change if you adding it back with the same name.[not suggested]
On the laptop in the nic add a static IP and DNS, and rejoin it to the domain.


MCITP:EA/SA, MCSE, MCSA, MCDBA, MCTS, MCP+I, MCP

 

[sshrum]

No good.

I assigned a static IP to the laptop, tested connectivity via pings, manually added the computer name into AD and attempted to join and got:

> The following error occured attempting to join the domain "sp":
> The format of the speciied network name is invalid

I then manually removed the computer name from ad, attempted to join and got this:

> The following error occured attempting to join domain "sp":
> The network location cannot be reached. For information about network troubleshooting, see Windows Help

Any other ideas? I'm on the verge of just rebuilding the laptop but I'm not 100% sure the issue is just client related.

 

[GrimR]

Can you ping the DC by it's name, to make sure DNS is working.
Set your primary DNS to the IP of your DC on the NIC.
Do not add the PC to AD directly instead can you not add the PC via the Network Identification Wizard.

MCITP:EA/SA, MCSE, MCSA, MCDBA, MCTS, MCP+I, MCP

 

[sshrum]

The laptop started BSoD'ing so I just reimaged and crossed my fingers

Everything is set to dhcp (like before) and I'm now able to join the domain (using the original PC name).

Dx: Something was f-ed up on the laptop.

I would have loved to figure out what it was but this was a client PC that needed to get back in the field pronto.

Thanks again for the assistance.