Public ip asking for credentials

[urgenthelpneed]

Hi,

I am using an old Dell laptop on which i have installed Windows server 2008 r2 and recently brought a static ip from my ISP. My ISP had setup the static ip on the modem which is a d-link and my modem is connected to the Linksys router wrtg54 which gives is DHCP enabled and my ip for the router is 192.168.192.1 and right now my server laptop i am using through wifi.

I had installed IIS on it and successfully configured FTP on it and i can access ftp internally but not externally through public ip.

I have given 192.168.192.103 static ip on my server and forwarded port from modem to router and even from firewall inbound setting.

I had also tried DMZ setting from my modem as well router it still dont work.

Completely closed firewall on my server

Checked with the ISP if port are closed or open they confirmed ports are opened.

My main concern is that

"I cant access my ftp outside my network" it ask for login credentials which i havent setup on my modem or on my router.

I am stuck on this from last few days i would really appreciate if someone can help me with this.

 

[razel]

You may need to add your external IP to the FTP binding in IIS. I assume when you say you are getting a login prompt that you mean you are using Windows Explorer to FTP to your external IP? If so then it is resolving. If you are using another protocol like HTTP, then it has reached IIS, but not FTP, the web server. The third option is the scary one... you have reached the login screen for your router which should never be exposed by default on the Internet.

 

[Gryz]

Three layers of NAT. Good luck with that. No wonder something goes wrong.

When troubleshooting, always try to make the easiest case work first. From there, slowly increase complexity. And keep testing every step. Until you get where you want to be.

So in this case, connect your ftp server right behind your isp's modem. Note, it might be a modem, but it might be a router (with a modem built in). Modems themselves shouldn't get ip-address, or else they aren't modems.

Anyway, connect your ftp server behind your modem, and make it work. Once that works, put your own router between the modem and the ftp-server. Test again. When that works, put your PC with IIS in between, and test again. Step by step.

If your ftp-server and/or your PC with IIS are windows-based PC, you might want to install WireShark. It's free. It's useful. It might take an hour (or more) to learn how to configure the filtering, but once you understand the filtering, WireShark can tell you exactly what packets are flying over the network. You can then see what is happening. If one is linux-based, you can try the tcpdump utility. Tcp dump works just like WireShark, but is text-based, not graphical. Tcpdump comes with most linuxes.

Good luck.