Can ping but cannot browse network shares from new subnet

[samshedd]

We have created a new subnet 172.18.x.x on it's own VLAN and I believe
I have the VLAN setup and routed properly. We have another subnet of
172.16.x.x which our Windows 2000 servers are on. From a XP client on
the new 18 subnet, I can ping our servers on the 16 subnet ok, by name
and by IP address. I can also ping the client's IP and name from the
16 subnet. What I'm having a problem with is browsing to \\servername
on the 16 subnet from the client on the 18 subnet. I also cannot
browse to a share on the client from the server. What could be causing
this?

 

[Kurt]

We have created a new subnet 172.18.x.x on it's own VLAN and I believe
I have the VLAN setup and routed properly. We have another subnet of
172.16.x.x which our Windows 2000 servers are on. From a XP client on
the new 18 subnet, I can ping our servers on the 16 subnet ok, by name
and by IP address. I can also ping the client's IP and name from the
16 subnet. What I'm having a problem with is browsing to \\servername
on the 16 subnet from the client on the 18 subnet. I also cannot
browse to a share on the client from the server. What could be causing
this?

"Browsing" (My Network Places) is broadcast based. Broadcasts don't pass
across routed links. If you want to be able to browse, you'll need WINS.
I'm a little confused about your terminology, you don't normally
"browse" to a UNC path. If you can resolve the fqdn, DNS is working. If
you need to resolve the netbios name, WINS is your answer.

 

[SheddTec]

"Browsing" (My Network Places) is broadcast based. Broadcasts don't pass
across routed links. If you want to be able to browse, you'll need WINS.
I'm a little confused about your terminology, you don't normally
"browse" to a UNC path. If you can resolve the fqdn, DNS is working. If
you need to resolve the netbios name, WINS is your answer.

The part that is confusing is I can resolve both the fqdn and the
netbios name. But when I try to open the network shares with \
\servername. I get the error "No network provider accepted the given
network path." So it does not appear that I am having a resolution
issue, is WINS still necessary?

 

[SheddTec]

The part that is confusing is I can resolve both the fqdn and the
netbios name. But when I try to open the network shares with \
\servername. I get the error "No network provider accepted the given
network path." So it does not appear that I am having a resolution
issue, is WINS still necessary?

I have installed and setup WINS, I still see nothing in Network Places
and cannot access network shares. What is next?

 

[Moderator]

hi, have your tried to allow broadcast traffing thru? win2k broadcasts too
much (due to netbios) and this is the main reason why we're now upgrading to
win2k3 (netbios is not needed) for all our remote, routed sites. WINS, IMHO,
can't help as i've tried it and never got anything working.

 

[Kurt]

I have installed and setup WINS, I still see nothing in Network Places
and cannot access network shares. What is next?

You've installed and set up WINS on the server and made the necessary
_client_ entries (via DHCP, hopefully or statically if that's how you're
set up) so that they will register themselves? Clients that are
configured to use a WINS server register themselves when they boot up,
so you'll likely have to reboot the whole bunch before you'll get any
registrations. Once that happens, you should start seeing any registered
computer in My Network Places. You can check for client registrations in
the WINS snap-in.

From your earlier post, "No network provider accepted the given network
path", means that as far as it knows, the network path does not exist,
or in other words, it couldn't identify the path as given which was the
computername. Remember, ping is part of the TCP/IP protocol, and will
resolve using the hostname (which is the same as the netBIOS name less
the ".whatever") by default.

....kurt

 

[SheddTec]

You've installed and set up WINS on the server and made the necessary
_client_ entries (via DHCP, hopefully or statically if that's how you're
set up) so that they will register themselves? Clients that are
configured to use a WINS server register themselves when they boot up,
so you'll likely have to reboot the whole bunch before you'll get any
registrations. Once that happens, you should start seeing any registered
computer in My Network Places. You can check for client registrations in
the WINS snap-in.

From your earlier post, "No network provider accepted the given network
path", means that as far as it knows, the network path does not exist,
or in other words, it couldn't identify the path as given which was the
computername. Remember, ping is part of the TCP/IP protocol, and will
resolve using the hostname (which is the same as the netBIOS name less
the ".whatever") by default.

...kurt

Well, I just found out, Sonicwall is having multiple users report a
similar problem as mine with the 3.5 enhanced firmware. Specifically,
the firewall rules are not being enforced properly, so netbios was
being blocked at the firewall. So now the problem is in their labs...
thank god the services on this subnet aren't in production yet.