Specified Domain Does Not Exist or Could Not Be Contacted

I'm having an issue logging a server at a remote location onto our internal
domain. Every time I try to log on the domain, I get the message that's in
my Subject title.

Not sure what could be the case. When the machine was setup locally, it was
added to the domain and able to log in. However, after moving it to a remove
location, and on a different IP subnet, it can not contact our domain.

I have LDAP open both here and at the remote location. I also have added
routes in the LMHOSTS file that point to our DC, and other computers, here in
the office. Anyone have any possible ideas as to what would prevent the
remote server from finding the domain and being able to log in?

-Brian Allen

You have 2 issues:

1. Ports - probably need to open Kerberos (88 UDP) and DNS (53 TCP/UDP).

2. Routing - you can put names and IP addresses in LMHOSTS, but not
routing. Can you ping the IP of the DC from the remote server?

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Brian Allen" <(E-Mail Removed)> wrote in message
news:60BD63B0-6431-4D67-9FCC-(E-Mail Removed)...
> I'm having an issue logging a server at a remote location onto our
internal
> domain. Every time I try to log on the domain, I get the message that's
in
> my Subject title.
>
> Not sure what could be the case. When the machine was setup locally, it
was
> added to the domain and able to log in. However, after moving it to a
remove
> location, and on a different IP subnet, it can not contact our domain.
>
> I have LDAP open both here and at the remote location. I also have added
> routes in the LMHOSTS file that point to our DC, and other computers, here
in
> the office. Anyone have any possible ideas as to what would prevent the
> remote server from finding the domain and being able to log in?
>
> -Brian Allen