port forwarding to virtual server

[petrefax]

having trouble setting up port forwarding to a virtual server

i have a 2008 R2 server with windows home server 2011 running as a virtual server on it

both servers have fixed IP addresses

both servers can ping router

router can ping both server IPs & both servers show up in router "devices connected" table by name, so they can see router & router can see them

tried the homeserver auto config option first, that reported uPNP off on router (despite it being on, but...)

so manually forwarded required ports (80, 443 and 4125) to homeserver IP

when trying to connect to homeserver web page, getting nothing, and homeserver config keeps throwing the same error that router isn't configured.

ok, this is probably because i have the server virtualised with master server & virtual server sharing a NIC, but it must be possible....i just don't know how!

any advice gratefully recieved

[Splash]

Can you access the server on the local network using the ip that you forwarded to on the ports you specified? If not then your issue isn't down to port forwarding. How is the virtual network configured?

[petrefax]

now, this is probably where i come unstuck since (as you may have guessed) i'm making this up as i go along

virtual network is configured basically however Hyper-V configured it, i added a VM & added local area connection

[Splash]

Does the VM have an ip address in the same subnet as your PC? (probably 192.168.0.something) If so can you contact the server by opening a browser and putting http://whs_ip_address into the address bar (also https://whs_ip_address)?

[petrefax]

Yup, vm has ip in same subnet, not tried browsing o it yet but will do that in the morning since its currently switched off, my wife has reminded me that its (a) friday (b) valentine's day and buying her a new coffee maker will only earn me a certain amount of leeway for messing about with computers, so i'll get back onto it tomorrow!! Thanks for the info tho dude, much appreciated

[Splash]

No worries. If browsing *doesn't* work we'll likely need to know a bit more about your network setup in order to help further though

[petrefax]

browsing to homeserver IP via HTTP and HTTPS both successfully connected to server *but* there was a certificate error on both instances

attempting external connection gets me "the remote device or resource won't accept the connection"

[wasabi]

suspect the clue might be this

' homeserver config keeps throwing the same error that router isn't configured.'

Is gateway IP configured in the guest VM? You could always try route add commands to add a route to both the host machine and to the router and route print to confirm.

[Splash]

I'd expect a cert error as it'll be using a default or self signed cert. What router are you using?

[petrefax]

Sky Sagem f@ST2504n, firmware version 7.16a4N_UNI (latest released by Sky AFAIK)

browsing internally, can accept certificate error & get to server remote web login page & enter details, will briefly display expected page then throw a 404 error(...if that helps at all)

and thank you, appreciate the time you're taking dude

[Splash]

Doing a quick bit of reading it looks like a lot of people have issues with port forwarding on that device. Are the port forwarding entries showing on the web interface of the router (seems some people enter the port details, then apply and they disappear...)

Are you able to post a screen grab of the port forwarding setup that you have (feel free to mask out any bits that you're uncomfortable with posting)?

EDIT - there's a pretty comprehensive guide at http://portforward.com/english/route...ome_Server.htm - have you checked that out?

[petrefax]

think I've found the issue - checked, double checked etc my port forwarding rules & could see no issue so checked the ports were showing as open via shields up!

that reported port 4125 closed, despite me definitely opening it.

changed the firewall rule to open a series of ports (used 4123 - 4128)

now it works. looks like port forwarding on port 4125 is blocked on these routers by default.

next i'll try editing the working firewall rule back to the single port. not ideal having ports open for no reason

[Splash]

Glad you've made some progress