rpc server is unavailable - trust

i get this error when trying to remote to a member server "rpc server is unavailable", after entering my credentials.  i found a couple questions on here that say it might be related to a trust with the DC's.  apparently it is because when i run a netdiag, i cant get a list of DC's.

DC list test . . . . . . . . . . . : Failed
    'MyDomain': No DCs are up.

Trust relationship test. . . . . . : Failed
    'MyDomain': No DCs are up (Cannot run test).
    Secure channel for domain 'MyDomain' is to '\\DC2.MyDomain.com'.

ive tried using the netdiag /fix switch, but that doesnt change anything.  no other servers are having this problem and the DNS appears to be in perfect shape.  i thought it would work to unjoin and rejoin the server from the domain, but my boss doesnt want to do that unless it is our only option.  what else can we try?
LVL 22
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Are you remoting through ISA server?
WMIFAuthor Commented:
nope, this is straight from my workstation pc using microsofts remote desktop client.  the member server is in admin mode.  
RPC issues are tough to troubleshoot.  

I would start with DNS.  Make sure all the SRV records are registered and you have no resolution issues.  
No ISP DNS addresses anywhere inside the LAN except on the Forwarder tab of the DNS server.

I had the same issues when attempting to connect to my server from one workstation here.  I played with numerous things - then one day it decided to work.

I did make an adjustment to my ISA server and even though the client and server were inside the ISA it seemed to make a difference.

If you use a Firewall you may want to look at the RPC filter and disable strict compliance.  

Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

WMIFAuthor Commented:
ive gone through the dns and it appears to be in good shape.  i ran netdiag and dcdiag on both DCs just to be sure and they came back clean.  
There is a utility (I think in the Resource Kit - could be wrong) called RPCPING.  You could see if that helps point to something of value.

Is the RPC service running?
If the server has 2 NICs is the LAN side interface at the top of the binding order?

I'm still thinking.

In the meantime, here are some articles:


WMIFAuthor Commented:
RPC service is running and i thought about restarting it, but its greyed out and wont let me (on any of the other servers as well).  server has only one nic.  earlier today i installed new drivers, management configuration utility, and firmware from hp with a reboot after.

ive been to the first article and nothing came of it.  the second one is for the DC not functioning properly, but ive got 15 other servers that work properly as well as 300 workstations.  since dcdiag came clean as well, im leading away from the DCs.

im heading home for the night though, so dont think too hard. :)
WMIFAuthor Commented:
btw, i couldnt find rpcping in the support tools group, and a quick google only turned up articles on how to use it.  ill give it a shot to help troubleshoot this, but do you know where to pull it from?
You'll find it in the NT Res Kit (believe it or not!)

Here: http://support.microsoft.com/kb/206848/en-us

Here is (sort of) how to use this:  http://support.microsoft.com/kb/167260/en-us

It's kind of dated, but can yield some useful results.

WMIFAuthor Commented:
i will check it out tomorrow morning when i get into the office.  if you think of anything else in the meantime, be sure to post. :)
WMIFAuthor Commented:
the rpingdos utility couldnt bind, which is pretty much what i was expecting.  i think i need to attack this problem with the netdiag not being able to list the DCs.  any ideas on that?
Is there something in the middle that is blocking some ports?  or is everything on the same wire inside the firewall?

You could reset the Secure Channel:


This should work the same for 2003.

Let me know.
WMIFAuthor Commented:
no hardware or software firewall between the 2.

am i reseting the machine account on the DC or the member server?
WMIFAuthor Commented:
well, i tried to reset the password from the dc pointing to the member server and from the member server pointing to the dc.  all times i have tried it cannot communicate with the domain.  says it does not exist.
Is the Computer account in the Domain Controllers OU?  Can you recheck the NIC setting to make sure there are no ISP entries on it and that it points to a DNS server internally that is up and running?

If you need some eyes on this let me know.  My alias here at gmail.

WMIFAuthor Commented:
digging deeper, i found that the netbios helper service is not started.  from what i can search, its very much required in order for file sharing, web, network browsing, etc.  the problems i have found with having the service disabled, pretty much line up with what im facing.  problem is, the service is set to start automatically, but it wont start on bootup.  it wont startup when i manually try to start it either.  i cant find anything on problems of why it wouldnt start, just problems that happen when its not started.
Mine is started, so I assume it should be on yours.

Is NetBIOS enabled on the NIC?  It's on the WINS tab.

There should be Event Logs for this not starting.  Can you find any?

WMIFAuthor Commented:
yup, it just says that the netbios service didnt respond in a timely fashion.  my boss got a call into microsoft a bit ago, and the tech had him remove a couple files and registry entries.  now the server is inaccessable completely.  

I suggest you find the case # and reopen it.  Tell them it's worse than when you started.

The $250 is per incident, so make sure you tell them it's the same incident.

WMIFAuthor Commented:
sorry, i should have mentioned that he was still on the phone with them.  it is finally resolved and back to normal.  he had him delete a winsock and winsock32 file then reboot.  that rebuilt those files and allowed the netbios helper service to start again.  netdiag shows everything passed now and we can remote desktop in again.

do you have any objections to a PAQ/refund?
Closed, 500 points refunded.

Community Support Moderator

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.