Networking Forums

Networking Forums > Computer Networking > Windows Networking > Domain Controller can not see client work stations

Reply
Thread Tools Display Modes

Domain Controller can not see client work stations

 
 
Mark
Guest
Posts: n/a

 
      08-23-2005, 06:34 AM
Hello

I was testing VPN connections to our domain controller which is a windows
2003 server.

Once we had finished I disabled the remote access service.

The domain controller can now ping the workstations and if you search for a
workstation you can access the shared folders but you can not see any
computer in network places.

From the work station you can ping the server and can remote desktop to the
server and you can map the shred drives but you can not access the server
through network places or windows explorer.

Can any one suggest how I can fix this issue.

Thanks in advance

Mark
 
Reply With Quote
 
 
 
 
Todd J Heron
Guest
Posts: n/a

 
      08-23-2005, 01:23 PM
>The domain controller can now ping the workstations and if you search for a
>workstation you can access the shared folders >but you can not see any
>computer in network places.


Are these remote computers registering with the same WINS server your domain
controller is registering with? Are these computers members of the same
domain your domain controller is in?

>From the work station you can ping the server and can remote desktop to the
>server and you can map the shared drives but >you can not access the server
>through network places or windows explorer.


Sounds like a NetBIOS name resolution issue. Network Places uses WINS for
it's name services, in a subnetted environment (you have one simply by
virtue of having a VPN), if you want to see a list of all computers in your
infrastructure, all computers must be pointed to the same WINS server, be
members of the same domain, and run the Client for MS Networks and File and
Print Sharing for MS Networks (and no firewall blocking these). The
Computer Browser service must be running on the DC and on at least one
computer in every subnet.

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights


"Mark" <(E-Mail Removed)> wrote in message
news:11353688-B432-44E6-8A43-(E-Mail Removed)...
Hello

I was testing VPN connections to our domain controller which is a windows
2003 server.

Once we had finished I disabled the remote access service.

The domain controller can now ping the workstations and if you search for a
workstation you can access the shared folders but you can not see any
computer in network places.

From the work station you can ping the server and can remote desktop to the
server and you can map the shred drives but you can not access the server
through network places or windows explorer.

Can any one suggest how I can fix this issue.

Thanks in advance

Mark

 
Reply With Quote
 
Mark
Guest
Posts: n/a

 
      08-24-2005, 01:06 AM
The computers are all on the same domain.
They are on the internal network.
We decided not to go ahead with the VPN so we do not have any external
computers connecting to the network.

The thing I did was to configure routing and remote access to test the VPN
and then uninstall the routing and remote access once we were finished

I believe the DC stopped seeing the internal network once I had configured
the routing and remote access. because I lost all connections to the mapped
network drives on the DC.

Once I removed the routing and remote access we reconnected the network
drives but have the issue of not seeing the DC from the workstations.

Thanks

Mark

You can see the Domain group but not the individual workstations.


"Todd J Heron" wrote:

> >The domain controller can now ping the workstations and if you search for a
> >workstation you can access the shared folders >but you can not see any
> >computer in network places.

>
> Are these remote computers registering with the same WINS server your domain
> controller is registering with? Are these computers members of the same
> domain your domain controller is in?
>
> >From the work station you can ping the server and can remote desktop to the
> >server and you can map the shared drives but >you can not access the server
> >through network places or windows explorer.

>
> Sounds like a NetBIOS name resolution issue. Network Places uses WINS for
> it's name services, in a subnetted environment (you have one simply by
> virtue of having a VPN), if you want to see a list of all computers in your
> infrastructure, all computers must be pointed to the same WINS server, be
> members of the same domain, and run the Client for MS Networks and File and
> Print Sharing for MS Networks (and no firewall blocking these). The
> Computer Browser service must be running on the DC and on at least one
> computer in every subnet.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
>
> "Mark" <(E-Mail Removed)> wrote in message
> news:11353688-B432-44E6-8A43-(E-Mail Removed)...
> Hello
>
> I was testing VPN connections to our domain controller which is a windows
> 2003 server.
>
> Once we had finished I disabled the remote access service.
>
> The domain controller can now ping the workstations and if you search for a
> workstation you can access the shared folders but you can not see any
> computer in network places.
>
> From the work station you can ping the server and can remote desktop to the
> server and you can map the shred drives but you can not access the server
> through network places or windows explorer.
>
> Can any one suggest how I can fix this issue.
>
> Thanks in advance
>
> Mark
>
>

 
Reply With Quote
 
Mark
Guest
Posts: n/a

 
      08-24-2005, 01:28 AM
Hello Todd

You were right I checked the network setting s and enabled netbios over TCP
and it all started to work again.

Thanks

Mark

"Todd J Heron" wrote:

> >The domain controller can now ping the workstations and if you search for a
> >workstation you can access the shared folders >but you can not see any
> >computer in network places.

>
> Are these remote computers registering with the same WINS server your domain
> controller is registering with? Are these computers members of the same
> domain your domain controller is in?
>
> >From the work station you can ping the server and can remote desktop to the
> >server and you can map the shared drives but >you can not access the server
> >through network places or windows explorer.

>
> Sounds like a NetBIOS name resolution issue. Network Places uses WINS for
> it's name services, in a subnetted environment (you have one simply by
> virtue of having a VPN), if you want to see a list of all computers in your
> infrastructure, all computers must be pointed to the same WINS server, be
> members of the same domain, and run the Client for MS Networks and File and
> Print Sharing for MS Networks (and no firewall blocking these). The
> Computer Browser service must be running on the DC and on at least one
> computer in every subnet.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
>
> "Mark" <(E-Mail Removed)> wrote in message
> news:11353688-B432-44E6-8A43-(E-Mail Removed)...
> Hello
>
> I was testing VPN connections to our domain controller which is a windows
> 2003 server.
>
> Once we had finished I disabled the remote access service.
>
> The domain controller can now ping the workstations and if you search for a
> workstation you can access the shared folders but you can not see any
> computer in network places.
>
> From the work station you can ping the server and can remote desktop to the
> server and you can map the shred drives but you can not access the server
> through network places or windows explorer.
>
> Can any one suggest how I can fix this issue.
>
> Thanks in advance
>
> Mark
>
>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. Ace Fekay [MVP-DS, MCT] Windows Networking 1 01-10-2010 11:08 PM
Clients can't join domain-new Primary Domain Controller installed blinton25 Windows Networking 7 06-23-2008 09:58 PM
Server 2003 Standard - Cannot browse domain with domain controller! davidw@dwynn.demon.co.uk Windows Networking 2 04-12-2006 04:28 PM
VPNs will not work with MS Wireless Routers (Base Stations) Dilbug Broadband Hardware 0 11-04-2004 02:18 AM
Moving a domain 2003 domain controller to a different subnet John zhang Windows Networking 1 07-27-2004 01:41 PM



1 2 3 4 5 6 7 8 9 10 11