I created an ftp account on one of my IPs using Plesk.
Tested it. Worked OK.
I then used it to upload a forum & install. OK. This was a few days ago.
Yesterday... I tried to connect again but just kept getting "Cannot connect. Cannot login" from my FTP client.
I checked the settings on Plesk and everything seemed fine but it still wouldn't worked.
So I rebooted my server. After which I connected first time.
Today.. I tried to connect again and got the same error message.
Any ideas?
I have only used Plesk to setup the ftp. Haven't touched IIS.
Full Version: FTP Problem
what program are you using to ftp in?
Can you get us a full error description using the command line ftp program?
to open:
start -> run -> type: cmd
at the prompt type: ftp my.ip.address (eg: ftp 69.93.000.00)
then login
to copy/paste the output right-click and select "mark", then select what you want, and then right click again (this will copy the text)
Can you get us a full error description using the command line ftp program?
to open:
start -> run -> type: cmd
at the prompt type: ftp my.ip.address (eg: ftp 69.93.000.00)
then login
to copy/paste the output right-click and select "mark", then select what you want, and then right click again (this will copy the text)
OK.. did this..
It did nothing for about 20 secs and then came back with..
ftp: connect: unknown error number
It didn't even get to a logon stage
HELP!
It did nothing for about 20 secs and then came back with..
ftp: connect: unknown error number
It didn't even get to a logon stage
HELP!
is ftp even running?
type: netstat -a
into a command prompt window (start -> run "cmd")
do you have something like this:
TCP COMPANY01:ftp COMPANY01:0 LISTENING
?
type: netstat -a
into a command prompt window (start -> run "cmd")
do you have something like this:
TCP COMPANY01:ftp COMPANY01:0 LISTENING
?
OK.. tried that now and I got 'LISTENING' as you described.. but I rebooted the server a few hours ago and ftp is working at the mo.
I'll wait till tomorrow when it will invariably have failed again and then test it again.
I still reckon it's something to do with Plesk. I'm beginning to form the opinion that Plesk is rubbish.. and looking at the SWSoft forums.. I'm not the only one.
I'll wait till tomorrow when it will invariably have failed again and then test it again.
I still reckon it's something to do with Plesk. I'm beginning to form the opinion that Plesk is rubbish.. and looking at the SWSoft forums.. I'm not the only one.
heh, bad luck. When it goes down agin (if it does) take a look in the IIS management interface and see if you can start the ftp process back up
OK.. down again. Lasted a few days this time.
Checked the netstat -a thing. It's still listening.
Checked IIS. FTP still running.
Stopped it in IIS. Started it again.
Still can't connect via ftp.
Checked the netstat -a thing. It's still listening.
Checked IIS. FTP still running.
Stopped it in IIS. Started it again.
Still can't connect via ftp.
Launch the Event Viewer on the remote server and check for errors.
OK.
Every hour, Application log getting..
and
and
Yet the netstat said it was listening
However.. more intreging...
The system log.
On the 18th May..
then on the 19th..
then lots of these...
I've restarted the FTP Publishing Service in SERVICES but still no luck
Every hour, Application log getting..
CODE
Event Type: Warning
Event Source: named
Event Category: None
Event ID: 2
Date: 5/22/2004
Time: 1:51:50 PM
User: N/A
Computer: #####
Description:
not listening on any interfaces
Event Source: named
Event Category: None
Event ID: 2
Date: 5/22/2004
Time: 1:51:50 PM
User: N/A
Computer: #####
Description:
not listening on any interfaces
and
CODE
Event Type: Error
Event Source: named
Event Category: None
Event ID: 1
Date: 5/22/2004
Time: 1:51:50 PM
User: N/A
Computer: #######
Description:
creating IPv4 interface TCP/IP Interface 6 failed; interface ignored
Event Source: named
Event Category: None
Event ID: 1
Date: 5/22/2004
Time: 1:51:50 PM
User: N/A
Computer: #######
Description:
creating IPv4 interface TCP/IP Interface 6 failed; interface ignored
and
CODE
Event Type: Error
Event Source: named
Event Category: None
Event ID: 1
Date: 5/22/2004
Time: 1:51:50 PM
User: N/A
Computer: ######
Description:
could not listen on UDP socket: permission denied
Event Source: named
Event Category: None
Event ID: 1
Date: 5/22/2004
Time: 1:51:50 PM
User: N/A
Computer: ######
Description:
could not listen on UDP socket: permission denied
Yet the netstat said it was listening
However.. more intreging...
The system log.
On the 18th May..
CODE
Event Type: Warning
Event Source: MSFTPSVC
Event Category: None
Event ID: 10
Date: 5/18/2004
Time: 11:18:32 AM
User: N/A
Computer: #####
Description:
User ##### at host XXX.XXX.XXX.XX has timed-out after 120 seconds of inactivity.
Event Source: MSFTPSVC
Event Category: None
Event ID: 10
Date: 5/18/2004
Time: 11:18:32 AM
User: N/A
Computer: #####
Description:
User ##### at host XXX.XXX.XXX.XX has timed-out after 120 seconds of inactivity.
then on the 19th..
CODE
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1013
Date: 5/19/2004
Time: 4:59:02 AM
User: N/A
Computer: ####
Description:
A process serving application pool 'PSASystemAppPool' exceeded time limits during shut down. The process id was '5292'.
Event Source: W3SVC
Event Category: None
Event ID: 1013
Date: 5/19/2004
Time: 4:59:02 AM
User: N/A
Computer: ####
Description:
A process serving application pool 'PSASystemAppPool' exceeded time limits during shut down. The process id was '5292'.
then lots of these...
CODE
Event Type: Warning
Event Source: MSFTPSVC
Event Category: None
Event ID: 100
Date: 5/19/2004
Time: 7:02:24 AM
User: N/A
Computer: #####
Description:
The server was unable to logon the Windows NT account 'test' due to the following error: Logon failure: unknown user name or bad password. The data is the error code.
Event Source: MSFTPSVC
Event Category: None
Event ID: 100
Date: 5/19/2004
Time: 7:02:24 AM
User: N/A
Computer: #####
Description:
The server was unable to logon the Windows NT account 'test' due to the following error: Logon failure: unknown user name or bad password. The data is the error code.
I've restarted the FTP Publishing Service in SERVICES but still no luck
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.