> [...] it is a D7000 [...]
According to the attached picture, it's a D7000v2 with very old
firmware. V1.0.0.41 is not even available under "Previous Versions".
There could be a reason for that. As a start, you might try a firmware
update.
Visit http://netgear.com/support , put in your model number, and look
for Downloads. (For older versions, under Firmware and Software
Downloads, look for "View Previous Versions".) Find the kit(s).
Download the kit(s) you want. Read the "Release Notes" file for
instructions.
> [...] I've attached a picture of the port forwarding rules I set up.
Looks ok to me.
> Port 22 is commonly used for SFTP - so I am just following that normal
> usage, so surely it is OK?
It's fine, if you want to be bombarded by attacks on external port
22. Specifying (and using) a different external port could save you
some future headaches. A Web search for terms like:
ssh port 22 security
should find abundant similar advice. Note that there's no reason to
move your server off port 22; port 22 is fine on your LAN. Specifying a
different external port in the port-forwarding rule will do the job
without adding any inconvenience ("-p xxxx") for local access.
> [...] when I go to it from the web [...]
"go to it from the web" is not a useful description. As usual,
showing actual actions (commands) with their actual results (error
messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations.
I'll assume that you mean that you used some web browser or other,
from someplace in the outside world, with a URL like
"http://<your_public_IP_address>". But I'm guessing.
> [...] I get presented with the Netgear login screen, [...]
That should not happen, at least with reasonable firmware. Such
remote access should be restricted to a (different) URL like
"https://<your_public_IP_address>:<alternate_port>", as configured at
ADVANCED > Advanced Setup > Remote Management.
On the other hand, if you're really doing this (vaguely specified)
test from a system on your LAN (rather than from the outside world),
then the router's NAT loopback feature could cause some unexpected
behavior.
> [...] do you have any idea why I get presented with the Netgear login
> screen rather than being forwarded through to my internal server?
Depends on what you're actually doing, but lame firmware is (always)
a possibility.
Can you access these services from a system on your LAN, using the
server's LAN IP address ("192.168.0.101")? If so, and if NAT loopback
is working, the you should get the same results (again, from a system on
your LAN) if you specify the router's WAN/Internet IP address with the
appropriate external port number, if that differs from the internal port
number.
If that works, and if your public IP address matches the router's
WAN/Internet IP address, then you should get the same results from the
outside world.
