Cesar FTP WinXP SP2 behind firewall router and DSL modem

H

hammmy

New Member
Hello all,

I'm trying to set up a FTP server using Cesar FTP 0.99g on WinXP SP2. The PC runs into a D-Link firewall router (firewall active) which in turn runs through a Westell firewall DSL modem (firewall disabled).

I have FTP (20, 21) port forwarding active on the DSL modem to .47, the router. The router has FTP (20, 21) routed to .112, my PC. This doesn't work, and I don't know why. Any ideas?

Oh, I tried testing from my PC and using a friend's PC, but no joy--FTP server never saw anything. I used IE 6 with passive FTP enabled (and tested with active FTP as well) as the FTP client.

Thanks for looking,

-dave
 
I have FTP (20, 21) port forwarding active on the DSL modem to .47, the router.
Click to expand...
little confused by this step, if the modem is just connected to the router there shouldn't be any need to open up these ports, you modem shouldn't be assigning a internal ip addy to your router???
 
Well, I'm no expert on why this is. However, the Westell DSL modem says there is a device connected to it, "dlk001", and that its address is 192.168.1.47. I assume that's the router.

The DSL modem still acts as the DHCP server I think, so maybe that means something to you?

Thanks,

-dave
 
The DSL modem still acts as the DHCP server I think, so maybe that means something to you?
Click to expand...
ah, ok

is there any option to place 192.168.1.47 into a DMZ??
also what ip address is your router giving out to your machine

Sorry bro, i have to go to bed now. I will try to pick this up tomorrow, unless Trizoy can take a look.
 
I haven't seen a DMZ option on the modem, but I'll read through the manual to see if I can do so.

The router assigns 192.168.0.112 to my PC.

Thanks,

-dave
 
Update: I set up something called Static NAT on the DSL modem, which is described as having any unsolicited traffic sent to a designated device. I have it sent to the router now. I read about an option for Static IP Passthrough, which basically would have let the router be visible on internet instead of the modem, but that option doesn't work under my ISP's current configuration specs, apparently.

Anyhoo, after shunting unsolicited traffic straight through to the router, I then used the router's DMZ option to open my PC to all traffic. I tried to connect to my instance of Cesar FTP then using a login and password I'd created in Cesar, but still no go. I then masked my PC again.

-dave

Update #2: I removed the router and plugged directly into the DSL modem. I tested using the modem's port forwarding service, as well as with no firewall engaged and this PC receiving all traffic. Still no luck, and I'm suspecting now that CesarFTP doesn't work with WinXP.

-dave

Update #3: Placed the router back into the network. Successfully logged into CesarFTP over the router using the local IP address (192.168.0.112) from .119, another PC on the router. I think this points to the DSL modem as being the problem for trying to connect over the internet. I have no ideas yet on what new to try as far as the modem.

Coincidentally, the discovery of being able to use CesarFTP over the intranet provides a workaround for another issue I've had, which is that the Win2K machine (.119) couldn't access the WinXP machine's (.112) shared drives, although .112 could access .119's shares. So, I've got that going for me.
 
Last edited:
I think I just came up with a new idea. I'll plug .112 into the DSL modem (4 ports), and see if .119 can still connect to CesarFTP over that setup. This may help further isolate the issue.

Is it common/possible for DSL providers to block certain traffic from reaching their users (like FTP)?

-dave
 
You must log in or register to reply here.
Back
Top