We are experiencing some remote access problems with 2 of our servers. On each one we are not able to log on through remote desktop using the domain admin account. We are able to log on using the local admin account though. Each time we use domain credentials we receive the infamous "RPC server unavailable error."
The RPC server service is started and set to automatic. The RPC locater service is stopped and set to manual. And I'm guessing since these are system services, the properties can't be modified. Windows' firewall is diasabled since this is a closed network.
We are recieiving the follwing event IDs on a regular basis:
7003 - TCP/IP BetBIOS helper service needs NetBT.
1030 - Can't query for list of GPOs.
1058 - Can't access file gpt.ini
1219 - Logon rejected for domain admin, RPC server unavailable.
We also had some other strange occurences like not being able to connect to the problem sever through MMC. It's like all terminal services are blocked....but not really?
Now the only changes to the network was the upgrading of our domain controllers. We upgraded from 2000 to 2003 a few weeks ago. We're not sure if the problem was occurring before the upgrade, but it definately seems more prominent now.
Solutions tried:
All items under terminal services in the problem server's GPO were set to not configured.
No domain account can log in, only local accounts.
There are no open sessions for domain admin in terminal services manager.
I've done almost every DNS test can I think of and everything resolves fine.
To add to the confusion, this happened today:
We rebuilt 2 of our print servers today, NOT including the one mentioned above, and we were not able to rejoin them to the domain. I checked all the normal Microsoft fixes such as records, etc. and everything seems to be in line. I get the error:
"Unable to contact domain controller."
"DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain X: The query was for the SRV record _ldap._tcp.dc.msdcs.X
The follwing domain controllers were identified by the query:
bsc-dc1.X
bsc-dc2.X
All of the above is correct and I hope it helps determine my original problem. We have had tons of problems since upgrading and promoting our DCs from 2000. Is this a situation where some name records need to be updated in DNS? I checked all the records I knew of and they all seemed to be in line. I did a /registerdns on dc1 and the new server, etc.
I have worn out eventid.com, Microsoft, and Google. Nothing seems to fix it. I've found a few cases with exactly similar circumstances, but none of the fixes work. I'm hoping my combination of event IDs and circumstances will shed some more light. All suggestions appreciated.
The RPC server service is started and set to automatic. The RPC locater service is stopped and set to manual. And I'm guessing since these are system services, the properties can't be modified. Windows' firewall is diasabled since this is a closed network.
We are recieiving the follwing event IDs on a regular basis:
7003 - TCP/IP BetBIOS helper service needs NetBT.
1030 - Can't query for list of GPOs.
1058 - Can't access file gpt.ini
1219 - Logon rejected for domain admin, RPC server unavailable.
We also had some other strange occurences like not being able to connect to the problem sever through MMC. It's like all terminal services are blocked....but not really?
Now the only changes to the network was the upgrading of our domain controllers. We upgraded from 2000 to 2003 a few weeks ago. We're not sure if the problem was occurring before the upgrade, but it definately seems more prominent now.
Solutions tried:
All items under terminal services in the problem server's GPO were set to not configured.
No domain account can log in, only local accounts.
There are no open sessions for domain admin in terminal services manager.
I've done almost every DNS test can I think of and everything resolves fine.
To add to the confusion, this happened today:
We rebuilt 2 of our print servers today, NOT including the one mentioned above, and we were not able to rejoin them to the domain. I checked all the normal Microsoft fixes such as records, etc. and everything seems to be in line. I get the error:
"Unable to contact domain controller."
"DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain X: The query was for the SRV record _ldap._tcp.dc.msdcs.X
The follwing domain controllers were identified by the query:
bsc-dc1.X
bsc-dc2.X
All of the above is correct and I hope it helps determine my original problem. We have had tons of problems since upgrading and promoting our DCs from 2000. Is this a situation where some name records need to be updated in DNS? I checked all the records I knew of and they all seemed to be in line. I did a /registerdns on dc1 and the new server, etc.
I have worn out eventid.com, Microsoft, and Google. Nothing seems to fix it. I've found a few cases with exactly similar circumstances, but none of the fixes work. I'm hoping my combination of event IDs and circumstances will shed some more light. All suggestions appreciated.
