none
Need Help with Install. Can not get Remote Access Set up.. RRS feed

  • Question

  • Well I got homeserver to install and run good on an old laptop that I had laying around.  Fit the bill nicely.  I am having a problem getting my remote access set up.  I have a DIR 655 Dlink router and a smc 8014 cable modem/router.  I am using comcast cable. I have the WHS hook into the Dlink Router.    On the roter set up I am getting error messages on verifing your router is accepting web site connections and verifing that your router is accepting remote access.

    I have upnp is enabled and I manully set the ports open in port forwading.  I think I did it correctly.... 

    Do I need to set the same ports open in my cable modem?  I am at a lose where to look.  I have been doing some searching but I think I am just spiing my wheels taking stabs at trying different things... 

    Any input would be great... thanks

    Doug 

    PS I can get to the internet from the server and I can locate the server on my LAN.  I have DHCP server enabled on my dlink router.  I have my domain name set up as well.


    Here are some logs from my dlink if it helps at all...

    [INFO] Fri Feb 13 01:00:42 2004 Allowed configuration authentication by IP address 192.168.0.194
    [INFO] Fri Feb 13 00:42:56 2004 Above message repeated 1 times
    [INFO] Fri Feb 13 00:40:14 2004 UPnP added entry 255.255.255.255 <-> 10.1.10.192:4125 <-> 192.168.0.191:4125 TCP timeout:-1 'WHS_4125'
    [INFO] Fri Feb 13 00:40:14 2004 UPnP added entry 255.255.255.255 <-> 10.1.10.192:443 <-> 192.168.0.191:443 TCP timeout:-1 'WHS_443'
    [INFO] Fri Feb 13 00:40:14 2004 UPnP added entry 255.255.255.255 <-> 10.1.10.192:80 <-> 192.168.0.191:80 TCP timeout:-1 'WHS_80'
    [INFO] Fri Feb 13 00:32:06 2004 Blocked incoming ICMP packet (ICMP type 8) from 10.1.10.1 to 10.1.10.192
    [INFO] Fri Feb 13 00:31:59 2004 Above message repeated 3 times




    Sunday, February 1, 2009 11:13 PM

Answers

  • Hi,
    your description points to a double NAT configuration (the modem produces one private network range, the router another), which is not supported by WHS.
    Please check this thread, maybe the information given here can help you to get further.
    Best greetings from Germany
    Olaf
    Monday, February 2, 2009 7:27 AM
    Moderator

All replies

  • Hi,
    your description points to a double NAT configuration (the modem produces one private network range, the router another), which is not supported by WHS.
    Please check this thread, maybe the information given here can help you to get further.
    Best greetings from Germany
    Olaf
    Monday, February 2, 2009 7:27 AM
    Moderator
  • Thanks for the link.  I figured since my DIR 655 has a firewall that I would just shut it off in the Cable modem.  SO I made all the ports avalable in the cable modem and shut the fire wall off.  Still didnt work=..... HUMMMMMM

    Does anyone have the settings for the DIR 655 that they could post for me.  THe intro page has all of the settings.  Thanks in advance

    Doug 
    Monday, February 2, 2009 7:54 PM
  • Have you try conecting to your server even though you have the error? I have the same problem. when I try to connect it displays the same error, but I am still able to conect to the saver and access the WHS.
    Tuesday, February 3, 2009 3:22 AM
  • In the link referenced before people wrote about succeeding with changing the modem to bridged mode.

    Best greetings from Germany
    Olaf

    Tuesday, February 3, 2009 7:38 AM
    Moderator
  • There is not a bridge setting on the modem I have.  I am not going to trouble shot the modem for I am getting a new one with my comcast upgrades on wed.  I would like the DIr 655 settings how ever.

    Thanks Doug
    Thursday, February 5, 2009 2:08 AM
  • You can download the entire user guide of that router on dlinks website, I have as I have the same router. You may want to reset the router back to factory specs and reboot it. I had to do that when I added mine and first set it up.

    Also, if you have another A/V suite running it may be blocking your port forwarding ability.
    PACS Technical Support Engineer
    Sunday, February 8, 2009 4:14 AM
  • I have a motorolla modem from comcast and a 655 router.  i just had whs do all the stuff auto and it worked.
    athlon 3400, 2gb ram, 9 drives totaling about 3.5 tbs.
    Sunday, February 8, 2009 7:30 AM