locked
firewal and connector problem in whs RRS feed

  • Question

  •  

    i deleted all port in my whs firewal and wonder what should i open ?

     

    i have open :

    file and printer sharing

    http ( 80 )

    http ( 55000 )

    http ( 56000)

    https (443 )

    remote desktop

    UPnP framework

     

    but im missing a lot of them i would like both name and port number and if its TCP ore UDP

     

    i also have another problem, the connector software on all my computers detect the whs and i enter the corect password

    but it cant connect. i have tryed disabling the firewall but no luck.

    i have also tryed reinstaling connector software.

     

    all file shareing and website works fine 

     

     

     

    Sunday, December 30, 2007 6:24 PM

All replies

  •  Tideman wrote:

     

    i deleted all port in my whs firewal and wonder what should i open ?

     

    i have open :

    file and printer sharing

    http ( 80 )

    http ( 55000 )

    http ( 56000)

    https (443 )

    remote desktop

    UPnP framework

     

    but im missing a lot of them i would like both name and port number and if its TCP ore UDP

     

    i also have another problem, the connector software on all my computers detect the whs and i enter the corect password

    but it cant connect. i have tryed disabling the firewall but no luck.

    i have also tryed reinstaling connector software.

     

    all file shareing and website works fine 

     

     

     


    I would simply reset the firewall to the default state. I've had no issues  with it that way.

    Is your server set up with a static IP?? If not, I'd try that first and see if that cures the connection problem.

    Cruise
    Sunday, December 30, 2007 6:34 PM
  •  

     

    thats how it got messed up, i pushed the reset button to get it to defoult.

    its safe to say it dident work .

     

    my whs has a static ip and whs connector worked fine a few days ago, i realy dont know why it dont annymore.

    i ewen tryed reinstaling the whs but that dident work.

    i stil cant get the connector to connect.

    i get unable to connect to your home server.

     

    here is the error message i get.

     

     

    ---------------------------
    Windows Home Server Console
    ---------------------------
    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.
    ---------------------------
    OK  
    ---------------------------

    exept my whs is running and connector is finding it and i enter my password but it wont connect.

    Sunday, December 30, 2007 6:41 PM
  • Ports that are open  after fresh install:

     

    File and Printer Sharing:

    UPD 137, 138

    TCP 139, 445

    HTTP:

    TCP 80, 55000

    HTTPS:

    TCP 56000

    Remote Desktop:

    TCP 3389

    UpNP Framework:

    UDP 1900

    TCP 2869

    Windows Home Server Transport Service:

    TCP 1138

    Windows Media Connect:

    UDP 10280, 10281,10282,10283, 10284

    TCP 10243

     

    Programs allowed:

    C:\Program Files\Windows Home Server\whsbackup.exe

     

    SCOPE is local subnet only for all rules above.

     

    To reconnect you may need to run C:\Program Files\Windows Home Server\discovery.exe

     

     

    Sunday, December 30, 2007 7:28 PM
    Moderator
  • thank you, now my firewal is ok again, but i stil got connector problem.

     

    ive uninstalled the connector and deleted all entry in registery (regedit) and rebooted the computer

    reinstaled and get to the point where i enter whs password but not longer.

     

    the password is corect i use it at remote desktop to my whs and i enter it over ewery time im trying.

    i also tryed disable all firewals both om computer and on my whs.

     

    i think it dont get an answer from the whs but why.

    this error is on all my 3 computers, 2 x win XP and 1 vista.

    all worked fine youst a few days ago but it seems that whs got messed up somehow cos sudenly the iis service vass gone and not working ( thats why i reinstalled whs)

    now all is fine except that connector problem.

     

     

     

    Sunday, December 30, 2007 8:03 PM
  • Tideman,

    I don't have a solution for you, but I seem to be having a similar problem.  I have access via remote desktop, but my connector doesn't work anymore:

    http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2592923&SiteID=50

     

    Please let me know if you get things to work!

    BruceHall

    Sunday, December 30, 2007 8:20 PM
  • Have a look at this one for troubleshooting: http://blogs.msdn.com/eldar/archive/2007/04/28/windows-home-server-client-join-troubleshoooting-hints.aspx

     

    Also check IP address on your WHS ( on WHS do Start, run, type cmd, hit enter, in cmd window type ipconfig /all)

     

     

    Sunday, December 30, 2007 8:25 PM
    Moderator
  • only thing i can think of is that before my problems i got a update after that, things started to happend.

    i usualy do not "disturb" my whs by loging in to it as it is not nessesery .

    but when connector, ftp and whs site started to fail i logged in and discoverd that iis wass gone i suspekted virus but thats not the case, i removed all my hdd exept the c: and formated the whole thing and reinstalled whs.

    i runn all updates and all exept the  connector software is fine.

    i still havent added more then 1 hdd but i wass shure to format it first to be on the safe side.

    this error is starting to realy get on me now as i have been at it fore almost 48 houers whithout sleep.

     

    well i hope someone figures it out and i wil post here if i find out of it.

    thank you for help so far Smile

     

    Sunday, December 30, 2007 8:38 PM
  • You may try uninstalling windows updates kb928365 and / or KB941914, reboot whs and then run discovery.exe again from client.

     

    If you think it's the updates that caused your problem, and you don't know which one is the culprit you may try reinstalling WHS without network cable attached. During final install choose to disable automatic updates. After connecting network cable try and connect again. If it fails again the error is probably caused by another component in your network (router, client / client windows updates, ??).

     

    If you can succesfully connect RDP to your WHS, startup IE, go to windowsupdate site and install updates one by one (or in small batches of 5 or so).  After each (series) of updates test connection to server.

     

    Remember to enable automatic updates when your finished

    Sunday, December 30, 2007 11:32 PM
    Moderator
  • I am also having password issues.  I will watch this post to see what happens here.

     

    Sunday, December 30, 2007 11:37 PM
  • After a week of frustration, I got tired of messing around.  I made sure all data was saved elsewhere, then rebuilt the server.  On my HP system this is called 'factory reset'.  A less-thorough rebuild, called 'server restore', didn't work. 

     

    My connector is finally working  I even changed the server to a static IP (http://www.myhomeserver.com/?page_id=20), rebooted everything, and it still works (for the moment).  Good luck!

    Monday, December 31, 2007 1:24 AM
  • @ Tidemman, can you please try https://server:56000/enroll/id.xml from browser window on your client? This should display <ID>2</ID> in your browser window. If you get a certificate error please try and your server is HP mediasmart and you changed the servername during first client install (or later) you may try renaming your server to HPserver.

     

    If you don't have HP machine checkout name on the certficate and compare it with server name. If they don't match try changing the servername to the name on the certificate

     

    After changing the name you'll have to reboot your server

    Monday, December 31, 2007 1:31 AM
    Moderator
  • well ive tryed to unninstall all updates and rebooted after every unninstal to test whith no luck

    then i enebled update and reinnstaled them whith no luck

    then i changed name on my server from homeserver to server as it wass mensioned but whith no luck

     

    sence im not dependent on my computer backups i wil leave it fore a little while. after all ewerything else works

    and there is new year now so i wil take a break maybe something popp upp im my head...

     

    if not i will transfeer all my data and kompletly rebuild my whs ( reinstall and not repair it)

    i belive this is the downside whith whs, if client dont work youre in fore a lot of trouble.

     

    annyway happy new year to you all and have a nice day and be carefull whith the fireworks

     

     

    oh yea, my whs is a home build one whith AMD X2 4600 2GB ram and a realy bad nvida screencard.

    all suporting win2003 server whith Windows Home Server OEM lisence ( i love it so mutch i bougth it the day

    i saw it in shop) . some time as betatester made me love this thing, but as in real life we get a little resistance some times hehe.  

     

     

    a little update: 31 des 07

    i was reading in a norwegian computer magazine abaut the same problem i got

    and the solution they ended up whith was a rebuild of server. i am shure there is other solutions

    but not as i can figure out now. i have started moving all my files and wil work on that a bit to day.

    im not shure if i mannage to do it all to day bit the operation has started.

    Monday, December 31, 2007 2:11 AM
  • well now my whs is totaly reinnstaled and up running. all updates are innstaled. but some of the updates i got a error on.

    it is not vital fore my whs and it is running werry well. actualy i got it to work bether now whith a clean innstall.

    the innstal before wass a reinsatall from the RC1.

     

    so my problem is gone and server running fine.

    to the others that got the same problem:

    i found that backup service wasent running, i dont know how to start it again ( i dident look werry hard )

    but i got a warning abaut the bacup service when i deleted all bacups to free space as i needed it fore my files.

    and i would loose them annyway with a clean innstall.

    another thing i couldent remove anny of my hd's  by presing remove in the connc\ector

    so to move files i had to give ewery hdd a drive letter to make them visible and move all files manualy.

    this is werry time consuming.

     

    hope this info can help and i realy hope i newer need to make a clean install ewer again.

     

     

     

    Wednesday, January 2, 2008 7:02 PM