problem accessing share by name vs. ip address...

Hello,
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 (don't ask!).
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 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.
I had read some of Oliver's responses to a similar post here and recall him
asking about a "multi-homed" system. It just so happens this Server does
have a second NIC but it is on a subnet dedicated to data Backup. Could this
possibly be the problem? If so, would someone please explain why?
Any other ideas???
Thanks!

If the multihomed server is registering both IP addresses in WINS, that
might account for your issue - ie WINS clients are getting the IP for the
adapter on the backup subnet, but have no available route. What happens if
you try \\FQDN?

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Barry" <(E-Mail Removed)> wrote in message
news:0450EA7D-BF3B-454E-9689-(E-Mail Removed)...
> Hello,
> 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 (don't ask!).
> 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 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.
> I had read some of Oliver's responses to a similar post here and recall
him
> asking about a "multi-homed" system. It just so happens this Server does
> have a second NIC but it is on a subnet dedicated to data Backup. Could
this
> possibly be the problem? If so, would someone please explain why?
> Any other ideas???
> Thanks!
>
>

Hi Doug,
Thanks for taking the time to respond.
The secondary NIC does not have a default gateway specified so it would seem
to me the Broadcast messages would not be able to go beyond the local
subnet, or am I wrong about that?
I will have to look to make sure but I do not believe the secondary NIC is
configured to use WINS, but it is definitely worth looking into, thanks!
When I use the FQDN in the UNC path I get an "access is denied."
Regards,
Barry

"Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> If the multihomed server is registering both IP addresses in WINS, that
> might account for your issue - ie WINS clients are getting the IP for the
> adapter on the backup subnet, but have no available route. What happens
> if
> you try \\FQDN?
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "Barry" <(E-Mail Removed)> wrote in message
> news:0450EA7D-BF3B-454E-9689-(E-Mail Removed)...
>> Hello,
>> 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 (don't ask!).
>> 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 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.
>> I had read some of Oliver's responses to a similar post here and recall
> him
>> asking about a "multi-homed" system. It just so happens this Server does
>> have a second NIC but it is on a subnet dedicated to data Backup. Could
> this
>> possibly be the problem? If so, would someone please explain why?
>> Any other ideas???
>> Thanks!
>>
>>
>
>

We managed to resolve this problem today and it turned out to be a Firwall
issue after all.
Thanks to all for your help!

"Barry Oxenberg" <(E-Mail Removed)> wrote in message
news:%23$(E-Mail Removed)...
> Hi Doug,
> Thanks for taking the time to respond.
> The secondary NIC does not have a default gateway specified so it would
> seem to me the Broadcast messages would not be able to go beyond the local
> subnet, or am I wrong about that?
> I will have to look to make sure but I do not believe the secondary NIC is
> configured to use WINS, but it is definitely worth looking into, thanks!
> When I use the FQDN in the UNC path I get an "access is denied."
> Regards,
> Barry
>
> "Doug Sherman [MVP]" <(E-Mail Removed)> wrote in
> message news:(E-Mail Removed)...
>> If the multihomed server is registering both IP addresses in WINS, that
>> might account for your issue - ie WINS clients are getting the IP for the
>> adapter on the backup subnet, but have no available route. What happens
>> if
>> you try \\FQDN?
>>
>> Doug Sherman
>> MCSE, MCSA, MCP+I, MVP
>>
>> "Barry" <(E-Mail Removed)> wrote in message
>> news:0450EA7D-BF3B-454E-9689-(E-Mail Removed)...
>>> Hello,
>>> 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 (don't ask!).
>>> 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 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.
>>> I had read some of Oliver's responses to a similar post here and recall
>> him
>>> asking about a "multi-homed" system. It just so happens this Server
>>> does
>>> have a second NIC but it is on a subnet dedicated to data Backup. Could
>> this
>>> possibly be the problem? If so, would someone please explain why?
>>> Any other ideas???
>>> Thanks!
>>>
>>>
>>
>>
>
>