I am running SBS 2003 without ISA. I have a linksys router to direct incomin
g
traffics to my server. (Note: I have two NICs on this server: Local NIC and
External NIC).

On my Firewall I have forwarded ports 20 and 21 to my server's External NIC.
I also enabled FTP from SBS firewall.

I also created a ftp users group and added this group to "Domain Controller
Security Policy" under "Allow Log on Locally" and made my FTP user to be par
t
of this group.

Now when I use a FTP client I am getting this error:
426 Connection closed; transfer aborted.

Am I missing something here?

Can someone please guide me as far as how to confgure my ftp users with IIS
6 on SBS 2003 server and an external firewall?

Thanks alot,

Mike

[ Post a follow-up to this message ]

Sounds like passive mode issue again.
if you try command prompt ftp.exe from remote host,
can you login ? and do dir listing ?

For passive mode to work, you need to open certain port range.
read -
Information About the IIS File Transmission Protocol (FTP) Service
http://support.microsoft.com/?id=283679
How To Configure PassivePortRange In IIS
http://support.microsoft.com/?id=555022

--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/



"Mike R." <MikeR@discussions.microsoft.com> wrote in message
news:464DDBA6-D555-4074-9A60-8A88D0A7B2C7@microsoft.com...
> I am running SBS 2003 without ISA. I have a linksys router to direct
incoming
> traffics to my server. (Note: I have two NICs on this server: Local NIC
and
> External NIC).
>
> On my Firewall I have forwarded ports 20 and 21 to my server's External
NIC.
> I also enabled FTP from SBS firewall.
>
> I also created a ftp users group and added this group to "Domain
Controller
> Security Policy" under "Allow Log on Locally" and made my FTP user to be
part
> of this group.
>
> Now when I use a FTP client I am getting this error:
> 426 Connection closed; transfer aborted.
>
> Am I missing something here?
>
> Can someone please guide me as far as how to confgure my ftp users with
IIS
> 6 on SBS 2003 server and an external firewall?
>
> Thanks alot,
>
> Mike
>
>

[ Post a follow-up to this message ]

Bernard,

Thanks for your reply.
Now I can't even connect to my server!!!
Here is the new error message:

C:\ftp domain.com
Connected to domain.com.
Connection closed by remote host.

I have no clue what's going on.
Port 20 and 21 are open.

Thanks,

Mike

"Bernard" wrote:

> Sounds like passive mode issue again.
> if you try command prompt ftp.exe from remote host,
> can you login ? and do dir listing ?
>
> For passive mode to work, you need to open certain port range.
> read -
> Information About the IIS File Transmission Protocol (FTP) Service
> http://support.microsoft.com/?id=283679
> How To Configure PassivePortRange In IIS
> http://support.microsoft.com/?id=555022
>
> --
> Regards,
> Bernard Cheah
> http://www.tryiis.com/
> http://support.microsoft.com/
> http://www.msmvps.com/bernard/
>
>
>
> "Mike R." <MikeR@discussions.microsoft.com> wrote in message
> news:464DDBA6-D555-4074-9A60-8A88D0A7B2C7@microsoft.com... 
> incoming 
> and 
> NIC. 
> Controller 
> part 
> IIS 
>
>
>

[ Post a follow-up to this message ]

what did you changed ?
first - always test internally and locally first.
try ftp at the server, make sure everything is running, then test remote
connection.

You only need inbound 21 and outbound 20 (active mode)
for passive mode, 21 + outbound passive port range.

also try ftp using IP address to skip the host name resolution.

--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/



"Mike R." <MikeR@discussions.microsoft.com> wrote in message
news:2E6CCD96-82C1-418F-9493-6C513B0F4003@microsoft.com...[vbcol=seagreen]
> Bernard,
>
> Thanks for your reply.
> Now I can't even connect to my server!!!
> Here is the new error message:
>
> C:\ftp domain.com
> Connected to domain.com.
> Connection closed by remote host.
>
> I have no clue what's going on.
> Port 20 and 21 are open.
>
> Thanks,
>
> Mike
>
> "Bernard" wrote:
> 
NIC[vbcol=seagreen] 
External[vbcol=seagreen] 
be[vbcol=seagreen] 
with[vbcol=seagreen] 

[ Post a follow-up to this message ]

Internally it is working.

I think I just need active mode.

FTP IP gives me the same issue.

"Bernard" wrote:

> what did you changed ?
> first - always test internally and locally first.
> try ftp at the server, make sure everything is running, then test remote
> connection.
>
> You only need inbound 21 and outbound 20 (active mode)
> for passive mode, 21 + outbound passive port range.
>
> also try ftp using IP address to skip the host name resolution.
>
> --
> Regards,
> Bernard Cheah
> http://www.tryiis.com/
> http://support.microsoft.com/
> http://www.msmvps.com/bernard/
>
>
>
> "Mike R." <MikeR@discussions.microsoft.com> wrote in message
> news:2E6CCD96-82C1-418F-9493-6C513B0F4003@microsoft.com... 
> NIC 
> External 
> be 
> with 
>
>
>

[ Post a follow-up to this message ]

Ok, so from remote machine you try:
ftp.exe yourserverip

where do you experienced 426 error ?

--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/



"Mike R." <MikeR@discussions.microsoft.com> wrote in message
news:BA9E1C5C-18CC-4AE0-B190-1AB037E3A82F@microsoft.com...[vbcol=seagreen]
> Internally it is working.
>
> I think I just need active mode.
>
> FTP IP gives me the same issue.
>
> "Bernard" wrote:
> 
direct[vbcol=seagreen] 
Local[vbcol=seagreen] 
to[vbcol=seagreen] 

[ Post a follow-up to this message ]

Can you post the log ?
Connecting to ...
220 Microsoft FTP Service
....

also IIS FTP log as well.



--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/



"Mike R." <MikeR@discussions.microsoft.com> wrote in message
news:3DBD9368-A888-4437-9D9A-DB303FF446E6@microsoft.com...[vbcol=seagreen]
> from outside (ftp public ip)
>
> "Bernard" wrote:
> 
remote[vbcol=seagreen] 
Service[vbcol=seagreen] 
"Domain[vbcol=seagreen] 
user[vbcol=seagreen] 
users[vbcol=seagreen] 

[ Post a follow-up to this message ]

C:\Documents and Settings\mike>ftp publicip
Connected to publicip.
Connection closed by remote host.

log:
#Software: Microsoft Internet Information Services 6.0
#Version: 1.0
#Date: 2004-10-11 02:00:16
#Fields: time c-ip cs-method cs-uri-stem sc-status sc-win32-status
02:00:16 192.168.16.2 [2]USER administrator 331 0
02:00:20 192.168.16.2 [2]PASS - 230 0
02:02:55 192.168.16.2 [2]closed - 421 121
02:24:55 192.168.16.11 [4]closed - 421 121



"Bernard" wrote:

> Can you post the log ?
> Connecting to ...
> 220 Microsoft FTP Service
> .....
>
> also IIS FTP log as well.
>
>
>
> --
> Regards,
> Bernard Cheah
> http://www.tryiis.com/
> http://support.microsoft.com/
> http://www.msmvps.com/bernard/
>
>
>
> "Mike R." <MikeR@discussions.microsoft.com> wrote in message
> news:3DBD9368-A888-4437-9D9A-DB303FF446E6@microsoft.com... 
> remote 
> Service 
> "Domain 
> user 
> users 
>
>
>

[ Post a follow-up to this message ]

"Mike R." <MikeR@discussions.microsoft.com> wrote in message
news:A84A370A-478D-4C70-B6DB-D361ECFD248F@microsoft.com...
> 02:00:16 192.168.16.2 [2]USER administrator 331 0
> 02:00:20 192.168.16.2 [2]PASS - 230 0
> 02:02:55 192.168.16.2 [2]closed - 421 121

421 is a different error from 426.  421 is used to indicate a closure of the
control connection, whereas 426 is used for closing the data connection.
The win32-status field gives you some further information, which can be
gleaned from "net helpmsg 121" - that tells you:

"The semaphore timeout period has expired."

Ignore, for now, the technical term "semaphore", and concentrate, instead,
on the word "timeout".  Now go back and look at the log, and you'll see that
two and a half minutes, and no commands, came between the logon (USER and
PASS commands) and the time when you were disconnected for no activity.
This seems like everything's working as it should on the server's side.

426, on the other hand, is a very common error now that the world uses
firewalls and NATs - which one are we debugging right now?

Alun.
~~~~

[ Post a follow-up to this message ]

Thank you Alun for your reply,

First when I started configuring my ftp server it gave me error 426 and
after couple days the error changed to 421.

How can I give you more information so we can troubleshoot this problem? Any
logs that you need to look at? Please let me know.

Thanks,

Mike



"Alun Jones [MSFT]" wrote:

> "Mike R." <MikeR@discussions.microsoft.com> wrote in message
> news:A84A370A-478D-4C70-B6DB-D361ECFD248F@microsoft.com... 
>
> 421 is a different error from 426.  421 is used to indicate a closure of t
he
> control connection, whereas 426 is used for closing the data connection.
> The win32-status field gives you some further information, which can be
> gleaned from "net helpmsg 121" - that tells you:
>
> "The semaphore timeout period has expired."
>
> Ignore, for now, the technical term "semaphore", and concentrate, instead,
> on the word "timeout".  Now go back and look at the log, and you'll see th
at
> two and a half minutes, and no commands, came between the logon (USER and
> PASS commands) and the time when you were disconnected for no activity.
> This seems like everything's working as it should on the server's side.
>
> 426, on the other hand, is a very common error now that the world uses
> firewalls and NATs - which one are we debugging right now?
>
> Alun.
> ~~~~
>
>
>

[ Post a follow-up to this message ]