Hello,
I have a similar issue.
We have a file share on a machine at a remote site, different subnet, and
recently the users at our local site can no longer access the share by using
the host name in the UNC path. Accessing the share by using the IP address
of the host computer in the UNC path works.
If I do a net view \\servername from the command line I will get either a
"Network path not found" or "Access denied." If I change the command to net
view \\172.x.x.x it returns a list of shares on the target computer (Windows
Server 2003).
I can ping the target Server by host name, FQDN, and IP address. I can also
telnet to the appropriate ports on the remote machine.
Our site is a child Domain and the Server hosting the file share is in a
separate child Domain. To the best of my knowledge no Trust relationships
exist between child Domains.
WINS appears to be working correctly and I believe NetBIOS over TCP/IP is
enabled across our entire Network.
Here is the kicker...if I log in to either of our DC's (my user account has
Domain Admin privileges) I can view the list of shares on the remote Server
with no problem, by host name or IP address. To eliminate the possibility
it was an XP vs. Windows Server 2003 issue I tried from one viewing the
shares on the remote machine from one of our Windows Server 2003 file
Servers and had the same problem as when I tried from my Workstation. The
two DC's are the only machines that do not display this errant behavior.
Any ideas???
Thanks!
"Oliver O'Boyle" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I need to know exactly which one works for what. There's obviously some
>missing information in your name resolution solution.
>
> I would also be surprised if you could't access both by IP (assuming
> routing was set up for the 10 network, so we'll make that assumption).
>
> Thanks,
> Oliver
>
>> We only route class c addresses so the 10.x.x.x didn't work. but here is
>> the
>> situation:
>> -you can get the open shares ONLY by one of the following
>> -ip address
>> -host (netbios) name OR
>> -fqdn
>> BUT not all three!
>> I have several domains and this one is the only one that this happens in
>> (if
>> that makes a difference)
>>
>> "Oliver O'Boyle" wrote:
>>
>>> > Yes,
>>> > we have one nic that works for the LAN (192.168.xx.xx) and another
>>> > that is
>>> > a
>>> > class A for the data transfer between two boxes (10.x.x.x).
>>>
>>> Try \\192.168.xx.serverIP
>>>
>>> what happens?
>>>
>>> Try \\10.x.x.serverIP
>>>
>>> what happens?
>>>
>>> >
>>> > "Oliver O'Boyle" wrote:
>>> >
>>> >> > We have a domain that has a particular problem. On a server, for
>>> >> > example,
>>> >> > you
>>> >> > type in the \\servername you might get the open shares. But, if you
>>> >> > type
>>> >> > in
>>> >> > the fqdn \\servername.domain.org you won't get the open shares. OR,
>>> >> > vice
>>> >> > versa.
>>> >> > If you do a flusha and register dns and NBTSTAT -RR it might or
>>> >> > might
>>> >> > not
>>> >> > work.
>>> >> > Where can I go to troubleshoot?
>>> >> > Thanks
>>> >>
>>> >> Does the server have multiple network cards?
>>> >>
>>> >> O.
>>> >>
>>> >>
>>> >>
>>>
>>>
>>>
>
>
|
Similar Threads
Linear Mode
