I need help.
I have an HP MediaSmart Server hooked up to my Sky Router (Sagem). I have tried to set up the router to allow remote access. The HP software is saying that it cannot detect if the router accepts UnPnP and is reporting that the router is not configured for remote access. I have looked at the UPnP settings and this is check marked. I have forwarded port TCP 80, 443 and 4125. I have tried everything that I can think of. Sky technical assistance did not have a clue what I was on about. HP did not know what router it was and Sagem gave me anumber to speak to someone in France!!

If anyone can help me set this up so that I can access the server via the internet then I would be most grateful. The server works great at home and all computers connected directly either via ethernet or wireless are working faultless with the server. It is the remote acces side that is not happening.!!
Many thanks

You’ll probably know that Windows Home Server is meant to be able to configure remote access for your router if it supports uPnP, but in fact, this only seems to work with some routers. If you’re having problems with your existing router, make sure you’re running the latest firmware for the router, as this can work miracles.

So, if Windows Home Server auto-configured your router, then please visit the forums and let us know your router’s name and model number. If you have a firmware/hardware revision to hand, then that’s useful too. If you see a router listed that you do not believe auto-configures, it may be that you’re runner a different version of the router’s firmware. Please check the forum to see who submitted the router and contact them via the Personal Messaging system to check which firmware they’re using. Then let me know so I can update the list.

Update: List Updated 25th April 2008

So far we have:

3 Com 3CRWDR100A-72
3Com 3CRWE554G72T
Actiontec MI424-WR
Asus WL-700gE
Belkin N1
Belkin F5D7230-4
D-Link DGL-4100
D-Link DGL-4300
D-Link DGL-4500
D-Link DI-524
D-Link DI-634M
D-Link DIR-625 (Firmware 1.09)

D-Link DIR-635
D-Link DIR-655
Dynalink RTA1025W
Linksys BEFSR41
Linksys BEFSR81
Linksys BEFSX41 v.2
Linksys BEFW11S4
Linksys RT31P2
Linksys WRT54G
Linksys WRT54G
Linksys WRT150N
Linksys WRT300N
Linksys WRT350N
Linksys WRT600N
Linksys WRVS4400N
Microsoft MN-500
Microsoft MN-700
Netcomm NB6PLUS4W
Netgear DG834
Netgear FVS318
Netgear GT834GT
Netgear WGR614 (HW v.6,7)
Netgear WGT624 (V3, Firmware V4.2.10_1.0.1)
Netgear WPN824
Sitecom WL-153
SMC SMCWGBR14-N (Firmware 1.0.0.13)
Thomson SpeedTouch 585i
TRENDnet TEW-633GR
TP Link TP-WR541G
US Robotics USR8200
Xincom XC-DPG502 (FW 2.1)
Zyxel P-334WT
Zyxel P-2602R-D1A
Zyxel P-2602HW-D1A
Zyxel X-550

***from
http://www.wegotserved.co.uk/2008/04/25/routers-that-successfully-auto-configure-with-windows-home-server/

Try this.

If that doesnt help then post the exact model number of your router.

Hi,

Thanks for the assistance regarding the router.

I followed the steps as shown on the link but it did not work. What was shown was basically what I had done but it still refuses to set the router for remote access. I have the Sagem router that is grey in colour and looks like a small digibox. There is no model number on it but the firmware is 1.5 SKY. Do Sky block these ports?

All help is really appreciated!!

Go to Shields Up and do a "custom port probe" with the 3 ports seperated by commas.

Hi I have just been to shields up and this is the report that came up with:

GRC Port Authority Report created on UTC: 2008-06-08 at 19:55:19

Results from scan of ports: 80, 443, 4125

2 Ports Open
1 Ports Closed
0 Ports Stealth
---------------------
3 Ports Tested

NO PORTS were found to be STEALTH.

The port found to be CLOSED was: 4125

Other than what is listed above, all ports are OPEN.

TruStealth: FAILED - NOT all tested ports were STEALTH,
- NO unsolicited packets were received,
- A PING REPLY (ICMP Echo) WAS RECEIVED.


I guess then the possible culprit is that I cannot open port 4125.

Saying that there was not the option on the sky router to open this port. 80 and 443 were available but not 4125. mmmmm

I have spoken to sky who have stated that all the ports are open on the router by default (crap as shields up showed that the ones that I have forwarded are the only ones open!!) The port 4125 does not show on their router page unless you add it as a servive. Sky initially told me that I was not able to use a server for buisness, so I had to explain AGAIN what the HP HOMEMEDIA server was (the clue is in the name!!) and what it was used for. I have been told that I am not allowed to change my router to any other that they have provided even though it is unlikely that I will be able to use it with my server for remote access. There is a firmware upgrade coming but sky dont know when!

Has anybody actually managed to get the HP Mediaserver to carry out remote access whilst suscribing to SKY and using the Sagem router? If not then then a coule of things need to happen:
1. SKY get your finger out and wake up to the new technology that is out there.
2. SKY need to employ real people who actually know what a computer is so that technical assistance is just that. I really should not be explaining and teaching the fundamental theory of how a HP MediaServer does what it does to their staff.
3. If SKY dont get a grip then I will cancel my broadband and go to an ISP that allows me to use my kit as I want!


God I feel better now!

Clem[/b]

Ok,
I emailed SKY to find out why I could not port forward TCP 80, 443 and 4125. After some time (6 calls to technical and three emails) I finally got a reply from SKY which explains why you cant use the remote access feature from SKY routers. It is as follows:

Clem,
Just so you know. You dont need port 80 forwarded if you use port 443. You can use either or. I do not have 80 forwarded to my server and it works just fine. When you try to access your server you will need to type https://yourserver.
Its pretty much one or the other.

Hi Frunple, I have tried that as well but no matter what i try it will not show the webpage.

I get the standard internet explore cannot display the webpage.

I have typed in my address

https://clemster.hphomeserver.com in the address bar (this is not my real one). When I access the server the HP setup software is saying that my router is not configured for remote access. I have tried forwarding the ports but I am stumped or is there a work around?

Clemster

Theres always a work around, the problem is you need someone there that knows what they're doing in order to figure it out. Its very difficult to troubleshoot a problem like this when you have to continually ask the "problem" end for answers and you cant actually see whats going on for yourself.

Tell me about it!! I have had to explain the problem every single time I have spoken to them. The 4125 port is not on the listof ports on the SKY router so that may be a problem too. When I troed Shields up ist showed that ports 80 and 443 were open but 4125 was closed so I am now none the wiser, because if that was the case surely 80 would be shown as closed if SKY block them????

I did see something about a bug with Sagem routers with Sky and having Port 80 issues, I can't find that though.

I didnt really meam with them, I meant on your side. Ya see, you're saying that port 443 is open but 4125 is closed. Well, 4125 is only needed for remote access into OTHER pc's on your lan. It's not needed to remote into the mss. So if you have 443 forwarded correctly, you should be able to access your mss. Since you say you cant, there is something wrong with your setup , not your ISP's.

So let me ask you this.
What is the ip address of your mss?
Did you set it statically?
Can you save an image of the forwarded ports page in your router and post it here?
If you go to shields up with your MSS powered down (or disconnect the ethernet cable) does it still show 443 as open?
Are you trying to access your mss from inside your lan using your outside domain name (ie typing https://yourserver.com from a lan pc)??

Frunple I have cracked it!!!

You were right. I have managed to access it via 443. It comes up with the usual security messasge about the website being insecure (no security certificate and all that) but once you click that you trust the website, after all it is mine so I should trust myself!?! you are in and it works like a peach!!

It has to be said that the red herring is that if the setup program on the server is saying that the router is not set up for remote access then that is not the end of it. It is working fine now in all regards. Thanks for all your help you have been invaluable.

Kindest regards
Clemster