"David Mills" <> wrote in message
news:tLydnTLfm_ARZE_eRVn-...
> Ok, here is my setup.
>
> -Linksys cable modem and a Linksys router.
> -I have 2 pc's connected to the modem sharing the cable connection.
> -The pc's internal ip addresses are 192.168.1.100 and 192.168.1.101
> -My Wan/Internet ip address is 69.167.219.111
>
> I have my IIS server running and setup correctly. I have "Allow IIS to
> control password" checked under security accounts inside IIS.
> On my router setup pages, under the "forwarding" tab, I have ports 20 thru
> 21 forwarded to 192.168.1.100
That's OK but if the IP for the machine that has IIS running changes to
another IP then port forwarding will no longer work as it will be pointing
to the wrong machine.
> I checked on Linksys' knowledge base and it says to have the ip address
> set to 192.168.1.3. I tried using that address and it didn't work either.
Well, that's the kind of IP on the router you should be using a static IP on
the router for the machine and not a DHCP IP. The static IP never changes
for the machine and port forwarding rules would not be broken due to the IP
pointing to a machine that doesn't have IIS running.
> I have searched all over Google for FTP setup using port forwarding and
> they all basically say the same thing, but it isn't working.
You may have to set the IIS FTP folder and the browser to use the PASV mode
"passive mode setting".
> The only thing I tried but didn't work at all is setting up a static ip
> address within my router.
> I went into the router and typed in 69.167.219.111 for my static ip
> address and then that killed my internet access.
ISP's have a static IP address that they can give a user requesting to use
the IPS's static IP addresses which also includes two other IPS(s) that must
be used and are DNS IP(s) for the ISP.
> I am assuming you can't just type in whatever "static" ip address you
> want.
You can use any static IP on the router you want and not the static IP at
the ISP. Static IP(s) would be any IP that is not issued by the DHCP server
on the router. 192.168.1.2 through 192.168.1.99 are static IP(s). The DHCP
IP(s) start at 192.168.100 for the DHCP Issue Count most likely 50 so DHCP
IP(s) are from 192.168.1.100 to 192.168.1.150 and IP(s) after that are
static IP(s), since the DHCP server on the router doesn't issue those IP(s)
dynamically.
> Checking the research I have done, you shouldn't have to have a static ip
> address in order to get this to work.
No you don't. However, for reasons above, it's best that you use a static
IP on the router.
>
> If I open up windows explorer and type in ftp://69.167.219.111/ then I get
> this error:
> ------------------------------------------------------
> Windows cannot access this folder. Make sure you typed the file name
> correctly and that you have permission to access the folder.
>
> Details:
> The connection with the server was reset
> ------------------------------------------------------
>
> Does anyone have any ideas what I am doing wrong?
The fact that you're trying to expose a machine that has IIS running to the
public Internet that I am sure that the O/S, IIS, the registry, file system
and user accounts are not secured is the problem, which there are books
explaining how to do this properly and WEB sites that have this information
by using Google.
If you do get the machine exposed to the public Internet, then it's going to
be nothing but *hack* bait as you have not done your homework. IT WEB
administers have a hard time securing a machine running IIS facing the
public Internet let alone some clueless home user.
Duane