navmatt
asked on
Cannot Connect to SBS2003 Domain
My problem is on a SBS2003 sp1 network. All clients are XP Pro sp2.
One machine started having Synchronization issues with offline files. It also lost connection with the Exchange portion of SBS. I disconnected it from the domain under the local admin, renamed the machine, renamed the SBS client directory, and deleted the old machine from the server then attempted to reconnect to the domain via http://servername/connectcomputer.
I recieve this error message after I enter my username and password:
The list of users and computers cannot be found. Be sure you computer has a wired connection, dns is configured correctly etc.
I can connect to the internet just fine. DHCP is working correcty as far as I can tell, DNS appears to be ok, most of the other clients are connecting just fine. This started on a single machine and has since spread to one more. I have tried replacing the NIC in one machine as well as reseting TCP/IP and reinstalling TCP/IP.
I attempted to join the domain manually and recieve this message:
A Domain controller for the domain could not be contacted
-Details-
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.tx t.
DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain foxmanagementinc.local:
The query was for the SRV record for _ldap._tcp.dc._msdcs.foxma nagementin c.local
The following domain controllers were identified by the query:
george.foxmanagementinc.lo cal
Common causes of this error include:
- Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the network or are not running.
The A records appear to be configuared properly and the DC is connected to the network and is running as evidenced by the working clients.
I can ping the server both via it's IP and it's FQDN.
ipconfig /all for the client that cannot connect:
Windows IP Configuration
Host Name . . . . . . . . . . . . : stephanie01
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : FoxManagementInc.local
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . : FoxManagementInc.local
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Cont
roller
Physical Address. . . . . . . . . : 00-0F-1F-48-5E-CA
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.0.110
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 10.0.0.1
Primary WINS Server . . . . . . . : 10.0.0.1
Lease Obtained. . . . . . . . . . : Thursday, March 01, 2007 3:22:41 PM
Lease Expires . . . . . . . . . . : Friday, March 09, 2007 3:22:41 PM
Thanks in advance.
One machine started having Synchronization issues with offline files. It also lost connection with the Exchange portion of SBS. I disconnected it from the domain under the local admin, renamed the machine, renamed the SBS client directory, and deleted the old machine from the server then attempted to reconnect to the domain via http://servername/connectcomputer.
I recieve this error message after I enter my username and password:
The list of users and computers cannot be found. Be sure you computer has a wired connection, dns is configured correctly etc.
I can connect to the internet just fine. DHCP is working correcty as far as I can tell, DNS appears to be ok, most of the other clients are connecting just fine. This started on a single machine and has since spread to one more. I have tried replacing the NIC in one machine as well as reseting TCP/IP and reinstalling TCP/IP.
I attempted to join the domain manually and recieve this message:
A Domain controller for the domain could not be contacted
-Details-
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.tx
DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain foxmanagementinc.local:
The query was for the SRV record for _ldap._tcp.dc._msdcs.foxma
The following domain controllers were identified by the query:
george.foxmanagementinc.lo
Common causes of this error include:
- Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the network or are not running.
The A records appear to be configuared properly and the DC is connected to the network and is running as evidenced by the working clients.
I can ping the server both via it's IP and it's FQDN.
ipconfig /all for the client that cannot connect:
Windows IP Configuration
Host Name . . . . . . . . . . . . : stephanie01
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : FoxManagementInc.local
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . : FoxManagementInc.local
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Cont
roller
Physical Address. . . . . . . . . : 00-0F-1F-48-5E-CA
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.0.110
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 10.0.0.1
Primary WINS Server . . . . . . . : 10.0.0.1
Lease Obtained. . . . . . . . . . : Thursday, March 01, 2007 3:22:41 PM
Lease Expires . . . . . . . . . . : Friday, March 09, 2007 3:22:41 PM
Thanks in advance.
ASKER
All machines are on the 255.255.255.0 subnet.
http://10.0.0.1 has the same effect as http://servername, DNS resolution to IP does not seem to be an issue.
http://10.0.0.1 has the same effect as http://servername, DNS resolution to IP does not seem to be an issue.
Can you post an ipconfig/all of the server.
There have been some reported issues with integrated Broadcom NIC. Have you tried to update your NIC drivers?
There have been some reported issues with integrated Broadcom NIC. Have you tried to update your NIC drivers?
ASKER
Windows IP Configuration
Host Name . . . . . . . . . . . . : george
Primary Dns Suffix . . . . . . . : FoxManagementInc.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : FoxManagementInc.local
Ethernet adapter Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-04-23-CA-4D-36
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 10.0.0.1
NetBIOS over Tcpip. . . . . . . . : Disabled
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Generic Marvell Yukon Chipset based Gigab
it Ethernet Controller
Physical Address. . . . . . . . . : 00-04-23-CA-4D-37
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 10.0.0.1
Primary WINS Server . . . . . . . : 10.0.0.1
No broadcom NIC, but I haven't updated the existing NIC drivers either. To my thinking if there was a problem with the NIC drivers the problem would be global, not just specific to a couple machines.
Host Name . . . . . . . . . . . . : george
Primary Dns Suffix . . . . . . . : FoxManagementInc.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : FoxManagementInc.local
Ethernet adapter Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-04-23-CA-4D-36
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 10.0.0.1
NetBIOS over Tcpip. . . . . . . . : Disabled
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Generic Marvell Yukon Chipset based Gigab
it Ethernet Controller
Physical Address. . . . . . . . . : 00-04-23-CA-4D-37
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 10.0.0.1
Primary WINS Server . . . . . . . : 10.0.0.1
No broadcom NIC, but I haven't updated the existing NIC drivers either. To my thinking if there was a problem with the NIC drivers the problem would be global, not just specific to a couple machines.
there is no DHCP server in 10.x.x.x network but in xp configuration it is entered.
please reconfigure the ip configuration for xp machine
please reconfigure the ip configuration for xp machine
sorry there is some confusion. please cross check ip configuration in question and the last comment
specifically DHCP address
specifically DHCP address
sorry again. my first comment was right. I confused :(
Make sure your sbs server is the ONLY dhcp server in your network.
Make sure the clients get their dhcp info from the server.
As I can see in your ipconfigs the server has NO dhcp and still the clients have the sbs server as their dhcp server .... ??
Rerun the 'connect to the internet wizard', and make sure you enable dhcp on the server.
Maybe you will have to readd the clients via the http://server/connectcomputer if the problem isn't solved.
Make sure the clients get their dhcp info from the server.
As I can see in your ipconfigs the server has NO dhcp and still the clients have the sbs server as their dhcp server .... ??
Rerun the 'connect to the internet wizard', and make sure you enable dhcp on the server.
Maybe you will have to readd the clients via the http://server/connectcomputer if the problem isn't solved.
ASKER
The DHCP is configured on the serverfor the 10.x.x.x scope. It is the only DHCP server on the network. Both IPs on the server are set to static, but the dhcp server seems to be working as all the clients get their IPs from it.
suppsaws: The problem is that I can't re-add clients via http://servername/connectcomputer
suppsaws: The problem is that I can't re-add clients via http://servername/connectcomputer
I've been re-reading your post and the only thing I can think of is that something didn't go right when you put the client back into the workgroup and then tried to rejoin it.
Log on to the computer locally, not uisng the domain name, as a local adminsitrator.
Start> Control Pane>System >Computer Name >Change and join a workgroup. You should get a message that you have successfully joined a workgroup. Reboot, Log on locally with an account that has administrator permissions. Check ipconfig/all It should be different then the one you posted earlier.
Delete ths computer name from the server. Add the computer name back to the server.
Try to run http:.//servername/connectcomputer again.
Log on to the computer locally, not uisng the domain name, as a local adminsitrator.
Start> Control Pane>System >Computer Name >Change and join a workgroup. You should get a message that you have successfully joined a workgroup. Reboot, Log on locally with an account that has administrator permissions. Check ipconfig/all It should be different then the one you posted earlier.
Delete ths computer name from the server. Add the computer name back to the server.
Try to run http:.//servername/connectcomputer again.
ASKER
I've done that several times, into different workgroups and different names with no results. I'll try it again and check the ipconfig /all
any other ideas?
any other ideas?
ASKER
Ok, renamed computer to new name, joined workgroup "WORKGROUP", restarted
ipconfig /all comes back the same
ipconfig /all comes back the same
ASKER
I'll add another twist, my laptop connects to the domain via the http://servername/connectcomputer wizard.
Is it time to wipe and reinstall the machines I'm haveing problems with?
Is it time to wipe and reinstall the machines I'm haveing problems with?
Before you wipe it, change the NIC and disable DHCP. Manually put in the IP address above:
IP Address. . . . . . . . . . . . : 10.0.0.110
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 10.0.0.1
Primary WINS Server . . . . . . . : 10.0.0.1
and try ipconfig /flushdns on the server and the client.
IP Address. . . . . . . . . . . . : 10.0.0.110
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 10.0.0.1
Primary WINS Server . . . . . . . : 10.0.0.1
and try ipconfig /flushdns on the server and the client.
ASKER
Ok changed the NIC and entered IP manually, no go, when I go to http://servername/connectcomputer the page has an error and says permission denied.
If I let DHCP assign the IP, i get a different IP but run into the same error from the first post.
If I let DHCP assign the IP, i get a different IP but run into the same error from the first post.
Use the IP you get form DHCP, but manually put it in with DHCP turned off. The reason I am saying to fiddle around with manually putting in the IP is because on several occasions I ran into the exact same issue. And, forwhatever reason, once I got it to go with manually putting in the IP, I could switch back to DHCP. This might not work in your instance. You might get tired of this and just wipe it.
ASKER
Running a repair from the XP disc now to see if that has any effect. I'll attempt the new manual IP settings again if that doesn't work
ASKER
XP repair didn't help, no go on the manual IP settings either, trying a clean install
ASKER
A clean install solved the problem.
If anyone has any idea what could cause this I'd appreciate theories.
Thanks for all your help!
If anyone has any idea what could cause this I'd appreciate theories.
Thanks for all your help!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
you are using class A network address and the subnet mask refers to Class C
If it is subnetted in your organization, please check the same on server also
you can try the same link i.e. http://servername/connectcomputer but instead of servername try using ip address i.e. http://10.0.0.1/connectcomputer