問題 Web Access to Server

  • Montag, 12. März 2007 13:46
     
     

    I am trying to access WHS from the web via http://xx.xx.xx.xx/server/home/ but unable to bring it up(ping is ok).  It works fine internally.  I have forwarded ports 80,443 & 4125 through the router(tcp&udp as the directions didn't specify) to the server.  Has anyone else already created this wheel?

    Thanks,

    Pete

Alle Antworten

  • Montag, 12. März 2007 14:34
     
     
    Have you tried just http://xxx.xxx.xxx.xxx   ?

    No /server/ is needed.


    Dan
  • Montag, 12. März 2007 15:24
     
     
    yes i did try that!  thanks
  • Montag, 12. März 2007 16:45
     
     

    Are you sure that you fowarded the ports to the correct internal IP? Also, do you have DHCP setup on your router? If so, I would double check and make sure the IP address of your WHS box did not change. Also, to prevent this I would manualy setup your IP on WHS so this does not happen! Hope this helps.

  • Montag, 12. März 2007 16:55
     
     
    Yes, ports forward to correct ip and have the server assigned a permanent ip address via dhcp.  Thanks for your reply.
  • Montag, 12. März 2007 17:02
     
     

    Alright, seems to be your ISP then blocking port 80, you said you fowarded 443.. did you try

    https://  and not http://

  • Montag, 12. März 2007 18:12
     
     

    All ports can be set at TCP (udp is not needed)  Also I know on some of the newer linksys wireless routers that the remote administration was turned on and it used port 443 by default for admin of the router from the outside.  If you are using a linksys make sure you use change the default port from 443 which is waht whs needs or just be safe and turn it off. 

    Also you should be able to use http:// [ip addresss] to get to the web page then to the login screen (make sure your not using your internal address of like 192.168.x.x) You can get your external address by chekcing the status page of your router or some modems by default to http://192.168.0.1 and you can find the address on that page.

     

    Tom

     

  • Montag, 12. März 2007 19:21
     
     
    Thanks for your reply, Steve.  Yes, I have tried https
  • Montag, 12. März 2007 19:27
     
     

    Thanks for the info on the port forwarding configuration Tom, I will go back and change them to TCP.  I've tried connecting using the external ip address, but no go.  I can ping, but not get through on port 80 or 443.  I am tempted to hook WHS back up to monitor/keyboard etc., and change the port from 80 to 88 or something similar.  It is a shame that the WHS Administrator doesn't give you access to those things.  There seem to be a myriad of things that will break the WHS functionality, so trying to gather up any other ideas before striking out on my own!

     

    pete

  • Dienstag, 13. März 2007 00:56
     
     
    You don't need to put the keyboard/monitor/mouse back on your WHS...use remote desktop, connect to server, and log in with administrator/password.  You'll have the server desktop available.  IIS is up and running.  Heed the warning, however - I've poked around and it looks like a full W2K3 server behind the WHS curtain, and the manual specifically states that you can easily break your WHS if you poke in the wrong place.
  • Dienstag, 13. März 2007 01:02
     
     
    Make sure remote desktop is allowed on the client side.

      In vista there's an option you can get that won't let you connect with "external data" or something along those lines (phrase escapes me right now).  Let us know if it works!
  • Dienstag, 13. März 2007 12:21
     
     
    I enabled remote desktop assistance on the client, but still no go.  I queried the ISP and they tell me port 80 and 443 are not blocked.  I am still looking for other ideas!
  • Dienstag, 13. März 2007 12:36
     
     

    Are you positive on your router you have the "enable" box checked after port 80 and that it is forwarding to the correct internal IP (like 192.168.1.x)

    From the inside put in your outside address and make sure you can get to your server that way. (not the 192.168.x.x address)

     

    Tom

  • Dienstag, 13. März 2007 12:48
     
     

    Yes, I have verified the router config and am using the external ip address, currently 71.28.7.33 if you would like to give it a shot.

  • Dienstag, 13. März 2007 13:17
     
     

    I can get to it fine.  Get right to the main page and to your login prompt.

     

    Tom

  • Dienstag, 13. März 2007 13:28
     
     

    Hi Pete, I can also connect directly to your server. I used the https (port 443) and also got to the login page. That is better than I'm getting. Can someone see if they can get the the page where you enter the username and password on my server? http://smithwww.homeip.net/ or https://smithwww.homeip.net/ ?

     Oops, I found a typo in my port forwarding .... looks like mine is working OK now.

    Thanks for your help.

  • Dienstag, 13. März 2007 15:49
     
     

    Well now, that is encouraging.  I wonder why I am not able to get there using the external address?  Thanks Tom, I can now not worry with it anymore until I have a chance to try it from outside my network.

    pete

  • Dienstag, 13. März 2007 15:53
     
     

    Yes Steve, I was able to get to your login page. 

    pete

  • Dienstag, 13. März 2007 16:16
     
     

    What router are you using?  I have a linksys I am using right now...BUT if I throw my Cisco 871w up on my line it will not work.  On some routers (Cisco) there is more of a configuration you need to do to allow your own system back in from the outside using the external IP address.  

     

     

    Tom

     

  • Dienstag, 13. März 2007 17:27
     
     

    Tom, I have a Uniden ENR1504 router.  I guess I could try a firmware update?

    pete

  • Dienstag, 13. März 2007 18:11
     
     

    OK, I have been following this thread from the beginning and have done all that has been suggested so far.  I am able to log in to the server from my work computer and I am able to upload and download files to my work computer.  Now my only problem is I cannot connect to my home computer which the server page says is available.  I made sure port 3389 is available at this end on both the server and my computer (from a different thread).  I am a definate beginner at this, most likely the type of person who would be purchasing it in the future.  So, please, do not get too heavy on the techno language.  Most of the time I can figure out what you are saying.

    **UPDATE:  WILL START A NEW THREAD**

  • Dienstag, 13. März 2007 18:18
     
     
    So couple of questions:

    1) Can you connect from home?
    2) Do you get an error message? 

    Couple of notes:  You can only connect through WHS with Internet Explorer.

    If your client PC has vista installed, select "Allow connection from computers running any version of Remote Desktop (less secure)" in Remote Desktop options.
  • Dienstag, 13. März 2007 18:18
     
     

    CWORRELLSTER, you should really open another thread for this.  Your problem is a bit different than mine.

    pete

  • Dienstag, 13. März 2007 18:29
     
     

    I can connect internally on my network.  I can not connect using my external address, but people outside my network can.  The error message is "Internet Explorer cannot display the webpage"

    pete

  • Dienstag, 13. März 2007 18:36
     
     
    I had problems with my router not allowing loop backs, thus the request for the page would go through but it would not allow the page to be returned... I reflashed my router with 3rd party firmware and disabled remote access to router.

    On the second page of this thread I posted my problem and how I fixed it.

    Re: Web access, how?


  • Mittwoch, 14. März 2007 01:59
     
     

    Hi Pete

      I have been having the same issue if I try to remote desktop directly to the server from the outside internet. Though I have found tha if you go to your server like you were thinking http://xxx.xxx.xxx.xxx/server/home with internet explorer (it does matter what browser you have) you can remote access the computer clicking on the computer tab then the server.

      As pointed out you do have to have port 80 pointed/redirected to the server so that the web interface will come up. You also need port 443, port 3389, and port 4125 pointed/redirected to the server. This way the authentication via the web server can be done and you get desktop access either in a window or full screen. This also is true for the other computers on your network that are part of the home server.

      I suspect microsoft didn't turn on all these ports (though some of it is in the documentation) for security reasons. Make sure you have strong passwords and make the user account "Administrator" un-able to login remotely. If you don't do this the administrator account alone being able to access your system will get your server hacked in minutes.

      I still can't directly go to the server via remote desktop but the web address is just as easy and I don't have to run another program.

      Hope this helps.

     

    Tony  8-)

  • Mittwoch, 14. März 2007 02:29
     
     
    If you can't connect to your machine externally but other people can, it sounds more like there is a firewall where you are connecting from.  If you are trying to connect from work there is a REALLY good chance your IT department has locked down a lot of ports.