Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works

Lonely NT Server on 2003 Domain

  • Please log in to reply



    New Member

  • Member
  • Pip
  • 1 posts
I'm hoping someone has a thought on this. I've recently upgraded an NT domain to a 2003 domain. On the old domain there was an NT PDC, and a regular NT server that was not a controller. After the upgrade, the NT server that was not a DC will connect and disconnect from the network at random intervals. It will be working fine then suddenly start declaring "The RPC server is unavailable" and will stop talking to the network. It has a static IP, and is set on the DNS. Machines outside the server can see and ping the trouble child, and existing connnections will stay, but no new connections to the server through the network will be taken, until the server decides to rejoin the network again. Everything I read says that NT server will work fine with 2003 in interim mode, and the NT BDC that still exists will play all right, it's just this one machine.

Does anyone have any insight into this? It would be really appreciated. I've been beating my head against the wall with this for days now.
  • 0


Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP