Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Rendom /Prepare failed to bind to server error 1753

Status
Not open for further replies.

GeeBee2010

IS-IT--Management
Jun 14, 2010
2
IE
I have 4 DCs which all return this error:

Failed to bind to server "servername": 1753

All steps of the rendom process completed up to this.

I have checked dcdiag, netdiag, repadmin without success.

Can anyone shed some light on what i am missing.

the servers are 2003 SP2 and i am running redom from another 2003 sp2 box. 2 of the target dcs are in the same subnet and 2 in remote subnets.

The reason for attempting this rename is because the company netbios name has an ampersand (&) in the name.
DNS resolution is working perfectly and i get no errors at all in the event viewer. I have read just about every scrap of information i can find to no avail.

all help much appreciated.

 
Futher information: error message received is :
Failed to Bind to server server1.fqdn : 1753.
Failed to Bind to server server2.fqdn : 1753.
Failed to Bind to server server3.fqdn : 1753.
Failed to Bind to server server4.fqdn : 1753.
Waiting for DCs to reply.
4 servers contacted, 4 servers returned Errors
The operation completed successfully.

There are no errors in the event viewer that seem to relate to this. I am stuck at rendom /prepare

I have heard that possibly changing the RPC service to use a localsystem account instaed of the network service can help but am unsure about this as it could set off other issues such as DCOM? all help much appreciated
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top