J
John Foutch
Windows 2000 AD all DCs running SP3
This AM started to get the following message when attempting to connect to a
different Domain Controller in AD Users & Computers or AD Sites & Services:
"The list of domain controllers for domain is unavailable because: Not
enough storage is available to complete this operation."
To the best of my knowledge, the only thing that changed this AM was that I
manually added 2 Replication Connections to a DC in a remote site in AD
Sites and Services. I don't think that would cause this but at this point I
would believe anything.
I have looked at Event Logs to no avail. It does not seem to impacting our
users but all Admins are getting that same message when they attempt to
connect to a DC other than their LOGONSERVER. It will let you manually type
a new server in but it will not list them out (like it did before this AM).
I ran a sniffer and captured a few relevant frames while attempting the
above. I saw an RPC bind request from my client and an RPC ACK from that
client's LOGONSERVER. Then I saw an Endpoint Mapper Call to Get Service
Location that contained uninterpreted arguments and an Endpoint Mapper Resp
that contained uninterpreted arguments.
That's all folks.
This AM started to get the following message when attempting to connect to a
different Domain Controller in AD Users & Computers or AD Sites & Services:
"The list of domain controllers for domain is unavailable because: Not
enough storage is available to complete this operation."
To the best of my knowledge, the only thing that changed this AM was that I
manually added 2 Replication Connections to a DC in a remote site in AD
Sites and Services. I don't think that would cause this but at this point I
would believe anything.
I have looked at Event Logs to no avail. It does not seem to impacting our
users but all Admins are getting that same message when they attempt to
connect to a DC other than their LOGONSERVER. It will let you manually type
a new server in but it will not list them out (like it did before this AM).
I ran a sniffer and captured a few relevant frames while attempting the
above. I saw an RPC bind request from my client and an RPC ACK from that
client's LOGONSERVER. Then I saw an Endpoint Mapper Call to Get Service
Location that contained uninterpreted arguments and an Endpoint Mapper Resp
that contained uninterpreted arguments.
That's all folks.