Problem with new Subnet

Hello all,
We've recently added a new subnet in one of our offices. This subnet
does not have a DC but there is one in the same office on a different
office. It appears that workstations in this new subnet are authentication
to a domain controller in a different office over a WAN link.

Another odd thing is that I can't ping the DC that is in the same office
from a workstation on the new subnet nor can I ping that workstation from
the DC. I can however ping every computer and server from one subnet to the
other without a problem. It just appears to be a problem with that DC.

I'm hoping someone can shed some light on the situation. Thanks for the
help.
-LIT

Hi,

Do you have sites created in your AD? Did you add new subnet and link it to
a site that you want your PCs to connect to?

About ping problem... Can you connect to the server using start -> run
\\server\ (where \\server\ is name of your server you can't ping) or you
can't do that either?

Can you do the following...

tracert -d 10.10.10.10

where 10.10.10.10 is IP address of your server. What do you get?

What to check:
- routes on the PCs, DC and routers
- subnet masks assigned to PCs, DC to see if they don't overlap...

--
Mike
Microsoft MVP - Windows Security


"Bob" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello all,
> We've recently added a new subnet in one of our offices. This subnet
> does not have a DC but there is one in the same office on a different
> office. It appears that workstations in this new subnet are
> authentication to a domain controller in a different office over a WAN
> link.
>
> Another odd thing is that I can't ping the DC that is in the same office
> from a workstation on the new subnet nor can I ping that workstation from
> the DC. I can however ping every computer and server from one subnet to
> the other without a problem. It just appears to be a problem with that
> DC.
>
> I'm hoping someone can shed some light on the situation. Thanks for the
> help.
> -LIT
>