locked
whs home console won't connnect to server RRS feed

  • Question

  • I have a home built WHS server, all was working well when the MOBO died. I replaced it with the exact same model, reinstalled WHS all went well. Then my linksys wrt  router went out. So I replaced with a Belkin N+.
    I haven't been able to use the WHS console since.
    I can use remote desktop to get in without any trouble.
    backups are woring fine( scheduled or not),notifications are working,the web site is working.

    however I had to open some ports in the virtual servers area of my router.
    the ports I opened are , HTTP 80 and 55000, HTTPS 443 and 56000
    I had some more open, but I closed them because the problem did not get any better and I didn't think it was a good idea to have open want doesn't need to be.
    the  ports I closed are 3389, 4125, 8912 , 1138, 2869 and 10243.
    I wonder if something is corrupt in the sys files and another reinstall is in order. I have two desktops and one laptop that I'm using WHS for. I would like to add our web server at some point.
    I don't know if this helps, but the Xbox does not have any trouble connecting to play movies.
    Sorry for the long post I wanted to give as much detail as I could.
    Monday, October 12, 2009 1:53 PM

All replies

  • The Home Networking technical brief contains information about what ports are used by Windows Home Server, both inside your home and for Remote Access.
    I'm not on the WHS team, I just post a lot. :)
    Monday, October 12, 2009 3:30 PM
    Moderator
  • Thanks for link Ken, while my specific router is not in the certifiednetworking devices list, it did pass the Internet Connectivity Eval with flying colors. I turned all the ports I opened to run the test just to see how it would do. While the test ran I was notified that port forwording failed from the WHS server.(funny huh, as it wwas during the UPnp test)
    I have also reviewed the trouble shooting WHS connector guide and verified all the ports are open that should be.
    I suppose I'll open the WHS ports back up and restart the server and router.
    I have reviewed the WHS connector troublshooting guide as well to get the proper ports.
    Maybe it's a Belkin thing, I kinda hope not though, I'm enjoying the gigabit ports and the "n" wifi.
    Monday, October 12, 2009 4:37 PM
  • Does this help? kind of long, sorry.



    Active Connections

    Proto Local Address Foreign Address State

    TCP server:http server:0 LISTENING
    TCP server:epmap server:0 LISTENING
    TCP server:https server:0 LISTENING
    TCP server:microsoft-ds server:0 LISTENING
    TCP server:1025 server:0 LISTENING
    TCP server:1138 server:0 LISTENING
    TCP server:icslap server:0 LISTENING
    TCP server:ms-wbt-server server:0 LISTENING
    TCP server:8912 server:0 LISTENING
    TCP server:10243 server:0 LISTENING
    TCP server:55000 server:0 LISTENING
    TCP server:56000 server:0 LISTENING
    TCP server:1032 server:0 LISTENING
    TCP server:netbios-ssn server:0 LISTENING
    TCP server:1138 OFFICE2:50860 ESTABLISHED
    TCP server:1138 NICOLE:60568 ESTABLISHED
    TCP server:ms-wbt-server OFFICE2:53135 ESTABLISHED
    UDP server:microsoft-ds *:*
    UDP server:isakmp *:*
    UDP server:ipsec-msft *:*
    UDP server:8912 *:*
    UDP server:ntp *:*
    UDP server:ssdp *:*
    UDP server:ntp *:*
    UDP server:netbios-ns *:*
    UDP server:netbios-dgm *:*
    UDP server:ssdp *:*

    Monday, October 12, 2009 4:55 PM
  • I believe I will reinstall. I have made several attempts to correct this issue to no avail.
    Thanks anyway.
    Sunday, October 18, 2009 3:45 AM