Admin can't see the computers in the Active Directory!??

My dept. have Server running Windows 2003 Standard Edt. as DNS Server and DHCP Server. Workstations have Windows XP Professional with Norton Internet Security. I had already configured the firewall on each workstation to allow communcation between workstations and the server. Unfortuately, I can't see the workstations in MY Network Place, only the server. WTF!!

No trouble assigning the workstations to the domain.

DOMAIN: JWC.COM
DNS DOMAIN: PROBATION.JWC.COM
DNS IP ADDRESS: 192.168.12.198
SUBNET: 255.255.255.0

Can you tell me what I did wrong?!?

 

Im no pro at A.D. on 2003 but have a look at your DNS portion. Make sure you are pointing to yourself!!! And make sure you have a *pointer* in reverse lookup zone to your IP(server). Im assuming that users are able to log onto the domain? If so then drop the firewall on one terminal and try that. Also, make sure that the DHCP portion is issuing your server DNS IP to the clients.

Good luck

 

Perhaps, that's the problem why I can't see the WinXP Pro workstations. My VPN Router is acting as DCHP Server, not my win2003k server. Here's the catch.....Windows NT and Windows 2000 Workstations can be seen on the domain whileas Windows XP cannot be seen. Could it bee the security feature in Windows XP that prevent users, even the admin, from searching the workstation in the domain??

hmmmm.....I don't understand what the reverse lookup zone is. I just simply following steps the "Setup the Server" Wizard gave me.

 

It sounds like your problem could be boiled down to two things then.
1. Make sure all XP clients Machines have *Disabled simple file sharing*!!!!!!!! I dont know why but that alone will make Admin's pull their hair out when it comes to network Neighborhood.
2. Your DNS solution.......hhmmmmmmm I would need more details on your topology but what I do know is unless you are running a wins server to resolve hostname to IP you will not be able to see computers through a VPN. The only solution to that is using the LMHost file (LanManager).
As far as the pointer file on reverse look up zone, well, you need it. On your server, go to Admins tools and open up DNS. There you will see your servers name. Double click that and you will see foward lookup zone and reverse lookup zones. The wizard probably took care of the needed entries for the forward but not the reverse. I dont have 2003 in front of me now and Im trying to remember from memory. In a nutshell, you need a pointer (PTR) file to point to your subnet to resolve DNS. Without it I do not believe DNS will work locally. Your forward lookup is used to resolve DNS issues outside of your subnet. And as I mentioned before, on your DNS server machine, make sure you have the adapters DNS properties pointing toward itself. I hope this helps you, and to caviat everything I have said. IM NO PRO AT 2003 A.D.