Be Excellent To Each Other

My server is having difficulties settign up port forwading.. (by server I mean me)

I have a Netgear DG834PN..

Unless Netgear changed their web-based config page, try this:

Services > Add custom service
Give name
Specify type (probably TCP)
Start and End port
Apply

Firewall rules > Inbound Services > Add
Select the service created above
Action: Allow always
Send to LAN server - the local IP of the computer you want to receive this traffic
WAN users: Any
Apply

And that should do it. Watch out for Windows firewall or another firewall on the target PC - this may block the traffic unless told not to.

I think windows firewall could be the issue...

Is it trying to use UPnP to accomplish it? If so, check it's supported and enabled in the router. I don't know how else it's going to do it, except possibly with SNMP, but that's Old News.

Have you Googled?

It does use Upnp, I have even updated the firmware on the router.

End set up the ports as EoE said for

Port 80, 443 & 4125 at always allow.

If you want to test it, this site will send data to a specific port and tell you if it is reachable: https://www.grc.com/x/ne.dll?bh0bkyd2

One other thing you might need to do is reboot the router - I don't usually have to on mine, but your might be different. If it's Windows Firewall causing problems, make sure you have enabled World Wide Web Services (HTTP) and Secure WWW Services (HTTPS) are ticked as exceptions.

Also, check the router log after you've used Shields Up! to see if the traffic was blocked by the router.

i will try that later. Never had to use it before. I can still use it as a server if i can't get the port stuff working.

Out of interest, if you're using it for learning, do you need IIS and Remote Web Workplace accessible from outside your network?



Unless you're learning how to get really good at fixing machines with exploited IIS vulnerabilities, of course

I just like everything to work Home server is 2003 in a funky shell isn't it?

I think it's pretty much SBS 2003. I'm just saying, the IIS stuff you can just access from other machines on the network, rather than needing access from the internet, and it'll probably save you a world of pain.

i can access it from my other pc and there is not a need to access it over the net. But.. It will be something to look in to