Windows 2000 Server and IIS/FTP woes

This is a discussion about Windows 2000 Server and IIS/FTP woes in the Windows Networking category; I'm running Win2k Server on a cable modem and want to run an FTP server. It all runs fine. EXCEPT, users have to disable passive mode in order to send/receive data, otherwise a Data Socket Error occurs.

Windows Networking 2246 This topic was started by , . Last reply by ,


data/avatar/default/avatar11.webp

132 Posts
Location -
Joined 2000-02-02
I'm running Win2k Server on a cable modem and want to run an FTP server. It all runs fine. EXCEPT, users have to disable passive mode in order to send/receive data, otherwise a "Data Socket Error" occurs.
 
I'm running the default settings except I require authentication.
Is there a setting or anything that I need to set differently?
 
I am using a Linksys Router with the correct ports forwarded.
Let me know if you need any more info to help me.
 
Thanks
Ancker

Participate in our website and join the conversation

You already have an account on our website? To log in, use the link provided below.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This subject has been archived. New comments and votes cannot be submitted.
Sep 5
Created
Sep 5
Last Response
0
Likes
1 minute
Read Time
User User User
Users

Responses to this topic


data/avatar/default/avatar26.webp

362 Posts
Location -
Joined 2000-03-16
Are you using just basic Win2k authentication?
 
I have one setup on my cable modem also. Only difference is, I use Sygate to share my connection. Mine runs fine.

data/avatar/default/avatar19.webp

3857 Posts
Location -
Joined 2000-03-29
They have to "disable" or "enable" passive mode? Generally, you don't want to "enable" passive (PASV) mode on the client because it is a bit slower to authenticate and establish the connection, but it is needed when the client cannot actively negotiate additional ports to transfer data. FTP uses more than just ports 20/21 to function, and that is where the problem lies; the user and/or server may be behind a firewall that is restricting access.