Jump to content
RESET Forums (homeservershow.com)
JerryW

Home Server Status

Recommended Posts

JerryW

Yes Jerry the server name is listed (SERVER). I don't use the WHS Web Domain URL, my router is an old Linksys and is not setup for web access. Previous versions of HSS had the same problems. I did notice HSS icon now stays blue with "0%" as if it was backing up, but it never advances it just stays at "0%".

 

Seems like the shared folders menu item is ghosted, and the tray icon never changes color, stays black=Offline..

 

I don't have enough information to determine why HSS is not running properly on your end. My only suggestion, right now, is a communications problem between your computer and the home server. Why? Well, you are saying that the icon is referring to you being offline. The shared folders menu item merely points to your server name and the root of your shares on the server.

 

Here some questions to bounce off your mind:

 

Can you ping the hostname of your server, from your computer and get a reply, not timeouts?

Have you checked your event logs for .NET framework errors, authentication errors, etc.?

Does your backups run as expected?

Is this computer wired or wireless?

Do you have another computer to try the application on?

Have you re-installed or done a repair on the .NET Framework 4?

Have you re-installed or done a repair on your WHS 2011 Connector?

 

HSS stands alone and is not a server-based add-in. It relies on the information from the MS WHS 2011 Connector and .NET Framework 4. Any problems with either and you may encounter issues.

 

I want your experience with my application to be a good one and I apologize, that so far, it has not.

Edited by JerryW

Share this post


Link to post
Share on other sites
WalterS

Hi Jerry, I can't ping the host either "SERVER" or ip address, it times out =o packets.

My system is wired (my server is next to my desktop). Backups do run normally via the launchpad or automatically.

I tried the application on two other computers on the network with the same results.

The WHS 2011 Connector works normally on all computers on the network.

 

I did notice under System Services The entry MS.NET Framework v4.0.30319_x86 is not running, when I try to start it, it starts and stops. (?) also the entry ASP.NET State Service is running.(?)

In "msconfig" the entry Net Framework NGEN is in a stopped state.

I haven't done anything to the .NET Framework 4.

any other ideas? I'm determined to get this to work,

 

thanks Walt.

Share this post


Link to post
Share on other sites
ikon

Hi Jerry, I can't ping the host either "SERVER" or ip address, it times out =o packets.

My system is wired (my server is next to my desktop). Backups do run normally via the launchpad or automatically.

You can't ping your server but your backups work?????? That, hmmm, seems kinda impossible. If you really can't ping the server you've got network problems.

 

Try this: ping 127.0.0.1

If that works (it should), then ping <local computer IP>

Share this post


Link to post
Share on other sites
WalterS

HI IKON, Yup i tried it

i can ping 127.0.0.1

I can ping several other computers in my network.

when i ping the SERVER or ip 192.168.1.101 it times out..nothing.(?)

Take a look (I'm Lost, its beyond me)

 

Microsoft Windows [Version 6.1.7601]

Copyright © 2009 Microsoft Corporation. All rights reserved.

 

C:\Users\Dad's Desktop>ping 127.0.0.1

 

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

 

Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

(SERVER)

C:\Users\Dad's Desktop>ping 192.168.1.101

 

Pinging 192.168.1.101 with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

 

Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

Router Linksys WRT54GS

C:\Users\Dad's Desktop>ping 192.168.1.1

 

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

 

Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

SERVER

C:\Users\Dad's Desktop>ping server

 

Pinging SERVER [fe80::3196:5f85:196c:43ef%10] with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

 

Ping statistics for fe80::3196:5f85:196c:43ef%10:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

MY Desktop

C:\Users\Dad's Desktop>ping buddy

 

Pinging Buddy [fe80::d0be:a1ba:477c:4d9d%10] with 32 bytes of data:

Reply from fe80::d0be:a1ba:477c:4d9d%10: time<1ms

Reply from fe80::d0be:a1ba:477c:4d9d%10: time<1ms

Reply from fe80::d0be:a1ba:477c:4d9d%10: time<1ms

Reply from fe80::d0be:a1ba:477c:4d9d%10: time<1ms

 

Ping statistics for fe80::d0be:a1ba:477c:4d9d%10:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

Son's Computer

C:\Users\Dad's Desktop>ping paul

 

Pinging Paul [fe80::813c:8817:530c:7ead%10] with 32 bytes of data:

Reply from fe80::813c:8817:530c:7ead%10: time=5ms

Reply from fe80::813c:8817:530c:7ead%10: time=5ms

Reply from fe80::813c:8817:530c:7ead%10: time=5ms

Reply from fe80::813c:8817:530c:7ead%10: time=5ms

 

Ping statistics for fe80::813c:8817:530c:7ead%10:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 5ms, Maximum = 5ms, Average = 5ms

 

Son's Computer

C:\Users\Dad's Desktop>ping GG

Ping request could not find host GG. Please check the name and try again.

 

C:\Users\Dad's Desktop>ping gg-desktop

 

Pinging GG-Desktop [fe80::890b:b15e:c3c0:2bbe%10] with 32 bytes of data:

Reply from fe80::890b:b15e:c3c0:2bbe%10: time=2ms

Reply from fe80::890b:b15e:c3c0:2bbe%10: time=1ms

Reply from fe80::890b:b15e:c3c0:2bbe%10: time=1ms

Reply from fe80::890b:b15e:c3c0:2bbe%10: time=1ms

 

Ping statistics for fe80::890b:b15e:c3c0:2bbe%10:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 2ms, Average = 1ms

 

Son's Computer

C:\Users\Dad's Desktop>ping charles

 

Pinging Charles [fe80::ddc8:8a06:f18a:309b%10] with 32 bytes of data:

Reply from fe80::ddc8:8a06:f18a:309b%10: time<1ms

Reply from fe80::ddc8:8a06:f18a:309b%10: time<1ms

Reply from fe80::ddc8:8a06:f18a:309b%10: time<1ms

Reply from fe80::ddc8:8a06:f18a:309b%10: time<1ms

 

Ping statistics for fe80::ddc8:8a06:f18a:309b%10:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

My Desktop

C:\Users\Dad's Desktop>ping 192.168.1.117

 

Pinging 192.168.1.117 with 32 bytes of data:

Reply from 192.168.1.117: bytes=32 time=5ms TTL=64

Reply from 192.168.1.117: bytes=32 time=5ms TTL=64

Reply from 192.168.1.117: bytes=32 time=51ms TTL=64

Reply from 192.168.1.117: bytes=32 time=5ms TTL=64

 

Ping statistics for 192.168.1.117:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 5ms, Maximum = 51ms, Average = 16ms

 

SERVER

C:\Users\Dad's Desktop>ping SERVER

 

Pinging SERVER [fe80::3196:5f85:196c:43ef%10] with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

 

Ping statistics for fe80::3196:5f85:196c:43ef%10:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

C:\Users\Dad's Desktop>

Share this post


Link to post
Share on other sites
JerryW

I have to agree with ikon on this one. To not be able to communicate with your server via host name and/or i.p. and yet have backups working, I find this to cancel one another out. The MS WHS 2011 Connector uses the registry entry that specifies your server name for discovery and communication. Your also denoting that there are .NET problems. So, you will need to form communication between your clients and server, and fix your .NET issues long before you will see my HSS (or any other) .NET application of this type.

 

I had trouble with my server switching to IPV6 addresses. You can go here: http://support.microsoft.com/kb/929852 and download the tool to DISABLE IPV6 and run on SERVER. Save the website or download the enable IPV6 tool if you ever wish to reverse this.

 

After running this tool on your server, you may have to reboot. Afterwards, try and ping host name and/or i.p. of server.

 

You may also wish to double-check your servers ICMP settings in the WIndows Firewall.

 

1. Remote Desktop Control into your server (Not dashboard)

2. Click the Start Orb

3. Control Panel

4. Network and Internet

5. Network and Sharing Center

6. Lower left corner click on Windows Firewall

7. Advanced Settings on left menu

8. Click on Outbound Rules

9. Scroll middle screen to 'File and Printer Sharing (Echo Request - ICMPv4-Out)'

You will see three profiles for this entry: PUBLIC, PRIVATE, and DOMAIN

Make sure there is a green check next to PUBLIC and PRIVATE

 

 

(IF NEEDED) Scroll middle screen to 'File and Printer Sharing (Echo Request - ICMPv6-Out)'

You will see three profiles for this entry: PUBLIC, PRIVATE, and DOMAIN

Make sure there is a green check next to PUBLIC and PRIVATE

 

If the PUBLIC and PRIVATE profiles for these entries have grey check marks, then double-click entry and click checkbox to enable.

 

10. Now try pinging the host name of your server and/or I.P.

Edited by JerryW

Share this post


Link to post
Share on other sites
WalterS

I checked the Outbound rules and they are all correctly listed like you said. I tried to ping the SERVER or ip address from this desktop, it still timed out..

do i need to restart the computer for the rules to have a fresh start?

 

Do you think its a setting within the Linksys WRT54GS Router?

Share this post


Link to post
Share on other sites
WalterS

I got it to work! I double checked the "outbound rules on the server firewall" as per jerry and that did it..

thanks for all the help Jerry and ikon..

:):D

Share this post


Link to post
Share on other sites
WalterS

It's working on all Computers on the network. The server's firewall was blocking HSS requests.

 

Thanks guys..

Share this post


Link to post
Share on other sites
JerryW

I just love troubleshooting! I am glad all is well and that we were able to help.

 

Have a great weekend!

Share this post


Link to post
Share on other sites
ikon

As soon as I read where you say you can ping the other computers but not the server, and took into account the backups working, I think Jerry & I had the same bulb light up: it has to be the firewall. The backups work because the server initiates them, so the packets coming back to the server from your client are accepted as responses to the server's requests. When you tried to ping the server, it saw the requests as initiated from outside, so the firewall said, "I don't think so!" :)

 

Really glad to hear its working. Congrats.

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



×
×
  • Create New...