Re: Cannot expand domain node in "my network places"

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Windows IP Configuration
Host Name . . . . . . . . . . . . : NMHISC-XPPC1
Primary Dns Suffix . . . . . . . : nmhisc.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : nmhisc.local

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : NMHISC
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
Physical Address. . . . . . . . . : 00-07-E9-63-25-3E
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.10.1.28
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.1.1
DHCP Server . . . . . . . . . . . : 10.10.1.2
DNS Servers . . . . . . . . . . . : 10.10.1.2
Lease Obtained. . . . . . . . . . : Sunday, February 11, 2007
3:29:45 PM
Lease Expires . . . . . . . . . . : Monday, February 19, 2007
3:29:45 PM

If I issue the net view command I get "system error 6118 has occurred. The
list of servers for this workgroup is not currently available." However if I
issue "net view \\nmhisc-fs I see the shares on the file server?
--
Mike Bannister


"Herb Martin" wrote:


"Mike Bannister" <mbannist@xxxxxxxxx (donotspam)> wrote in message
news:1EF41CEC-278D-4DF4-9871-034778689B24@xxxxxxxxxxxxxxxx

If it's not a DFS problem as has been suggested here's some more things
to
check.
What steps should I take to troubleshoot DFS problem?

First, did you or someone else setup a DFS root? If not, then this cannot
be a DFS root masquerading as a NeBIOS domain name in the browser.


Has the workstation been joined to the domain? Is it showing up in the
correct OU?
Yes it has been joined to domain and is in the correct OU.

The problem with such issues is that there is NO SECURITY on the ordinary
(NON-DFS) Browser list.

It shows up because the Master Browser has the list -- this list is not
dependent on domain membership or any permissions on the actual
servers or shares.

This is done because someone might have a SECOND User account in
the security context of the Server, which will not be provided until after
the
server is contacted.

The domain itself is NOT secured for browsing. This was the reason that
I GUESSED this might be a DFS issue since DFS nodes are "objects" that
can have security.

I actually considered this unlikely but it was the only thing that was
likely to
fit the symptoms reported. It is unlikely for several reasons: You showed
a
single tag domain name (and I HOPE that you domain has at least two tags),
you would have needed to create the DFS share (it wouldn't just happen),
and by default DFS shares have permissions that would allow them to be
used by everyone, at least everyone in the domain.

Do you have WINS running?
No WINS running.

WINS is only critically relevant IF you have more than one Subnet -- you
do need WINS (and every COMPUTER a WINS client) in that case if you
wish browsing to work.

However, even then, the name would just not be present, since WINS is
needed by the (Domain &) Master Browsers to "find each other" and thus
to replicate the browse lists across subnets. It might also make name
resolution
impossible but missing WINS would not mess up any permissions.

Where is the DHCP server? Is it a router or is one of the servers doing
it?
DHCP is running on the DC for the Domain. (Win2k03 server)

Is the workstation using any DNS servers other than an AD one?

No.

Windows IP Configuration

Host Name . . . . . . . . . . . . : NMHISC-XPPC1
Primary Dns Suffix . . . . . . . : nmhisc.local
DNS Suffix Search List. . . . . . : swbiolabs.com
nmhisc.local
NMHISC

Interesting, WHY do you have so much stuff in your Suffix search list?
Especially that SINGLE TAG netbios name.

It is JUST (theoretically) possible that this 'DNS' name is confusing the
client into trying to lookup a DFS root with that name and thereby getting
a permissions error.

I see no reason for NMHISC appearing in this list and it MIGHT just
conceivably be the source of the problem.

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : NMHISC

You really should NOT be using NMHISC that single label again as a
connection specific DNS name -- and in general this should not even be
used AT ALL unless the machine has more than one NIC.

Instead the Computer Name PRIMARY DNS suffix should be set to the
domain name in the System Control Panel (Computer name tab).

This may even be the source of the extra suffix -- that does not belong.

IP Address. . . . . . . . . . . . : 10.10.1.28
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.1.1
DHCP Server . . . . . . . . . . . : 10.10.1.2
DNS Servers . . . . . . . . . . . : 10.10.1.2
10.10.1.3

What is 10.10.1.2 and .3 -- are they BOTH INTERNAL DNS servers?
That is, DNS servers which can resolve ALL internal (and external) names
needed by the clients?

I had made a mistake on DHCP config and listed 2 dns servers. I correct that
now I get the following on:


Is the workstation connected to any other domains via a VPN?
Yes occasionally but not constantly. I use a citrix client and I connect
via
an ssl tunnel to another network using RDP.

That is not (technically) a VPN (probably); it is not using a DUN or RRAS
client which integrates with the computers Network Interfaces as do these
features -- e.g., when a DUN/RRAS client connects to the VPN or DIAL
an additional "network interfaces" is added to the list for the duration of
the connection. Such interfaces include additional, OVERRIDNG Default
Gateways, DNS servers, and WINS servers which can complicate local
access, including authentiction.


--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)



.

Relevant Pages

  • Re: DNS stops resolving
    ... We've always used forwarders. ... As far as DNS suffixes, ... "append parent suffixes of the primary DNS suffix" ... I'm talking about the AD integrated internal DNS servers here. ...
    (microsoft.public.win2000.dns)
  • RE: Problem applying DNS Client settings via Group Policy
    ... the policy "Register DNS with connection ... specific DNS suffix" does not actually turn on Dynamic updates for the NIC, ... register A and PTR resource records with its connection-specific DNS suffix ...
    (microsoft.public.windows.server.active_directory)
  • Re: Lost Resources
    ... Meinolf - Thank you for all you Time this morning we have found the IBM ... didn't have our DC's in their DNS as Name Servers. ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.active_directory)
  • Re: not prompting for password change
    ... In DNS, is there a DNS server in both locations? ... *** The above should match the Primary DNS Suffix. ... *** Do these two DNS servers listed above have the same exact copy of the ... *** The 'companyname.com' zone does not need to be here. ...
    (microsoft.public.win2000.active_directory)
  • Re: Server 2008 DNS across subnets
    ... DNS suffix search list is commonly assigned via Group Policy - so you might ... If you need to allow unsolicited connections from SubnetB to servers on ... SubnetA than appropriate ports need to be opened - this does not require ...
    (microsoft.public.windows.server.dns)