Firewall Problem

[shanidham]

I am using Plesk 8.2 with CISCO Firewall.

When i create a domain in my Plesk it is created successfully and hosting is also set. However when i ftp the domain it doesnt works. Also when i change the file through File manager in Plesk then also the domain shows default Plesk Page. what could be problem.

 

[LeaUK]

Have you opened port 21 in Plesk and Cisco FW for your FTP server?

 

[shanidham]

Yes

Yes port 21 is allowed. I think there is some DNS setting to be done in the plesk. But i am not getting it.

 

[elimedesign]

I noticed on my server if I didn't have passive FTP enabled through the firewall I couldn't use FTP, unless I set the FTP program to "active" mode.

 

[Bender]

Hi,

I suggest you to check here for better understanding of passive and active ftp mode:
http://www.slacksite.com/other/ftp.html

In Plesk 8.3 it becomes possible to configure passive ports range in ftp server and firewall(i mean windows firewall on the Plesk host):
ftp://download1.swsoft.com/Plesk/Plesk8.3/Doc/en-US/plesk-8.3-win-administrators-guide/52601.htm

Also if you have additional routers/firewalls make sure that appropriate ports are opened.

 

[LeaUK]

Good point, you must enable passive mode for all your clients using firewalls. As mentioned, you can now add a range of passive ports via PLesk 8.3, although previously I simply added them to Windows Firewall manually - time consuming but effective.

Go into your FTP app and ensure passive is enabled. Then in your FTP app find the section where you define the passive port range - choose at least 10 ports, then match these with the ones you configured in Plesk.

Lea

 

[shanidham]

Its not only the problem of FTP

It is not only the problem of FTP. But The domain is also not resolving via http.

When i add domain in Plesk sometimes it resolves and afterwards it doesnt resolves. In whois also it shows my firewall address for the domain.

 

[LeaUK]

Make sure you have opened port 53 (DNS) in your firewall.

Make sure your DNS template is similar to this:

Record type Value
<IP you host domains on> / 24 PTR <domain>.
<domain>. NS ns1.yourdomain.net. (assuming DNS is running on same IP as hosting)
<domain>. NS ns2.yourdomain.net. (assuming DNS is running on same IP as hosting)
<domain>. A <IP you host domains on> (probably same as the /24 entry)
<domain>. MX (10) mail.<domain>.
ftp.<domain>. CNAME <domain>.
mail.<domain>. A <mail server IP> (probably same as the /24 entry)
mssql.<domain>. A <IP you host mssql on> (probably same as the /24 entry)
webmail.<domain>. A <IP you host webmail on> (probably same as the /24 entry)

Lea

It is not only the problem of FTP. But The domain is also not resolving via http.

When i add domain in Plesk sometimes it resolves and afterwards it doesnt resolves. In whois also it shows my firewall address for the domain.

 

[smurf]

We're running Serv-U and Windows/Plesk Firewall on Windows Server 2003 SP2

We've set the passive port range in both Serv-U and Plesk as xxxx-xxxx (Hidden for security reasons) and enabled the same ports in the Firewall. We still have issues with people trying to connect to the server using FTP-Passive. It freezes at the directory listing command.

When saving port range, Plesk gives us this message;

Warning: due to active Windows Firewall and Windows Application Layer Gateway Service (ALGS) not allowing to use a custom passive FTP ports range, it is recommended to switch ALGS off. If ALGS service is switched on, passive FTP ports range will be set to default 5001-65535, ignoring any custom values. Refer to Microsoft Windows help files for the information on how to switch ALGS off.

Is it required to follow the above if using Serv-U instead of MS FTP service?

 

[shall]

Yes. ALGS is a protocol-layer filter, which means it can affect ANY long-duration IP transaction, like a large FTP upload/download.