Port Fowarding for Windows Server 2003 1

[feneck]

I am new to Windows Server 2003. I am trying to setup a FTP server on it. However I am not having any luck!!!

I have followed all the things and successfully setup the FTP service on it and it is running...

I have gone to no-ip.com and got myself a name, that points to my INTERNET IP address. It is running on the Windows Server 2003 server computer.

On my modem I have forwarded ports 20 and 21 to the Router.

On the router i have forwarded ports 20 and 21 to the internal IP of the server computer, which is a static IP address.

I then use SmartFPT on my other computer which is on the same router and modem and connect to my no-ip name with my username, password and on port 21.

It doesn't even see my welcome message!

If i use the INTERNAL IP address as a name to connect to, it successfully works.

What is going on? Please help me? There isn't enough tutorials for this on the internet!

 

[TheLad]

Is there any Windows firewall blocking the connection?

--------------------------------------
"Insert funny comment in here!"
--------------------------------------

 

[Roadki11]

Sounds like you are trying to come in from the outside facing side of your router from inside your network, this wont work. You need to be outside your network to accomplish what you are trying to do.



RoadKi11

"This apparent fear reaction is typical, rather than try to solve technical problems technically, policy solutions are often chosen." - Fred Cohen

 

[feneck]

no there isn't a firewall blocking it...


Is there a way to set this up so i can connect from inside as well?

 

[Hondy]

try it in Active mode rather than passive, passive mode requires a port above 1024 to create a data connection which your firewall will probably be blocking.

When you try to connect using SmartFTP watch the port number it tries to use, this port is dynamic.

try connecting directly to the IP in case your no-ip isn't working as expected.

As roadki11 says, try it from a PC outside your set up

cheers

 

[Roadki11]

generally from inside your network you wouldnt try connecting to your internal ftp server with blah.no-ip.com, you would just use the server name or ip of the internal server.



RoadKi11

"This apparent fear reaction is typical, rather than try to solve technical problems technically, policy solutions are often chosen." - Fred Cohen

 

[feneck]

I see. It makes sense, but i thought Microsoft may have had a bit more brains and made this possible so i could easily test this out -.- *sigh* just makes my job harder.

oh well, thank you all

 

[Neoh4x0r]

feneck , like many have said you cannot use your no-ip.org address to connect to your ftp server from inside the network.

However, will use this address as an example, blah.no-ip.com (from Roadki11's post).

The problem is that the router only forwards the port from outside traffic and blah.no-ip.com would point to the internet side of the router -- you are trying to connect from an internal IP which is denied forwaring based on the rules the router uses internally.

Try this instead.

1) In Server 2003 setup DNS, and create a zone for blah.no-ip.com and setup forwarding on the DNS server for anything outside of blah.no-ip.com. In the zone point blah.no-ip.com to the IP of the FTP Server.

2) Either use static or DHCP addressing for network clients and set the DNS to point to the DNS server.

Now when an internal network client requests blah.no-ip.com from inside the network it resolve to the ip of the FTP Server (bypassing the router, altogether). When an internet client request blah.no-ip.com it resolve to your internet IP (it uses the internet DNS servers and not you private network DNS server).

William.