ThunderChyld
IS-IT--Management
We have two offices, connected by a VPN.
I am currently in the middle of transfering everyone to our new server & domain (Win2k Advanced Server).
The local office is working perfectly on the new domain. However the remote office has the problems.....
They can ping the new server, they can map shared drives and even use it's printer. However when they try and join the domain they get an error - The RPC Server is Unavailable -
I've already checked/tried LOTS of things.....
The RPC service is started and I've stopped and restarted it too.
The firewall between offices isn't blocking/encrypting anything.
The user has full rights to do anything on the server.
I've rebooted everything.
All machines are fully updated/service packed.
The odd part is that when trying to connect with a new machine, the computer gets registered in AD as an account but is disabled.
If I reenable the account and then try to connect again I get same error on the client and AD disables the account again.
All my clients are Win XP
the only difference I can see between the two offices is the IP range....local are 192. and remote are 10.2
Could this be part of it and maybe I somewhere have to tell the server that, 'yes, this range are allowed onto the network?'
But if that is the case why does the server let them use shared resources or map it's drives?
Thanks for any ideas anyone has.
TC
I am currently in the middle of transfering everyone to our new server & domain (Win2k Advanced Server).
The local office is working perfectly on the new domain. However the remote office has the problems.....
They can ping the new server, they can map shared drives and even use it's printer. However when they try and join the domain they get an error - The RPC Server is Unavailable -
I've already checked/tried LOTS of things.....
The RPC service is started and I've stopped and restarted it too.
The firewall between offices isn't blocking/encrypting anything.
The user has full rights to do anything on the server.
I've rebooted everything.
All machines are fully updated/service packed.
The odd part is that when trying to connect with a new machine, the computer gets registered in AD as an account but is disabled.
If I reenable the account and then try to connect again I get same error on the client and AD disables the account again.
All my clients are Win XP
the only difference I can see between the two offices is the IP range....local are 192. and remote are 10.2
Could this be part of it and maybe I somewhere have to tell the server that, 'yes, this range are allowed onto the network?'
But if that is the case why does the server let them use shared resources or map it's drives?
Thanks for any ideas anyone has.
TC