win2k3 sbs one client refuses to connect to domain

harleyx · 04-26-2008, 01:35 PM

Hey everybody,

I stepped into a situation with a company whose computers were quite screwed up. I've fixed and setup work arounds for all the problems but one.

The windows 2003 server runs ok. There are three client computers (the bosses, the secretary's, and this one I'm working on now). Two of the client computers work just fine, they connect to the domain no problems.

The computer I'm currently stuck on (that I reloaded with WinXp Pro & SP2) refuses to log on to the domain. I setup the client with the domain, which refused to work for a while but finally took. I got alot of "The RPC server is unavailable" messages while trying to get the domain to take. It finally did take.

The reloaded computer has no firewalls running, and all the network settings are default/automatic and I've verified they match the other two client computers exactly. I get this message when trying to logon to the domain from the client computer:

"Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable...."

There is a 4 port router which I've checked the settings on. It's setup with the static IP address and DHCP/etc disabled, and controlled by the server, as it should be. No IP's are blocked, nothing seems amiss there.

The reloaded machine has no firewalls running, not even windows firewall.

The server can ping the client by name and IP, and the client can ping the server by name but not by IP.

I know the logon being used is good because it works fine with the other client computers, and I've checked it on the server to make sure there are no access restrictions setup.

The newly reloaded computer doesn't automatically appear in the computers listing on the server. I can add it manually, but I always thought those were supposed to be added automatically, when you would define the domain on the new client.

The strange thing is, when I logon to the computers local user account, I can go into network places and connect to the company's shared files (//<folder>/Company), and it will ask for a domain login, which I'll give and it will take no problem.

What could be causing this refusal to login to the domain?

Thanks in advance.

Jay Ell · 04-28-2008, 07:57 AM

I am having exactly the same problem except the DNS is 2000 server, client is XP and I am trying to connect over a WAN. Router VPNs (cisco 1800 at client, 3800 at Head Office). All the other locations work OK but this one site doesnt. Same error messages. Ping tests work ok. Can access internet via HO connection but would not join to the domain. I have tried everything except changing out the router at the client site. Really need help here!!

04-26-2008, 01:35 PM	#1 (permalink)
harleyx Registered User Join Date: Apr 2008 Posts: 1 OS: xp pro ver 2002 sp2	win2k3 sbs one client refuses to connect to domain Hey everybody, I stepped into a situation with a company whose computers were quite screwed up. I've fixed and setup work arounds for all the problems but one. The windows 2003 server runs ok. There are three client computers (the bosses, the secretary's, and this one I'm working on now). Two of the client computers work just fine, they connect to the domain no problems. The computer I'm currently stuck on (that I reloaded with WinXp Pro & SP2) refuses to log on to the domain. I setup the client with the domain, which refused to work for a while but finally took. I got alot of "The RPC server is unavailable" messages while trying to get the domain to take. It finally did take. The reloaded computer has no firewalls running, and all the network settings are default/automatic and I've verified they match the other two client computers exactly. I get this message when trying to logon to the domain from the client computer: "Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable...." There is a 4 port router which I've checked the settings on. It's setup with the static IP address and DHCP/etc disabled, and controlled by the server, as it should be. No IP's are blocked, nothing seems amiss there. The reloaded machine has no firewalls running, not even windows firewall. The server can ping the client by name and IP, and the client can ping the server by name but not by IP. I know the logon being used is good because it works fine with the other client computers, and I've checked it on the server to make sure there are no access restrictions setup. The newly reloaded computer doesn't automatically appear in the computers listing on the server. I can add it manually, but I always thought those were supposed to be added automatically, when you would define the domain on the new client. The strange thing is, when I logon to the computers local user account, I can go into network places and connect to the company's shared files (//<folder>/Company), and it will ask for a domain login, which I'll give and it will take no problem. What could be causing this refusal to login to the domain? Thanks in advance.

04-28-2008, 07:57 AM	#2 (permalink)
Jay Ell Registered User Join Date: Apr 2008 Posts: 1 OS: XP	Re: win2k3 sbs one client refuses to connect to domain I am having exactly the same problem except the DNS is 2000 server, client is XP and I am trying to connect over a WAN. Router VPNs (cisco 1800 at client, 3800 at Head Office). All the other locations work OK but this one site doesnt. Same error messages. Ping tests work ok. Can access internet via HO connection but would not join to the domain. I have tried everything except changing out the router at the client site. Really need help here!!