Notorious
asked on
RPC Call Raised Exception 0x6ba. The Server is unavailable (Ms Exchange 5.5)
Hi Guys,
As of a week ago i have been getting the above error message when attempting to perform an RPC PING from any client PC to the Exchange box. This error message i think is causing the problem where by if any new mailbox is created within Ms Exchange Administrator, and Outlook is then configured to access this mailbox, the user is presented with a box asking for Username, Domain & Password. Eventhough they have logged on to the network. When however these details are keyed in, a message is returned stating that the logon details are incorrect when they are not.
The TCPIP Binding order is correct. As only one protocol is in use.
The PCs and servers are virus free.
The Exchange server can be Pinged by Name & IP Address.
The Check Name within Outlook however does fail to resolve.
Please help as this problem is becoming critical.
Regards
Notorious.............
P.S. This problem is only affecting newly created mailboxes and not ones created a while ago.
As of a week ago i have been getting the above error message when attempting to perform an RPC PING from any client PC to the Exchange box. This error message i think is causing the problem where by if any new mailbox is created within Ms Exchange Administrator, and Outlook is then configured to access this mailbox, the user is presented with a box asking for Username, Domain & Password. Eventhough they have logged on to the network. When however these details are keyed in, a message is returned stating that the logon details are incorrect when they are not.
The TCPIP Binding order is correct. As only one protocol is in use.
The PCs and servers are virus free.
The Exchange server can be Pinged by Name & IP Address.
The Check Name within Outlook however does fail to resolve.
Please help as this problem is becoming critical.
Regards
Notorious.............
P.S. This problem is only affecting newly created mailboxes and not ones created a while ago.
Are you running the RPCserver component for RPCping? this must be running for a successfull test.
Did you apply the MS hotfixes of this month? might be the causing factor. LSASS has been updated.
Check you DSaccess as well. (Only if u use Outlook 98)
Did you apply the MS hotfixes of this month? might be the causing factor. LSASS has been updated.
Check you DSaccess as well. (Only if u use Outlook 98)
ASKER
Hi,
The server is running Ms Exchange 5.5. Enterprise.
Internal DNS's are being used for the clients and the servers. DNS servers appear to be resolving addresses normally.
RPC PING is only being used for the client end
Outlook 98 being using.
What is RUS? As i have not heard of it before.
No hotfixes have been applied as of yet.
Regards
Notorious....
P.S. All servers running WinNT4.0 sp6
The server is running Ms Exchange 5.5. Enterprise.
Internal DNS's are being used for the clients and the servers. DNS servers appear to be resolving addresses normally.
RPC PING is only being used for the client end
Outlook 98 being using.
What is RUS? As i have not heard of it before.
No hotfixes have been applied as of yet.
Regards
Notorious....
P.S. All servers running WinNT4.0 sp6
RUS is part of Exchange 2000/2003; not used with Exchange 5.5. Have you verified that WINS is working?
ASKER
Yes. WINS appears to be working fine. Nothing is standing out as a potential cause to this problem.
Regards
Notorious..........
Regards
Notorious..........
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks. Turned out that the WINS database was indeed corrupted. Had to restore from backup
D