Re: rendom /prepare failed to bind to server

From: James <James@xxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 5 Feb 2009 05:27:13 -0800

I've also seen issues when not using the default Forest administrator
account. Maybe it is not in the Schema Admin group as well? Is the Schema
set to allow updates? Have you tried the default forest admin account just
to see if it works? If that doesn't work, I would then look to see if any
ports are being firewalled. THe original error you got was for port 1753,
and keep in mind, Schema changes must be made for a rename to work. Use
prtqry again to check for TCP and UDP 1753. Keep in mind about the empheral
response ports (1024 - 5000) which must also be opened.

Ace

The accounts are in the correct groups. I have run a port query and have
the following results:

portqry -n 44lonad04 -e 1753 -p both

Querying target system called:
44lonad04
Attempting to resolve name to IP address...
Name resolved to 10.1.1.33

TCP port 1753 (unknown service): NOT LISTENING
UDP port 1753 (unknown service): NOT LISTENING

On the server 44LONAD03 itself:

C:\>netstat -an |find /i "listening"
TCP 0.0.0.0:53 0.0.0.0:0 LISTENING
TCP 0.0.0.0:88 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:464 0.0.0.0:0 LISTENING
TCP 0.0.0.0:593 0.0.0.0:0 LISTENING
TCP 0.0.0.0:636 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1027 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1058 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1076 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1097 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3268 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3269 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:10000 0.0.0.0:0 LISTENING
TCP 10.1.1.33:139 0.0.0.0:0 LISTENING

C:\>netstat -an |find /i "established"
TCP 10.1.1.33:135 10.1.1.33:1171 ESTABLISHED
TCP 10.1.1.33:389 10.1.1.33:1060 ESTABLISHED
TCP 10.1.1.33:389 10.1.1.38:38253 ESTABLISHED
TCP 10.1.1.33:1025 10.1.1.13:1245 ESTABLISHED
TCP 10.1.1.33:1025 10.1.1.33:1063 ESTABLISHED
TCP 10.1.1.33:1025 10.1.1.33:1172 ESTABLISHED
TCP 10.1.1.33:1025 10.1.1.34:3588 ESTABLISHED
TCP 10.1.1.33:1025 10.1.1.34:3605 ESTABLISHED
TCP 10.1.1.33:1060 10.1.1.33:389 ESTABLISHED
TCP 10.1.1.33:1063 10.1.1.33:1025 ESTABLISHED
TCP 10.1.1.33:1100 10.1.1.34:1025 ESTABLISHED
TCP 10.1.1.33:1165 10.1.1.13:1025 ESTABLISHED
TCP 10.1.1.33:1171 10.1.1.33:135 ESTABLISHED
TCP 10.1.1.33:1172 10.1.1.33:1025 ESTABLISHED
TCP 10.1.1.33:1178 10.1.1.18:445 ESTABLISHED
TCP 10.1.1.33:1180 10.1.1.34:1025 ESTABLISHED
TCP 10.1.1.33:1181 10.1.1.13:1025 ESTABLISHED
TCP 10.1.1.33:3268 10.1.1.38:38136 ESTABLISHED
TCP 10.1.1.33:3268 10.1.1.38:38198 ESTABLISHED
TCP 10.1.1.33:3268 10.1.1.38:38202 ESTABLISHED
TCP 10.1.1.33:3268 10.1.1.38:38224 ESTABLISHED
TCP 10.1.1.33:3268 10.1.1.38:38245 ESTABLISHED
TCP 10.1.1.33:3268 10.1.1.38:38251 ESTABLISHED
TCP 10.1.1.33:3268 10.1.1.38:38263 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1046 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1050 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1051 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1096 ESTABLISHED
TCP 127.0.0.1:1046 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1050 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1051 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1096 127.0.0.1:389 ESTABLISHED

Checking endpoints on 44LONAD04 again:

portqry -n 44lonad04 -e 135

Querying target system called:

44lonad04

Attempting to resolve name to IP address...

Name resolved to 10.1.1.33

TCP port 135 (epmap service): LISTENING
Querying Endpoint Mapper Database...
Server's response:

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[DNSResolver]

UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncalrpc:[W32TIME_ALT]

UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncacn_np:\\\\44LONAD04[\\PIPE\\W32TIME_ALT]

UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076
ncacn_ip_tcp:10.1.1.33[1097]

UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncalrpc:[OLECC8EA1E34FDC49B481D6CD65B231]

UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncacn_ip_tcp:10.1.1.33[1076]

UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncalrpc:[DHCPSERVERLPC]

UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncalrpc:[OLECC8EA1E34FDC49B481D6CD65B231]

UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncacn_ip_tcp:10.1.1.33[1076]

UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncalrpc:[DHCPSERVERLPC]

UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[OLEB5FE5C457662489D9B73824987D2]

UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncacn_ip_tcp:10.1.1.33[1058]

UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[LRPC000006a0.00000001]

UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[OLEB5FE5C457662489D9B73824987D2]

UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncacn_ip_tcp:10.1.1.33[1058]

UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[LRPC000006a0.00000001]

UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[OLEB5FE5C457662489D9B73824987D2]

UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncacn_ip_tcp:10.1.1.33[1058]

UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[LRPC000006a0.00000001]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC00000484.00000001]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC00000484.00000001]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC00000484.00000001]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC00000484.00000001]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\44LONAD04[\\PIPE\\lsass]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[audit]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[securityevent]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[protected_storage]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\44LONAD04[\\PIPE\\protected_storage]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[dsrole]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:10.1.1.33[1025]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_np:\\\\44LONAD04[\\PIPE\\lsass]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[audit]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[securityevent]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[protected_storage]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_np:\\\\44LONAD04[\\PIPE\\protected_storage]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[dsrole]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_ip_tcp:10.1.1.33[1025]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_np:\\\\44LONAD04[\\PIPE\\lsass]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[audit]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[securityevent]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[protected_storage]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_np:\\\\44LONAD04[\\PIPE\\protected_storage]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[dsrole]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_ip_tcp:10.1.1.33[1025]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\44LONAD04[\\PIPE\\lsass]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[audit]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[securityevent]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[protected_storage]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\44LONAD04[\\PIPE\\protected_storage]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[dsrole]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_ip_tcp:10.1.1.33[1025]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[NTDS_LPC]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_http:10.1.1.33[1027]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_np:\\\\44LONAD04[\\PIPE\\lsass]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[audit]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[securityevent]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[protected_storage]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_np:\\\\44LONAD04[\\PIPE\\protected_storage]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[dsrole]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_ip_tcp:10.1.1.33[1025]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[NTDS_LPC]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_http:10.1.1.33[1027]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\44LONAD04[\\PIPE\\lsass]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[audit]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[securityevent]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[protected_storage]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\44LONAD04[\\PIPE\\protected_storage]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[dsrole]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_ip_tcp:10.1.1.33[1025]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[NTDS_LPC]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_http:10.1.1.33[1027]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\44LONAD04[\\PIPE\\lsass]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[audit]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[securityevent]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[protected_storage]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\44LONAD04[\\PIPE\\protected_storage]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[dsrole]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_ip_tcp:10.1.1.33[1025]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[NTDS_LPC]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_http:10.1.1.33[1027]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_np:\\\\44LONAD04[\\PIPE\\lsass]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[audit]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[securityevent]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[protected_storage]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_np:\\\\44LONAD04[\\PIPE\\protected_storage]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[dsrole]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_ip_tcp:10.1.1.33[1025]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[NTDS_LPC]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_http:10.1.1.33[1027]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[wzcsvc]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[OLE806B8DC68882415997C336A835CD]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncacn_np:\\\\44LONAD04[\\PIPE\\atsvc]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[wzcsvc]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[OLE806B8DC68882415997C336A835CD]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncacn_np:\\\\44LONAD04[\\PIPE\\atsvc]

UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[wzcsvc]

UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[OLE806B8DC68882415997C336A835CD]

UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncacn_np:\\\\44LONAD04[\\PIPE\\atsvc]

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[dhcpcsvc]

Total endpoints found: 99

==== End of RPC Endpoint Mapper query response ====

RPC ENdpoints 1097,1076,1058,1025,1027 show open:

C:\>portqry -n 44lonad04 -o 1097,1076,1058,1025,1027

Querying target system called:

44lonad04

Attempting to resolve name to IP address...

Name resolved to 10.1.1.33

TCP port 1097 (unknown service): LISTENING

TCP port 1076 (unknown service): LISTENING

TCP port 1058 (unknown service): LISTENING

TCP port 1025 (unknown service): LISTENING

TCP port 1027 (unknown service): LISTENING

I have removed out antivirus software and rebooted the server. There are no
firewalls.
Not sure what else to check?

.

Follow-Ups:
- Re: rendom /prepare failed to bind to server
  - From: Ace Fekay [Microsoft Certified Trainer]

Prev by Date: Re: Possible to have inter-forest trust between subdomains of two fore
Next by Date: Re: Possible to have inter-forest trust between subdomains of two fore
Previous by thread: Re: Workstation won't take the Domain Policy - help...
Next by thread: Re: rendom /prepare failed to bind to server
Index(es):
- Date
- Thread

Relevant Pages

Re: dcdiag - Starting test: KnowsOfRoleHolders - DsBindWithSpnEx() failed with error 1722
... I was able to resolve the remote DC's with the nslookup command. ... TCP port 1094 (unknown service): ... Are you able to use PORTQRY against the Schema master? ...
(microsoft.public.windows.server.active_directory)
Re: Cannot contact the DNS server, 2003 server
... The only thing I've installed on this is Exchange. ... TCP port 1094 (unknown service): NOT LISTENING ...
(microsoft.public.windows.server.dns)
Re: rendom /prepare failed to bind to server
... Attempting to resolve name to IP address... ... TCP port 1753 (unknown service): NOT LISTENING ...
(microsoft.public.windows.server.active_directory)
Re: NTP Problem
... Querying target system called: ... Attempting to resolve IP address to a name... ... TCP port 123 (unknown service): ...
(microsoft.public.win2000.general)
Re: rendom /prepare failed to bind to server
... Not Listening means it is connecting, but nothing is listening on the port, ... Attempting to resolve name to IP address... ... TCP port 1753 (unknown service): ...
(microsoft.public.windows.server.active_directory)