Re: Can ping but cannot browse network shares from new subnet
- From: Kurt <kurtl@xxxxxxxxxxxxxxxxx>
- Date: Wed, 21 Feb 2007 20:38:59 -0800
SheddTec wrote:
On Feb 20, 9:19 am, "SheddTec" <samsh...@xxxxxxxxx> wrote:On Feb 19, 9:13 pm, Kurt <k...@xxxxxxxxxxxxxxxxx> wrote:
samsh...@xxxxxxxxx wrote:The part that is confusing is I can resolve both the fqdn and theWe have created a new subnet 172.18.x.x on it's own VLAN and I believe"Browsing" (My Network Places) is broadcast based. Broadcasts don't pass
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?
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.
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?
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
.
- Follow-Ups:
- References:
- Prev by Date: Re: Network share limit
- Next by Date: Laptop to Desktop but not back - please help
- Previous by thread: Re: Can ping but cannot browse network shares from new subnet
- Next by thread: Re: Can ping but cannot browse network shares from new subnet
- Index(es):
Relevant Pages
|
