Sign in to follow this  
Followers 0
discombooberate

Cannot Access Shared Folders Or Whs Through Console

2 posts in this topic

A friend of mine was helping set up my Mac so I could use remote desktop to access my whs. Remote desktop works fine now, however my other Windows 7 machines cannot see the server in Windows Explorer. I think he monkeyed with the wrong setting. Here's a list of what is/isn't working:

Works

- Remote Desktop Connection

- Windows Home Server Network status is green

- All backups for both Windows 7 machines are working

- I can access all files through Windows Media Connect on the Xbox and PS3

- Can access the server drives in the Finder window on Mac OS X

Not Working

- Cannot access the server through the Windows Home Server Console on the Windows 7 machines. Error "This computer cannot connect to your home server. Check your network connection and make sure your home server is powered on. If your home server has recently restarted, try again in a few minutes."

- Server does not appear under "Computers" in the Windows Explorer Network tab on Win7 machines. It does appear under "Media Devices" and "Other Devices" but I cannot connect to it through either one.

- Mapped server drives on Win7 machines are broken.

I've spent a few days on the forum trying different things but I haven't had any luck. I have tried the registry fix . I have static IP's set for all the machines in my house. I think my 'friend' (who is not allowed in my house until this is fixed) was playing with settings in "Administrative Tools", broke something, and then left me holding the bag.

ANY help would be much appreciated!! All of my iTunes music is stored on the server and it is currently inaccessible!

Thanks!

Share this post


Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

I've found that the best bet is to run the connector troubleshooter, as it has a lot of network related tests that should "root out the problem".

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0



Upgrade to a WGS Supporter Account to remove this ad.



  • Posts

    • RODCs only work with "active" services like DHCP when the RWDC (your DC) is still active.  If the RODC can't get the information from the RWDC, then the DHCP service stops on the RODC.   The problem is, since the RODC is read-only, it can't write back the DHCP lease information to AD, especially if your only read-write domain controller is down.   DNS and Global Catalog (AD authentication) works as long as clients are only reading from it, but DNS changes won't update if a client's only DNS server is a RODC.   AD best-practices is to have a minimum of two RWDCs for any domain (which Microsoft itself doesn't follow with the Essentials product in the first place), so that you have another writable domain controller that can update information in the event the primary goes offline.
    • That's not how WAN uplinks work.  Except for very specific circumstances*, you won't be able to aggregate separate WAN links into one large WAN "pipe" with combined bandwidth to a single destination.  TCP/IP doesn't work that way, and even in the event you somehow jury rig half of an IMUX'ed (inversely multiplexed) connection with three very different WAN connections, most intelligent security devices on the public Internet will simply reject TCP [SYN,ACKs] they never received an initial TCP [SYN] from -- asymmetric routing will just be outright rejected.   Most smart security devices can support multiple WAN connections (usually two with a third as a warm spare backup), but done in such a way that there's a defined primary connection, a designated backup/failover connection...or done in such a way that each outgoing connection uses a separate WAN link, or in an active/backup/cellular failover or active/active/cellular failover configuration in the case of Cisco's Meraki hardware   To illustrate how it'd work, say you have three connections:  LTE-1, LTE-2 and ADSL.  So you have Netflix open.  That connection to Netflix is only going to take a single path (LTE-1), since each path has its own public IP address.  If you then decide to go to YouTube in a new browser tab, that YouTube connection may take a separate path (LTE-2), depending on how you have the uplinks configured.  Then you decide to stream Pandora from a third browser tab -- that Pandora stream may also take the last path available (ADSL), but each media stream will still be limited to the bandwidth of the path it's taken and won't be aggregated to a single connection equaling the sum of all three WAN uplinks.   *The only scenario in which WAN aggregation works as a combined WAN "pipe" is if you have a single ISP that can terminate a group of identical media types between you and their edge before going out to the Internet -- such as a group of DS1s or DS3s (or IMA -- Inverse Multiplexing over ATM) connections from your edge device to their first hop edge.  In that scenario, the WAN bundle is only going between you and your ISP, but that requires ISP support, additional ISP-provided hardware, and is usually VERY EXPENSIVE to implement for a home user.
    • I've been thinking about using W10 as my server recently.  MS has pretty much killed the home server market via pricing and poor support like the issue you ran into.  Essentials is an after thought for MS. The one thing that keeps me from moving to W10 is the remote access piece, but since that is not a requirement for you, I'd suggest W10.
    • I posted this in the wrong place. It should have been in the WHS 2011 > Lights-Out section where there is already a discussion about LO problems with the Windows 10 feature update: http://forum.wegotserved.com/index.php?/topic/31064-win-10-anniv-update-breaks-lo-client/  
    • I have resolved my problem by accessing http://server/connect and running the client installer.
  • Popular Contributors