Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 906
  • Last Modified:

Server cannot join a windows 2003 domain, "semaphore timeout"

I am trying to join a windows 2003 server 64 bit enterprise edition workstation  on a freshly installed vmware instance to a windows 2003 domain controller 64 bit enterprise edition. The domain controller is also a clean install on a physical server. Both servers are equally patched with service pack 2.
The workgroup server can ping the domain controller by ip and FQDN. ( a host file entry was also added to the workgroup server) I run steady pings on both machine, and there are no timeouts. I don't see anything in the windows event logs. After supplying the domain admin credentials during the domain join, the system hangs  and eventually gives the error message "semaphore timeout" . Microsoft has a few articles on this, which appear to hardware related - possible issues in the nic cards and network switches not auto-negotiatiating the correct port speed and duplex.  I tried manually changing these on both machines. I restarted the netlogon service on the domain controller. The dns entries on the dc are correct.


Any help is appreciated


0
bignewf
Asked:
bignewf
1 Solution
 
MikeKaneCommented:
Funny as it sounds...   I've seen this a few times.  

This has worked for me:

On a domain server, install WINS services.   Add the WINS IP to the DHCP scope options or manually to the 2 devices.  

Reboot and then join the domain.  

Once you are joined, remove wins.  


0
 
bignewfAuthor Commented:
IT worked, but I had also added static entries in the hosts file on the machine that had issues.  So I wonder if it was wins or the static entries.

thanks for your great help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now