problems resolving UNC paths

  • Thread starter Thread starter Timboi
  • Start date Start date
T

Timboi

Hi,

I've setup a win2k DC and connected a XP pro WS to
domain. For some reason the WS machine cannot connect to
UNC paths with domain names in it but can connect to UNC
paths with IP address in. However, the WS can resolve the
domain name in a ping, and if you browse the network
(using My Netowrk places) you cannot connect to shared
folders that appear in the initial window, but if you
select 'Entire Nwtwork' and then 'Microsoft Windows
Network' I am able to get to the folders that I am denied
via UNC addresses. What's going on here? Is this a DNS
issue or some sort of RPC issue?
The network connection has correct address for DNS

cheers,
Timboi
 
In
Timboi said:
Hi,

I've setup a win2k DC and connected a XP pro WS to
domain. For some reason the WS machine cannot connect to
UNC paths with domain names in it but can connect to UNC
paths with IP address in. However, the WS can resolve the
domain name in a ping, and if you browse the network
(using My Netowrk places) you cannot connect to shared
folders that appear in the initial window, but if you
select 'Entire Nwtwork' and then 'Microsoft Windows
Network' I am able to get to the folders that I am denied
via UNC addresses. What's going on here? Is this a DNS
issue or some sort of RPC issue?
The network connection has correct address for DNS

cheers,
Timboi
Click to expand...

Network Neighborhood does not use DNS it uses NetBIOS, so I'm not sure what
is going on there.

The XP client is pointing to the DC for DNS only, correct?
 
-----Original Message-----
In Timboi <[email protected]> posted a question
Then Kevin replied below:

Network Neighborhood does not use DNS it uses NetBIOS, so I'm not sure what
is going on there.

The XP client is pointing to the DC for DNS only, correct?
Click to expand...

Kevin,

Thanks for your response. We were actually the problem -
getting confused with the machine name Vs the NetBIOS
domian name (we were entering the NetBIOS domain name in
the UNC path instead of the machine name - duh!).
We would have figured this out alot longer ago, but
strangely it seems that we were able to connect to SYSVOL
using the NetBIOS name in the UNC (but no other share
worked this way) so this sort of threw us off the right
track and we initially thought it was a wierd permissions
problem. The other thing is if you put the domian NetBIOS
name only in a UNC path, all the shares will be
displayed, but you cannot connect to any of them except
SYSVOL.

cheers,
Timboi
 
-----Original Message-----
In Timboi <[email protected]> posted a question
Then Kevin replied below:

Network Neighborhood does not use DNS it uses NetBIOS, so I'm not sure what
is going on there.

The XP client is pointing to the DC for DNS only, correct?
Click to expand...

Kevin,

Thanks for your response. We were actually the problem -
getting confused with the machine name Vs the NetBIOS
domian name (we were entering the NetBIOS domain name in
the UNC path instead of the machine name - duh!).
We would have figured this out alot longer ago, but
strangely it seems that we were able to connect to SYSVOL
using the NetBIOS name in the UNC (but no other share
worked this way) so this sort of threw us off the right
track and we initially thought it was a wierd permissions
problem. The other thing is if you put the domian NetBIOS
name only in a UNC path, all the shares will be
displayed, but you cannot connect to any of them except
SYSVOL.

cheers,
Timboi
 
Back
Top