Answered by:
"network path was not found"

Question
-
I've just installed WHS and the Connector on two of our PCs. I am able to log into the server through the Connector, but when I try to access the shares I get a "network path was not found"error. I can even see (through the connector) if a folder is empty or how much data it contains, but I can't access the folders through the Connector.
Anyone have an idea of what is going wrong here?
- Moved by Lara JonesModerator Friday, January 23, 2009 3:25 AM moving to correct forum (Moved from Windows Home Server Hardware and Installation to Windows Home Server Software)
Friday, January 23, 2009 3:01 AM
Answers
-
Problem solved!! I had IPX/SPX protocols installed. I had previously unchecked the box in my Network Connection Properties, but I hadn't uninstalled it. When I uninstalled IPX/SPX, my 'File and Printer Sharing for Microsoft Networks' and 'Client for Microsoft Networks' became unchecked. I don't know if they are supposed to be checked, but I re-checked them anyway and restarted my machine. Everything appears to be working now!
My thanks to Olaf, brubber, and Colin for your time and efforts. This setup might just work afterall!
~Karen
SOLUTION: Don't just uncheck IPX/SPX in 'Network Connection Properties', completely uninstall it.
- Marked as answer by Knrothwell Sunday, January 25, 2009 4:57 AM
Sunday, January 25, 2009 4:57 AM
All replies
-
Hi,
You cannot use the Connector to access the WHS folders, on installation there will have been a shortcut named Shared Folders created on the desktop of each Client. Alternatively, 'right-click' on the Connector icon by your time in the Taskbar and select Shared Folders.
HTH,
Colin
If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.Friday, January 23, 2009 6:30 PMModerator -
This type of problem is often due to incorrect network or firewall configuration. Some basic things to check:
1. Please check your firewall configuration, it should allow NETBIOS ports on your local network. For windows firewall enable file and printersharing in the firewall, any other firewall please read the manual.
2. In most home networks client PC's get their IP address and other TCP/IP settings such as Default Gateway and DNS server addresses from a router (sometimes also the modem). The router should be configured properly for home networking, which means that one of the DNS server addresses points to the router. For example if the router has an IP address 192.168.1.1 in most cases Default Gateway and DNS server addresses are also 192.168.1.1. You can simply check the settings on client PC:
a. Open a command prompt, type ipconfig /all and hit Enter
b. This command will list the relevant TCP/ IP settings. in general DHCP server, DNS server and Default Gateway all have the same address. It's possible to have multiple DNS server addresses, as long as one is identical to the Default Gateway/DHCP server address.
Friday, January 23, 2009 7:24 PMModerator -
Colin Hodgson said:Maybe I'm using the wrong terminology then. I am now able to access files, through the Windows Home Server Console (by going to 'Shared Folders' and choosing 'Open' for the folder I want to access), but only on three out of the four machines I'm trying to install on. I can access the shares on one wired PC and two wireless PCs, but I'm still not able to access the shares through my laptop.
Hi,
You cannot use the Connector to access the WHS folders
Saturday, January 24, 2009 1:31 AM -
The machine I'm having issues with is my laptop (connecting wirelessly). I've connected two other PCs wirelessly and they seem to be working correctly.
On the laptop, I can connect to the Windows Home Server Console and see the server. I can even backup my laptop to the server. But, I can't access the shares. If I click on the 'Shared Folders' from the icon in the taskbar, I get the message "Cannot open Windows Home Server Shares. Please check the access permissions and try again." I do not get the authentication box that pops up when I chose the same option on my other machines.
Here's the ipconfig /all for the "broken" machine:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : KarensNotebook
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gateway.2wire.net
Ethernet adapter Wireless Network Connection 2:
Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Belkin 802.11g Network Adapter
Physical Address. . . . . . . . . : 00-11-50-7C-CF-5F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.72
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Friday, January 23, 2009 5:01:53 PM
Lease Expires . . . . . . . . . . : Saturday, January 24, 2009 5:01:53 PMAnd here's the ipconfig/ all for one of the machines that is working correctly:
Windows IP Configuration
Host Name . . . . . . . . . . . . : daBoyz
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gateway.2wire.net
Ethernet adapter Wireless Network Connection 5:
Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : 2Wire 802.11g USB Wireless LAN Card #3
Physical Address. . . . . . . . . : 00-60-B3-5F-D1-51
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.68
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Friday, January 23, 2009 4:13:31 PM
Lease Expires . . . . . . . . . . : Saturday, January 24, 2009 4:13:31 PMAny help would be great! I'm completely out of my element here. Thanks!
eta: I forgot to mention that I've disabled the firewall on the laptop, so, I don't think that's the issue here.
Saturday, January 24, 2009 1:51 AM -
This appears to be a different issue then the one you originally reported. To help others can you please indicate how you solved you original issue? (or is this issue still there and is your current method a workaround.
For the new issue, please start with enabling the firewall! Disabling firewall is a major risk, especially when connected to the internet! Then please read Access and password problems
Saturday, January 24, 2009 3:30 AMModerator -
No worries, I enabled the firewall after my tests with it disabled didn't solve the problem. :)
Well, the problem seems to be resolved on one of the PCs I was trying to get running. I've no idea what changed on that one. I tried it and found it still not to be working before I went to bed and when I woke up and tried it again, it was working on that machine (without a restart or anything else). So, who knows?The issue on the machine that is still not working is the same issue I initially reported. When I try to access the shares through the Console I get the error "network path was not found". When I try to access the shares through the icon in the task bar, I get "Cannot open Windows Home Server Shares. Please check the access permissions and try again."
I'm confused and a bit amused by the fact that I can access the shares from the other computers using the log in name and password from my laptop (the machine it's not working on).
I did intially have a conflict with the log in name and display name being different, but I fixed that yesterday and it hasn't made a difference with this problem.
Any other ideas? Thanks for all your help!
Saturday, January 24, 2009 4:44 AM -
Hi,
the name resolution could have problems with Connection-specific DNS Suffix . : gateway.2wire.net
This means, if the client tries to resolve a name via DNS, it will ask for the name of the machine with that suffix attached and attempt to resolve the name in the Internet.Another reason could be, if you edited the hosts file in C:\Windows\system32\drivers\etc to point to your server for fixing a name resolution issue and the server changed it's IP address since that time.
Can the machine ping the server by name and by IP address?
What is the output of nslookup server from the client (change server against the machines real name)?
The output of ipconfig /all on the server could also be helpful.Best greetings from Germany
OlafSaturday, January 24, 2009 11:21 AMModerator -
[quote] the name resolution could have problems with Connection-specific DNS Suffix . : gateway.2wire.net
This means, if the client tries to resolve a name via DNS, it will ask for the name of the machine with that suffix attached and attempt to resolve the name in the Internet. [/quote]
If that is the problem, how would I go about fixing it?
[quote]Another reason could be, if you edited the hosts file in C:\Windows\system32\drivers\etc to point to your server for fixing a name resolution issue and the server changed it's IP address since that time. [/quote]
I have never edited the hosts file, but I took a look and there are lots of entries placed there by Spybot - Search & Destroy, but they all are set to 127.0.0.1 .
[quote]Can the machine ping the server by name and by IP address? [/quote]
Yes, I can ping the server by name and IP address:
C:\Documents and Settings\Owner>ping server
Pinging server.gateway.2wire.net [192.168.0.79] with 32 bytes of data:
Reply from 192.168.0.79: bytes=32 time=2ms TTL=128
Reply from 192.168.0.79: bytes=32 time=2ms TTL=128
Reply from 192.168.0.79: bytes=32 time=2ms TTL=128
Reply from 192.168.0.79: bytes=32 time=2ms TTL=128
Ping statistics for 192.168.0.79:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms
C:\Documents and Settings\Owner>ping 192.168.0.79
Pinging 192.168.0.79 with 32 bytes of data:
Reply from 192.168.0.79: bytes=32 time=2ms TTL=128
Reply from 192.168.0.79: bytes=32 time=1ms TTL=128
Reply from 192.168.0.79: bytes=32 time=2ms TTL=128
Reply from 192.168.0.79: bytes=32 time=2ms TTL=128
Ping statistics for 192.168.0.79:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
[quote]What is the output of nslookup server from the client (change server against the machines real name)? [/quote]
C:\Documents and Settings\Owner>nslookup server
Server: home
Address: 192.168.0.1
Name: server.gateway.2wire.net
Address: 192.168.0.79
[quote]The output of ipconfig /all on the server could also be helpful. [/quote]
Here it is:
C:\Documents and Settings\Administrator>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : server
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gateway.2wire.net
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : VIA Rhine II Compatible Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0E-A6-D1-2E-35
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.79
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Saturday, January 24, 2009 9:24:52 AM
Lease Expires . . . . . . . . . . : Sunday, January 25, 2009 9:24:52 AMThanks for your help! Short of completely reformatting my laptop drive, reinstalling XP and trying to install the Console again, I'm out of ideas.
-Karen
Saturday, January 24, 2009 7:25 PM -
Hi Karen,
(unfortunately the forum seems not to support the syntax for quoting you know from other places.)
[quote] the name resolution could have problems with Connection-specific DNS Suffix . : gateway.2wire.net
This means, if the client tries to resolve a name via DNS, it will ask for the name of the machine with that suffix attached and attempt to resolve the name in the Internet. [/quote]
If that is the problem, how would I go about fixing it?Check the configuration of your router. Somewhere in the DHCP entries of the router or on another place in your router settings this entry is configured. At least the results of accessing the server, while attaching the DNS suffix to the server name, seem to resolve properly to the internal name in your case. What happens, if you type \\server.gateway.2wire.net\software or \\server\software in Start/Run on the client?
On the client, in Control Panel/Network Connections right click the LAN connection, select Properties, open Internet Protocol (TCP/IP) and click Advanced.
Navigate to the WINS tab and select the radio button NetBIOS over TCP/IP. Click OK, until all dialogs are closed, and reboot.
Do the same on the server.
Give the machines some time to build the NetBIOS master browser list and try now to access a share again.The usual hosts file is very clean, only some example entries are there. Maybe the best is to copy this file from another machine to that folder.
Do you have a 3rd party firewall on that client? Such things can also disturb the access to shared folders in the network, so I usually recommend to uninstall those.
Best greetings from Germany
OlafSaturday, January 24, 2009 9:18 PMModerator -
Yes, I noticed my syntax was off for the forum, but I'd no idea what the correct syntax was. So, I left it figuring that anyone reading would hopefully be able to decipher what I had meant to do/say. I did mention I was out of my element here, right? :D
I haven't been able to locate where in the router the info you mentioned is. I'm leaning toward this being a machine specific problem though, not a router issue. I'm only having this problem on one out of four machines, two of which are also connecting wirelessly. Also, when I choose "View workgroup computers" in My Network Places, nothing appears. On the rest of the machines, I am able to view the other machines in the workgroup. When I type in: \\server.gateway.2wire.net\software and \\server\software, I get "No network provider accepted the given network path."
I did as you suggested with the NetBIOS over TCP/IP on the client and server (on the client, I did this both for the LAN and the Wireless connection), but I'm still having the same issue.
There was a backup of the clean hosts file saved in the same folder as the hosts file that had been edited. I renamed the backup to replace the hosts file and restarted, but still no resolution to the problem.
I did have Comodo Firewall installed and I uninstalled that and am now just using Windows Firewall (and I made sure I have printer and file sharing enabled). But, that didn't fix the issue either.
And so the search for a solution continues ...
Thanks again for all your help, I really appreciate it!
Karen
Saturday, January 24, 2009 11:46 PM -
Problem solved!! I had IPX/SPX protocols installed. I had previously unchecked the box in my Network Connection Properties, but I hadn't uninstalled it. When I uninstalled IPX/SPX, my 'File and Printer Sharing for Microsoft Networks' and 'Client for Microsoft Networks' became unchecked. I don't know if they are supposed to be checked, but I re-checked them anyway and restarted my machine. Everything appears to be working now!
My thanks to Olaf, brubber, and Colin for your time and efforts. This setup might just work afterall!
~Karen
SOLUTION: Don't just uncheck IPX/SPX in 'Network Connection Properties', completely uninstall it.
- Marked as answer by Knrothwell Sunday, January 25, 2009 4:57 AM
Sunday, January 25, 2009 4:57 AM -
Well done and thanks for posting the solution!Sunday, January 25, 2009 10:19 AMModerator