WHS 2011 with Remote desktop

Schizophonic · 26 Feb 2012 at 11:50

Need some help.

I've finally managed to get users and computers to connect to my desktop. Need to get Remote access working properly and access to desktop rather than the dashboard.

When I run the setup wizard I get errors say Port fowarding not cofigure and blah blah.

I've created a static IP address on my server.
Unticked firewall (just to be sure)

I have a Netgear DGN2200 and their portforward options are a little crap but the principle are the same as other Netgear routers.

I've included a screenshot because its easier to explain. As you can see my server is 192.168.0.8. I've opened my ports but its still not letting me through.

I have made sure my UPnP is ticked but cannot see much activity on the log list that its tried or made any attempt

However I dont know if the next thing is a problem but other devices seem to work fine. My equipment is on the top floor of a 2 storey town house and my router is in the ground floor. From my router I have a home plug connect downstaire and into the other homeplug and then splits off into a 8 port router. Would this have any interference?

swinnie · 26 Feb 2012 at 12:18

So, you've got two routers?

On the second router is DHCP, DNS, NAT and the Firewall switched off, so it effectively becomes a switch?

Schizophonic · 26 Feb 2012 at 12:27

Sorry I meant that the device is a Netgear GS608 8 Port Gigabit Desktop Switch. Is not a router and its unmanaged.

Schizophonic · 26 Feb 2012 at 13:59

I've currently got my Server downstaires connected directly to the router. Now I'm doing some testing and I can't connect from my main desktop PC.

I'm on the laptop as well and can log on.

back to my main desktop, when I log onto my router I can see it attached but I can't connect to it or even ping it. I think its down to this homeplug which is causing my problems.

wonko · 27 Feb 2012 at 14:45

There should be no need to disable the firewall or do any port forwarding on your router to do RDP across your LAN (and good security reasons not to). Port forwarding would only be needed if you wanted to access your server from across the internet.

What wizard is it that is telling you about port forwarding errors?

When trying to ping or RDP into your server from your desktop, have you tried using the server's IP address to rule out name resolution problems?

Another thing you could try is to turn off the wireless on your laptop and try to connect via the desktop's network cable - this might help point the finger at or away from the homeplugs.

Hope this helps.