Cannot connect to the Domain

[Guest]

The situation is we have 2 buildings each on a different subnet (we'll call
them building A and building B). I've come across a PC that I can not log
into the domain in building B. I've tried different cube locations but still
recieve a msg the domain could not be found. I am able to connect different
computers in those same locations successfully (all built with same process).
I bring the affected PC back to building A and it connects fine. We've tried
release/renew, remove/readd to domain, ran gpupdate, etc. (non work from
building B). I am however able to get to the internet from both buildings. We
then took a new PC and built it and transfered all user data/profiles etc. to
the new buid, worked fine in building A, brought it to building B and again
cannot connect to the network.
Any suggestions?

 

[Kerry Brown]

Carefully look at the results of ipconfig /all from a pc that works and one
that doesn't. You are looking for any differences at all. Post the results
here if you like. The only differences should be the IP address and the MAC
address.

 

[Guest]

Well after another 90 minutes at looking into this issue, we started sniffing
down the Windows Firewall path. Nothing came up until we noticed the the
Symantec Personal Firewall sw was installed. This is a client that we run on
our Laptops. 2 things here, First - we don't ever install this on PC's hence
why we never went looking for it on this machine so it must have been
installed by mistake via SMS (someone fat fingered the WSID). Second -
building B is a new building in which we have not set the exceptions for that
subnet in our Symantec Admin Console yet. Removed the Client and all is now
working!

A lovely waste of a morning!

 

[Kerry Brown]

Yes, I have learned to hate Symantec consumer products. They have many
"hidden" features.