none
Cannot access WHS files nor shared printer from Windows 7 workstations RRS feed

  • Question

  • I have Windows Home Server installed on my basement server, with attached printer.  I have several Windows 7 workstations throughout the house.  All have the WHS connector installed and are set up on the server for backup.  From the Win7 machines I can see the Server listed in the Network list, but when I try to open it, it refuses to open up any shared folders on the Server and the network diag box that pops up on Win7 is worthless to fix it.  The most important thing, the Win7 workstations cannot connect to the shared printer on the WHS.  I'm not sure which bogus security setting on the WHS is preventing me from accessing the printer.  The printer is shared.
    Sunday, March 7, 2010 11:22 PM

Answers

  • I fixed it.  I went to my IPv4 settings and changed the manual IP to automatic IP (which enables the DHCP) and everything went through immediately.  Go figure.

    Thank you kariya for your assistance.

    Kenn
    Monday, March 8, 2010 1:22 AM

All replies

  • I have Windows Home Server installed on my basement server, with attached printer.  I have several Windows 7 workstations throughout the house.  All have the WHS connector installed and are set up on the server for backup.  From the Win7 machines I can see the Server listed in the Network list, but when I try to open it, it refuses to open up any shared folders on the Server and the network diag box that pops up on Win7 is worthless to fix it.  The most important thing, the Win7 workstations cannot connect to the shared printer on the WHS.  I'm not sure which bogus security setting on the WHS is preventing me from accessing the printer.  The printer is shared.
    Are you getting "Access is denied" when trying to open the shares, or do you just not see any shares?  What happens if you go to \\server (replacing "server" with the name of your server)?
    Monday, March 8, 2010 12:13 AM
    Moderator
  • When I go to \\server (which is the name of my WHS) I get a "Windows cannot access \\SERVER"

    I also get a "network path not found" error also.  Which is ____ because every computer is on the same workgroup, working off the same router, and I can access all the shared folders on the Win7 workstations from the SERVER.  But, no workstations can access the SERVER folders nor the SERVER printers.  So I know it is a security setting on the SERVER. I just don't know which one it is.
    Monday, March 8, 2010 12:18 AM
  • When I go to \\server (which is the name of my WHS) I get a "Windows cannot access \\SERVER"

    I also get a "network path not found" error also.  Which is ____ because every computer is on the same workgroup, working off the same router, and I can access all the shared folders on the Win7 workstations from the SERVER.  But, no workstations can access the SERVER folders nor the SERVER printers.  So I know it is a security setting on the SERVER. I just don't know which one it is.
    Can you establish a Remote Desktop Connection to the server?  If so, you can try temporarily disabling Windows Firewall on it and see if it works.  Also, what is the color of the Connector icon in the system tray on your clients?  Have you installed any add-ins/applications on the server?  How is your server getting its IP address (DHCP or did you give it a static IP)?  If you can get to the server desktop, can you open a command prompt and type ipconfig /all on it (and one of your clients) and post the results of both here?

    EDIT:  Also, do you have any security-suite software on your clients?  Can you successfully ping the server, both by name and by IP address?
    Monday, March 8, 2010 12:25 AM
    Moderator
  • Yes, the RDC connects immediately without hesitation.  The Connector icon is red but only because one of my clients did not have updated antivirus.  No WHS add-ins, and very few apps (Office, browsers, etc., nothing security related).  DHCP.  No security suite software with firewalls.

    Microsoft Windows [Version 5.2.3790]
    (C) Copyright 1985-2003 Microsoft Corp.

    C:\Documents and Settings\Administrator>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : server
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
       Physical Address. . . . . . . . . : 00-15-58-48-04-DA
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IP Address. . . . . . . . . . . . : 192.168.2.150
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.2.1
       DHCP Server . . . . . . . . . . . : 192.168.2.1
       DNS Servers . . . . . . . . . . . : 192.168.2.1
       Lease Obtained. . . . . . . . . . : Sunday, March 07, 2010 6:24:36 PM
       Lease Expires . . . . . . . . . . : Sunday, March 14, 2010 12:53:47 AM

    C:\Documents and Settings\Administrator>

    Now from my desktop:

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Kenn>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Kenn-PC
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Marvell Yukon 88E8071 PCI-E Gigabit Ether
    net Controller
       Physical Address. . . . . . . . . : 00-1F-E2-02-B1-A8
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::9cc6:83af:7758:2ffb%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.2.66(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.2.1
       DHCPv6 IAID . . . . . . . . . . . : 218104172
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-10-B4-C5-CF-00-1F-E2-02-B1-A8

       DNS Servers . . . . . . . . . . . : 68.237.161.12
                                           151.202.0.85
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{7EA279C8-F60D-455C-84C9-2ADE16430366}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:1ca0:307b:b595:3224(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::1ca0:307b:b595:3224%13(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    C:\Users\Kenn>


    I'll try disabling the firewall on the server.... that didn't make any difference at all.  Still can't access the \\SERVER.

    Monday, March 8, 2010 12:45 AM
  • Yes, the RDC connects immediately without hesitation.  The Connector icon is red but only because one of my clients did not have updated antivirus.  No WHS add-ins, and very few apps (Office, browsers, etc., nothing security related).  DHCP.  No security suite software with firewalls.

    Microsoft Windows [Version 5.2.3790]
    (C) Copyright 1985-2003 Microsoft Corp.

    C:\Documents and Settings\Administrator>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : server
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
       Physical Address. . . . . . . . . : 00-15-58-48-04-DA
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IP Address. . . . . . . . . . . . : 192.168.2.150
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.2.1
       DHCP Server . . . . . . . . . . . : 192.168.2.1
       DNS Servers . . . . . . . . . . . : 192.168.2.1
       Lease Obtained. . . . . . . . . . : Sunday, March 07, 2010 6:24:36 PM
       Lease Expires . . . . . . . . . . : Sunday, March 14, 2010 12:53:47 AM

    C:\Documents and Settings\Administrator>

    Now from my desktop:

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Kenn>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Kenn-PC
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Marvell Yukon 88E8071 PCI-E Gigabit Ether
    net Controller
       Physical Address. . . . . . . . . : 00-1F-E2-02-B1-A8
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::9cc6:83af:7758:2ffb%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.2.66(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.2.1
       DHCPv6 IAID . . . . . . . . . . . : 218104172
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-10-B4-C5-CF-00-1F-E2-02-B1-A8

       DNS Servers . . . . . . . . . . . : 68.237.161.12
                                           151.202.0.85
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{7EA279C8-F60D-455C-84C9-2ADE16430366}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:1ca0:307b:b595:3224(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::1ca0:307b:b595:3224%13(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    C:\Users\Kenn>


    I'll try disabling the firewall on the server.... that didn't make any difference at all.  Still can't access the \\SERVER.

    What about pinging your server (I added that after the fact)?  Also, your clients might be resolving your server name out to the internet.  Try changing the DNS entries on your clients to the IP address of your router (or just change your clients to DHCP enabled).
    Monday, March 8, 2010 12:52 AM
    Moderator
  • I also tried to connect to the printer with 192.168.2.150\hplaser1022 but still get the connection error "Windows cannot connect to the printer".  I get the exact same result when I try \\server\hplaser1022 or 192.168.2.150\hplaser1022.  And the share name of the printer is correct.  When I search for network printers, it does not come up automatically.

    Monday, March 8, 2010 12:53 AM
  • Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Kenn>ping 192.168.2.150

    Pinging 192.168.2.150 with 32 bytes of data:
    Reply from 192.168.2.150: bytes=32 time<1ms TTL=128
    Reply from 192.168.2.150: bytes=32 time<1ms TTL=128
    Reply from 192.168.2.150: bytes=32 time<1ms TTL=128
    Reply from 192.168.2.150: bytes=32 time<1ms TTL=128

    Ping statistics for 192.168.2.150:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

    C:\Users\Kenn>

    So the PING worked just fine.  I'm not sure why the DHCP Enabled on my client says NO because when I run services.msc the DHCP Server is set to Automatic and is active.  Where do I find that setting in Win7?

    I'll change the DNS to 192.168.2.1 and see if that works.

    Monday, March 8, 2010 1:06 AM
  • I changed the DNS to 192.168.2.1 and nothing changed with the permissions.
    Monday, March 8, 2010 1:11 AM
  • After changing the DNS on my client, the ipconfig now looks like this:

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Kenn>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Kenn-PC
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Marvell Yukon 88E8071 PCI-E Gigabit Ether
    net Controller
       Physical Address. . . . . . . . . : 00-1F-E2-02-B1-A8
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::9cc6:83af:7758:2ffb%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.2.66(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.2.1
       DHCPv6 IAID . . . . . . . . . . . : 218104172
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-10-B4-C5-CF-00-1F-E2-02-B1-A8

       DNS Servers . . . . . . . . . . . : 192.168.2.1
                                           68.237.161.12
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{7EA279C8-F60D-455C-84C9-2ADE16430366}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:1ca0:307b:b595:3224(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::1ca0:307b:b595:3224%13(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    C:\Users\Kenn>

    Monday, March 8, 2010 1:14 AM
  • Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Kenn>ping 192.168.2.150

    Pinging 192.168.2.150 with 32 bytes of data:
    Reply from 192.168.2.150: bytes=32 time<1ms TTL=128
    Reply from 192.168.2.150: bytes=32 time<1ms TTL=128
    Reply from 192.168.2.150: bytes=32 time<1ms TTL=128
    Reply from 192.168.2.150: bytes=32 time<1ms TTL=128

    Ping statistics for 192.168.2.150:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

    C:\Users\Kenn>

    So the PING worked just fine.  I'm not sure why the DHCP Enabled on my client says NO because when I run services.msc the DHCP Server is set to Automatic and is active.  Where do I find that setting in Win7?

    I'll change the DNS to 192.168.2.1 and see if that works.

    What about pinging by name (I asked that after my original post)?

    DHCP Settings in 7:  Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings > right-click on the network adapter > Properties > TCP/IPv4, then Properties.

    Also, I just realized that your node on your server is "unknown".  You might try the steps shown in KB310570.
    Monday, March 8, 2010 1:20 AM
    Moderator
  • I fixed it.  I went to my IPv4 settings and changed the manual IP to automatic IP (which enables the DHCP) and everything went through immediately.  Go figure.

    Thank you kariya for your assistance.

    Kenn
    Monday, March 8, 2010 1:22 AM
  • I am having almost the same problem. My x64 Win7 client gets "Access is Denied" to shares on my server but other clients on my home network see the shares fine including a different windows 7 client. It worked fine from this client one day (March 4) and the next it just stopped (March 5). The client and server have now been rebooted. No updates were applied to the client machine from when it did work to now.

    Server:
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : PURPLETEETH
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : hsd1.wa.comcast.net.
    
    Ethernet adapter Local Area Connection:
    
       Connection-specific DNS Suffix  . : hsd1.wa.comcast.net.
       Description . . . . . . . . . . . : SiS191 1000/100/10 Ethernet Device
       Physical Address. . . . . . . . . : 00-0A-E4-87-33-49
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IP Address. . . . . . . . . . . . : 194.165.1.100
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 194.165.1.1
       DHCP Server . . . . . . . . . . . : 194.165.1.1
       DNS Servers . . . . . . . . . . . : 68.87.69.146
                                           68.87.85.98
       Lease Obtained. . . . . . . . . . : Sunday, March 07, 2010 4:40:52 PM
       Lease Expires . . . . . . . . . . : Monday, March 08, 2010 4:40:52 PM
    
    Client:
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : WOW64
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : hsd1.wa.comcast.net.
    
    Wireless LAN adapter Wireless Network Connection:
    
       Connection-specific DNS Suffix  . : hsd1.wa.comcast.net.
       Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
       Physical Address. . . . . . . . . : 00-21-6B-45-02-0A
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::891b:29ff:b517:4a83%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 194.165.1.105(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Sunday, March 07, 2010 8:48:02 AM
       Lease Expires . . . . . . . . . . : Monday, March 08, 2010 8:47:59 AM
       Default Gateway . . . . . . . . . : 194.165.1.1
       DHCP Server . . . . . . . . . . . : 194.165.1.1
       DHCPv6 IAID . . . . . . . . . . . : 184557931
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-7D-31-40-00-23-8B-21-D9-F4
    
       DNS Servers . . . . . . . . . . . : 68.87.69.146
                                           68.87.85.98
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ping to server from client by name or ipaddress works.
    Ping FROM server to client does not (times out). But the ping from the server to other client machines works fine.
    Monday, March 8, 2010 3:59 AM
  •    Node Type . . . . . . . . . . . . : Unknown
     Better would be hybrid in context with NetBIOS over TCP/IP enabled.
       DNS Suffix Search List. . . . . . : hsd1.wa.comcast.net.
    Should be empty!

       Connection-specific DNS Suffix  . : hsd1.wa.comcast.net.
    Should be empty!

       Physical Address. . . . . . . . . : 00-0A-E4-87-33-49
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IP Address. . . . . . . . . . . . :      194.165.1.100
       Subnet Mask . . . . . . . . . . . :    255.255.255.0
       Default Gateway . . . . . . . . . :  194.165.1.1
       DHCP Server . . . . . . . . . . . :     194.165.1.1

    These are not the allowed addresses for a private network, so it is either a not legal (since other people/companies may own these addresses, maybe the DHCP server in the router is misconfigured), strange (maybe it is an ISP specific thing which I do not know about) or eventually not supported use of IP addresses (the later two, if you or your company own these addresses). You simply do not want addresses directly routable to the Internet in your home network in most cases.

       DNS Servers . . . . . . . . . . . : 68.87.69.146
                                                   68.87.85.98

    Also these settings look wrong, in most home networks with own routers this should only contain the routers internal IP address as DNS server.
    So you have a lot of configuration issues, which may each alone cause connectivity trouble.

    For more details also check the FAQ How to Troubleshoot Network Connection Problems with Windows Home Server.

    Best greetings from Germany
    Olaf
    Monday, March 8, 2010 9:47 PM
    Moderator