Solved

Workstation joined to domain but not visible in Microsoft Network

Posted on 2008-06-11
8
933 Views
Last Modified: 2013-12-23
AD consists of a parent domain and 2 child domains (ADMIN & ACADM).
Win2003 server in ADMIN (not a DC) sees SOME workstations in sibling domain (ACADM)

Selecting "Search AD" from within my network places the WIn2003 server finds the target workstations.
When you attempt to manage the workstation from with AD search results you get "Network path not found". The Win2003 server can Remote Desktop to any of the misssing workstations without needing to use a FQDN. Problem exists on multiple hosts in the ADMIN domain, including the DC.

All workstations connect to INTERNET, AD and exchange w/o issues
0
Comment
Question by:WTimKirk
  • 5
  • 3
8 Comments
 
LVL 3

Accepted Solution

by:
tsorensen55 earned 500 total points
ID: 21761810
Do you have WINS installed and configured on both ADMIN and ACADM and replicating with each other?

We run a root domain with 10 child domains and the only way we were able to smooth out most Network Path Not Found issues was making sure we had at least one WINS server in each child domain and the parent domain, make sure they all replicated in some form or fashion to the WINS server in the parent domain.

It might be a long shot but something to try and see if it works.
0
 

Author Comment

by:WTimKirk
ID: 21762059
I had my Network Manager add a WINS to both child domains last night (did not resolve this issue); I shall verify their replication pattern as I think he has replication between each child domain and the parent, but not directly between the sibling domains.
0
 
LVL 3

Expert Comment

by:tsorensen55
ID: 21762174
Are there any patterns such as certain operating systems etc? I know the firewall in Vista can pose some problems if not disabled and not set with certain exceptions allowed.
0
 

Author Comment

by:WTimKirk
ID: 21762253
None of the workstations are running Vista and we have disbled the Windows firewall via group policy. The truely odd thing is how 4 or 5 workstations in a classroom will be visble but not the remaing 20 or 21 systems are. Almost all of the 500+ workstations in ACADM are visble from ADMIN, but about 10% are not... All are successfully joined to the domain (test cases have been removed, renamed and rejoined successfully)..
0
 
LVL 3

Expert Comment

by:tsorensen55
ID: 21762291
Network Location Awareness service enabled and running and the workstation service?
0
 

Author Comment

by:WTimKirk
ID: 21769840
OK - I've now got a WINS in both child domains and the parent (all replicating to all WINS partners).
I have confirmed that the PDC in the ACADM domian is the master browser in that broadcast domain and that it and the missing workstations are on the same IP LAN segment and in the same VLAN. The machines are visible in AC on the PDC but the PDC does not see the target workstations in MyNetwork (I did try manulally remining several from the domain, deleting the AD record and readding them)???

We did have a workstation that had won the election as master browser, but that is no longer the case.
0
 

Author Comment

by:WTimKirk
ID: 21778154
I have managed to narrow the issue:

Some workstations in ACADM are not browsable within that domain. The server service is started and UNC connections work as does remote desktop using just the netbios name (I can do this from bothe the ADMIN and ACDAM domians)

nbtstat -n yields the expected  <00> unique workstation & group records as well as a <1E> domain record, but not a <20> server record.
0
 

Author Comment

by:WTimKirk
ID: 21782965
DUH... the enable Printer & File Sharing check box in the active network connection was not checked.
0

Join & Write a Comment

The Need In an Active Directory enviroment, the PDC emulator provide time synchronization for the domain. This is important since Active Directory uses Kerberos for authentication.  By default, if the time difference between systems is off by more …
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now