Hi Dave
I do not have the router you mention, but on most routers one would need to
setup port forwarding.
When your router connects to the internet it is given a public IP address.
When you enter this ip address into a web browser the browser will request
port 80 from your router, your router will not know what to do. If it is a
NAT router, and you are using NAT (which is very likely) the router will
disgregard the request anyway as it does not correspond to packets sent out
by the router, which is a nice safety feature.
Setup port forwarding on the router to the pc running IIS (ie your web
server).
You will need to enter port 80 and the pc's IP address.
If this PC is obtaining an IP address dynamically (through DHCP from the
router or a server) then you should change this a fixed ip.
If the router has an IP address of 192.168.0.1 set the pc to 192.168.0.2 and
enter 192.168.0.2 in the port forwarding entry.
Things should then work fine. When someone enters your public IP address
into a web browser the router will 'forward' the packets to the web server
and it will respond accordingly.
If you do this I would suggest you setup a firewall on the web server, to
give yourself some protection.
Hope it all goes well.
Darren
"Pile" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Got the above ADSL router all set up now, however I am running W2K and
> used to be able to access IIS externally. Now it is not possible.
> Please can someone tell me what I need to configure on the router's
> many config screens! I upgraded the firmware recently and there are
> lots of new tweaks in the web UI for the router.
> Thanks
> Dave
|