Windows Server 2003 R2
(1)
Exchange Server
(1)
CheckSDRefDom
(1)
KnowsOfRoleHolders
(1)
DNSResolver
(1)
NCSecDesc
(1)
ForestDnsZones
(1)
DomainDnsZones
(1)
rendom /prepare failed to bind to server
Asked By Jame
23-Jan-09 05:49 AM
I am running windows 2003 ADC, with SP2. The forest and domain are windows
2003 native.
When running the domain rename tool I get to stage 5 and then fail:
C:\Program Files\Microsoft Domain Rename Tools>rendom /prepare
Failed to Bind to server 44LONAD03.internal.london.occstrategy.com : 1753.
Failed to Bind to server 44LONAD04.internal.london.occstrategy.com : 1753.
Failed to Bind to server 44LONAD05.internal.london.occstrategy.com : 1753.
Waiting for DCs to reply.
3 servers contacted, 3 servers returned Errors
The operation completed successfully.
I have looked at article KB839880 and followed the tests there and
everything seems fine. Not sure what to check for now.
Hello James,Check with "netdom query fsmo" that all FSMO roles are available,
Asked By Meinolf Weber [MVP-DS]
25-Jan-09 07:11 AM
Hello James,
Check with "netdom query fsmo" that all FSMO roles are available, especially
the "Domain naming master". Did you check that one with the article? http://support.microsoft.com/kb/839880/en-us
Any firewall running?
Also check with portqry the server ports:
http://www.microsoft.com/downloads/details.aspx?FamilyID=89811747-C74B-4638-A2D5-AC828BDC6983&displaylang=en
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
I followed all the article suggestions and everything seems fine, here are the
Asked By Jame
23-Jan-09 07:08 AM
I followed all the article suggestions and everything seems fine, here are
the results:
C:\Program Files\Microsoft Domain Rename Tools>dsquery server -hasfsmo name
on,DC=occstrategy,DC=com"
C:\Program Files\Microsoft Domain Rename Tools>netdom query fsmo
Schema owner 44LONAD04.internal.london.occstrategy.com
Domain role owner 44LONAD04.internal.london.occstrategy.com
PDC role 44LONAD05.internal.london.occstrategy.com
RID pool manager 44LONAD04.internal.london.occstrategy.com
Infrastructure owner 44LONAD03.internal.london.occstrategy.com
The command completed successfully.
C:\Program Files\Microsoft Domain Rename Tools>portqry -n 44lonad04 -o
1025,1027
,1074,1054,1102
Querying target system called:
44lonad04
Attempting to resolve name to IP address...
Name resolved to 10.1.1.33
TCP port 1025 (unknown service): LISTENING
TCP port 1027 (unknown service): LISTENING
TCP port 1074 (unknown service): LISTENING
TCP port 1054 (unknown service): LISTENING
TCP port 1102 (unknown service): LISTENING
C:\Documents and Settings\Administrator.OC&C>dcdiag
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: London\44LONAD04
Starting test: Connectivity
......................... 44LONAD04 passed test Connectivity
Doing primary tests
Testing server: London\44LONAD04
Starting test: Replications
......................... 44LONAD04 passed test Replications
Starting test: NCSecDesc
......................... 44LONAD04 passed test NCSecDesc
Starting test: NetLogons
......................... 44LONAD04 passed test NetLogons
Starting test: Advertising
......................... 44LONAD04 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... 44LONAD04 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... 44LONAD04 passed test RidManager
Starting test: MachineAccount
......................... 44LONAD04 passed test MachineAccount
Starting test: Services
......................... 44LONAD04 passed test Services
Starting test: ObjectsReplicated
......................... 44LONAD04 passed test ObjectsReplicated
Starting test: frssysvol
......................... 44LONAD04 passed test frssysvol
Starting test: frsevent
......................... 44LONAD04 passed test frsevent
Starting test: kccevent
......................... 44LONAD04 passed test kccevent
Starting test: systemlog
......................... 44LONAD04 passed test systemlog
Starting test: VerifyReferences
......................... 44LONAD04 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : internal
Starting test: CrossRefValidation
......................... internal passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... internal passed test CheckSDRefDom
Running enterprise tests on : internal.london.occstrategy.com
Starting test: Intersite
......................... internal.london.occstrategy.com passed
test I
ntersite
Starting test: FsmoCheck
......................... internal.london.occstrategy.com passed
test F
smoCheck
C:\Documents and Settings\Administrator.OC&C>netdiag
.....................................
Computer Name: 44LONAD04
DNS Host Name: 44LONAD04.internal.london.occstrategy.com
System info : Microsoft Windows Server 2003 R2 (Build 3790)
Processor : x86 Family 6 Model 23 Stepping 8, GenuineIntel
List of installed hotfixes :
KB924667-v2
KB925398_WMP64
KB925876
KB925902
KB926122
KB927891
KB929123
KB930178
KB931784
KB932168
KB933729
KB933854
KB935839
KB935840
KB936021
KB936357
KB936782
KB938127
KB938127-IE7
KB938464
KB941202
KB941569
KB941644
KB941693
KB942763
KB943055
KB943460
KB943485
KB943729
KB944338
KB944653
KB945553
KB946026
KB948496
KB948590
KB949014
KB950759
KB950759-IE7
KB950760
KB950762
KB950974
KB951066
KB951072-v2
KB951698
KB951746
KB951748
KB952954
KB953838-IE7
KB953839
KB954211
KB955069
KB956390-IE7
KB956391
KB956803
KB956841
KB957095
KB957097
KB958644
Q147222
Netcard queries test . . . . . . . : Passed
Per interface results:
Adapter : Local Area Connection
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : 44LONAD04
IP Address . . . . . . . . : 10.1.1.33
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 10.1.1.1
Dns Servers. . . . . . . . : 10.1.1.13
10.1.1.33
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenge
r Service', <20> 'WINS' names is missing.
WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{2CCC324E-8B9F-4C83-A991-23EFE711189B}
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation
Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server
'10.1.1.13' a
nd other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server
'10.1.1.33' a
nd other DCs also have some of the names registered.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{2CCC324E-8B9F-4C83-A991-23EFE711189B}
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{2CCC324E-8B9F-4C83-A991-23EFE711189B}
The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Passed
Secure channel for domain 'OC&C' is to
'\\44LONAD05.internal.london.occstrat
egy.com'.
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Skipped
Note: run "netsh ipsec dynamic show /?" for more detailed information
The command completed successfully
rendom /prepare failed to bind to server
Asked By Ace Fekay [Microsoft Certified Trainer]
23-Jan-09 12:45 PM
James <James@> requesting assistance, typed the
following:
Are you running this on the Schema Master?
--Â
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer
aceman@mvps.Remove This Part.org
For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.
The accounts are in the correct groups.
Asked By Jame
05-Feb-09 08:27 AM
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?
rendom /prepare failed to bind to server
Asked By Ace Fekay [Microsoft Certified Trainer]
07-Feb-09 12:48 AM
James <James@>, posted the following:
When running portqry, run it from your machine that you are trying the
schema update from, as well as run it from another DC to 44lonad04. This
will test its response across the network.
Not Listening means it is connecting, but nothing is listening on the port,
which is a good thing, unless something is supposed to be listening on it,
such as a service supposedly using that port.
Here is a guide for portqry to understand the results:
http://blogs.technet.com/askds/archive/2009/01/22/using-portqry-for-troubleshooting.aspx
Ace
44> When running portqry, run it from your machine that you are trying the I
Asked By Jame
09-Feb-09 07:16 AM
44> When running portqry, run it from your machine that you are trying the
I have 3 AD servers in total, from 44lonad05:
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
From 44lonad03:
C:\>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
44> When running portqry, run it from your machine that you are trying the I
Asked By Jame
09-Feb-09 07:17 AM
44> When running portqry, run it from your machine that you are trying the
I have 3 AD servers in total, from 44lonad05:
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
From 44lonad03:
C:\>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
rendom /prepare failed to bind to server
Asked By Jame
09-Feb-09 07:17 AM
I have 3 AD servers in total, from 44lonad05:
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
From 44lonad03:
C:\>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
rendom /prepare failed to bind to server
Asked By Jame
09-Feb-09 07:18 AM
I have 3 AD servers in total, from 44lonad05:
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
From 44lonad03:
C:\>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
rendom /prepare failed to bind to server
Asked By Ace Fekay [Microsoft Certified Trainer]
12-Feb-09 01:36 AM
James <James@>, posted the following:
Hmm, all results indicate nothing is listening on that port. Curious why
rendom would fail on that port. I couldn't find any info on the port other
than it is an emphemeral response port used by Windows machines.
However, one thing I can point out, when running a rendom, it is targeting
the Domain Name Master. On that guy, can you run the following and post any
errors in the results?
netdiag /v /fix > c:\netdiag.txt
dcdiab /v /fix > c:\dcdiag.txt
Ace
I have run the above on the domain name master (44lonad04) and checked through
Asked By Jame
16-Feb-09 10:31 AM
I have run the above on the domain name master (44lonad04) and checked
through the txt files and no errors are reported.
rendom /prepare failed to bind to server
Asked By Ace Fekay [Microsoft Certified Trainer]
16-Feb-09 07:39 PM
Good. One more question, is the Schema set to allow to be updated?
Ace
rendom /prepare failed to bind to server
Asked By Ace Fekay [Microsoft Certified Trainer]
16-Feb-09 11:17 PM
Also, is the Domain Name Master a GC? Possibly move the DNM role to another
server? Keep in mind the DNM has to be a GC.
Ace
Yes it is.
Asked By Jame
19-Feb-09 09:51 AM
Yes it is. Moved to the other GC, waited 24 hours for direct sync and got
the same error when tried again.
I have looked at the schela update flag, is that just for windows 2000 only?
My DC's are windows 2003 and I could update the schema when doing a test
exchange 2007 migration.
rendom /prepare failed to bind to server
Asked By Ace Fekay [Microsoft Certified Trainer]
19-Feb-09 07:39 PM
James <James@>, posted the following:
Something else must be blocking the traffic. If everything else works, it is
becoming difficult to figure out. Possibly antivirus that also has a
component to restrict certain functions? I know McAfee restricts SMTP telnet
tests that I have to disable the On Access scanner to get it to work. That
is one possibility.
Also, I know you said you used a workstation. What operating system is the
workstation? I believe you need to use a Windows 2003 server (member server)
to use as the 'control center' and not a desktop operating system.
Domain Rename Part 1 - Setup
http://thelazyadmin.com/blogs/thelazyadmin/archive/2006/06/07/Domain-Rename-Part-1-_2D00_-Setup.aspx
Domain Rename Part 2 - Renaming
http://thelazyadmin.com/blogs/thelazyadmin/archive/2006/06/08/Domain-Rename-Part-2-_2D00_-Renaming.aspx
Domain Rename Part 3 - Exchange 2003
http://thelazyadmin.com/blogs/thelazyadmin/archive/2006/06/09/Domain-Rename-Part-3-_2D00_-Exchange-2003.aspx
Domain Rename – Rename a Windows 2003 Forest with Exchange 2003 installed
(ifyou don't have Exchange, you can ignore the Exchange part for now, unless
it applies to you)
http://www.msexchange.org/tutorials/Domain-Rename.html
Now if you have Exchange 2003, here is what you need as well:
Supplemental steps for using the Exchange Server Domain Rename Fixup tool
together with the Windows Server 2003 domain rename tools:
http://support.microsoft.com/kb/842116/
Ace