Each time I run my FTP Server keeps saying that it cannot open the port 21 because it's being used. Is there anyway to know who's opening... or just close the connection??
Printable View
Each time I run my FTP Server keeps saying that it cannot open the port 21 because it's being used. Is there anyway to know who's opening... or just close the connection??
Goto your Command Prompt
type netstat -a
that will show you all your active connections and what ahs them opened.
Hope that helps...
Ok... and what does this mean:
Code:Proto Local Address Remote Address State
TCP one:ftp one:0 LISTENING
it means someone, most likely you since you said you are running ftp, is listening for information via tcp. I take it your comptuer name is "one" and port 0 is being used, which i think is wierd...understand?
If I am wrong , someone please correct me :D
Use -o to show the process ID of the connection's owner. Then you can use Task Manager to end the app.
BTW... aren't to many ports opened??
Code:Proto Local Address Remote Address State
TCP one:ftp one:0 LISTENING
TCP one:ftp one:0 LISTENING
TCP one:smtp one:0 LISTENING
TCP one:http one:0 LISTENING
TCP one:epmap one:0 LISTENING
TCP one:https one:0 LISTENING
TCP one:microsoft-ds one:0 LISTENING
TCP one:999 one:0 LISTENING
TCP one:1025 one:0 LISTENING
TCP one:1028 one:0 LISTENING
TCP one:1031 one:0 LISTENING
TCP one:1933 one:0 LISTENING
TCP one:1934 one:0 LISTENING
TCP one:1935 one:0 LISTENING
TCP one:1936 one:0 LISTENING
TCP one:2498 one:0 LISTENING
TCP one:2499 one:0 LISTENING
TCP one:2556 one:0 LISTENING
TCP one:5000 one:0 LISTENING
TCP one:5678 one:0 LISTENING
TCP one:5679 one:0 LISTENING
TCP one:7438 one:0 LISTENING
TCP one:20004 one:0 LISTENING
TCP one:60652 one:0 LISTENING
TCP one:netbios-ssn one:0 LISTENING
TCP one:ms-sql-s one:0 LISTENING
TCP one:2499 205.188.11.23:5190 ESTABLISHED
TCP one:3307 cumeil7.prima.com.ar:pop3 TIME_WAIT
TCP one:3309 24.232.0.19:pop3 TIME_WAIT
TCP one:3311 mail.fibertel.com.ar:pop3 TIME_WAIT
TCP one:3313 jeeves.sinectis.com.ar:pop3 TIME_WAIT
TCP one:3315 zaphod.sinectis.com.ar:pop3 TIME_WAIT
TCP one:3319 mail.fibertel.com.ar:pop3 TIME_WAIT
TCP one:3321 mail.fibertel.com.ar:pop3 TIME_WAIT
TCP one:3325 mail.fibertel.com.ar:pop3 TIME_WAIT
TCP one:3327 mail.fibertel.com.ar:pop3 TIME_WAIT
TCP one:3361 200.49.139.132:http TIME_WAIT
TCP one:990 one:0 LISTENING
TCP one:990 one:1934 ESTABLISHED
TCP one:1026 one:0 LISTENING
TCP one:1027 one:0 LISTENING
TCP one:1027 one:2498 ESTABLISHED
TCP one:1027 one:3300 TIME_WAIT
TCP one:1027 one:3332 TIME_WAIT
TCP one:1027 one:3340 TIME_WAIT
TCP one:1027 one:3342 TIME_WAIT
TCP one:1027 one:3343 TIME_WAIT
TCP one:1027 one:3356 TIME_WAIT
TCP one:1040 one:0 LISTENING
TCP one:1040 one:3302 TIME_WAIT
TCP one:1040 one:3306 TIME_WAIT
TCP one:1040 one:3308 TIME_WAIT
TCP one:1040 one:3310 TIME_WAIT
TCP one:1040 one:3314 TIME_WAIT
TCP one:1040 one:3316 TIME_WAIT
TCP one:1040 one:3318 TIME_WAIT
TCP one:1040 one:3320 TIME_WAIT
TCP one:1040 one:3322 TIME_WAIT
TCP one:1040 one:3324 TIME_WAIT
TCP one:1040 one:3326 TIME_WAIT
TCP one:1040 one:3328 TIME_WAIT
TCP one:ms-sql-s one:0 LISTENING
TCP one:1933 one:5679 ESTABLISHED
TCP one:1934 one:990 ESTABLISHED
TCP one:1935 one:5678 ESTABLISHED
TCP one:1936 one:5678 ESTABLISHED
TCP one:2498 one:1027 ESTABLISHED
TCP one:2556 one:1027 CLOSE_WAIT
TCP one:3304 one:1040 TIME_WAIT
TCP one:3312 one:1040 TIME_WAIT
TCP one:3350 one:1027 TIME_WAIT
TCP one:3354 one:1027 TIME_WAIT
TCP one:3360 one:1027 TIME_WAIT
TCP one:5678 one:1935 ESTABLISHED
TCP one:5678 one:1936 ESTABLISHED
TCP one:5679 one:1933 ESTABLISHED
TCP one:11854 one:0 LISTENING
TCP one:netbios-ssn one:0 LISTENING
UDP one:epmap *:*
UDP one:microsoft-ds *:*
UDP one:1029 *:*
UDP one:1030 *:*
UDP one:ms-sql-m *:*
UDP one:3456 *:*
UDP one:4737 *:*
UDP one:netbios-ns *:*
UDP one:netbios-dgm *:*
UDP one:isakmp *:*
UDP one:1035 *:*
UDP one:1635 *:*
UDP one:1691 *:*
UDP one:2262 *:*
UDP one:2321 *:*
UDP one:netbios-ns *:*
UDP one:netbios-dgm *:*
UDP one:isakmp *:*
WOW....:eek:
Do you have a firewall???
You really should think about one if oyu dont!!! :cool:
Way to many ports open...I'd definately do a netstat -o to see what programs are waiting for connections.
killerSD: the 0 is there because there's no connection. The port is just listening.
The -o option does not seem to exist here.Quote:
Originally posted by Shawn N
Way to many ports open...I'd definately do a netstat -o to see what programs are waiting for connections.
killerSD: the 0 is there because there's no connection. The port is just listening.
I do have a firewall... but most of the connections remote addresses seem to be my computer :confused:Quote:
Originally posted by killerSD
WOW....:eek:
Do you have a firewall???
You really should think about one if oyu dont!!! :cool:
Aight ... but there is such thing as port 0. Lol read in to it... it sounds liek fun!Quote:
killerSD: the 0 is there because there's no connection. The port is just listening.
How do you close a connection?
does your firewall have a lock?
if so you could "try" to lock all internet access then restart your connection..
I am just guessing here ... i will look in to it more if someone doesnt post. :D
Get ZoneAlarm. It's free and will tell you what programs are trying to do.
He is right... Zonealarm is Awesome! I use it and it is amazing. :)
I will... althought I'm afraid that it start messing things up with Norton's. Anyway... how do you close a connection?
I don't know of any simple way to close another processes connection other than using ZoneAlarm.
Ok... and how would you close this connection:
with ZoneAlarm? Isn't there any way to close it through VB or a DOS command??Code:TCP one:ftp one:0 LISTENING
McBrain that's not even a connection. That's just showing that your computer is listening on that port, waiting for a connection.
Thanks!! I've realized that already. And found that Windows' FTP service should be stopped to get that port free.
you asked this over and over again, "how can i close a port/connection?" the truth is you cant.. you must close the application that has opened the port that is using it on your comp. netstat -n will give you all the remote connections..look at those and any suspicious ones you better check out..:D
You can close another processes connection, it's just not as simple as showing an input box. ZoneAlarm does it.
doesnt zonealarm simply disalow the application to send and establish a connection?
Err - maybe you're right. I haven't used the program for a while now so I forgot. I'm pretty sure that it is possible to close other program's connections, though.
is netstat -o only available on xp? because im on 2k and it just brings up the netstat help when i try it :D
netstat-o in WinXp=netstat in Win2KQuote:
is netstat -o only available on xp? because im on 2k and it just brings up the netstat help when i try it
I don't have the -o option on W2K.
You must be getting this when you type netstat in Win2k:
The State might be: Established, or Waiting or Listening. Anyways, when I type netstat-o in WinXP Pro I get the same thing as shown above so these two commands are same: in Win XP it is: netstat-o and in Win2k its just netstat, thats what I meant. BTW, whats the question?Code:Proto Local Address Remote Address State
TCP one:ftp one:0 LISTENING
TCP one:ftp one:0 LISTENING
....
i meant where does the -o flag come into play? xp/2k? another version of netstat?Quote:
Originally posted by Shawn N
Use -o to show the process ID of the connection's owner. Then you can use Task Manager to end the app.
Well, I'm on XP. I don't know if it's possible to use XP's version of netstat on a different Windows version.