How to kill a CLOSE_WAIT connection where the PID is not found? - sockets

I made a Flask app which links to a while true loop, and I killed the terminal with the trash icon in VSCode. Now I try to visit 3039 port, but it keeps on loading (I'm on Windows 11).
So, I tried netstat - ano | findstr ":3039" and I got CLOSE_WAIT connections with 2032 PID:
TCP 127.0.0.1:3039 0.0.0.0:0 LISTENING 2032
TCP 127.0.0.1:3039 127.0.0.1:54506 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:54507 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:59333 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:59334 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:59767 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:59768 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:59782 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:60694 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:60695 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:60788 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:60809 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:60905 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:60912 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:60995 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:61138 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:61226 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:61410 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:61411 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:61640 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:61641 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:61643 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:61647 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:61660 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:61754 CLOSE_WAIT 2032
TCP 127.0.0.1:3039 127.0.0.1:61786 CLOSE_WAIT 2032
Now to kill, I used taskkill /PID 2032 /F but it says:
ERROR: The process "2032" not found.
Also, I tried stop-process 2032 and the response is:
stop-process : Cannot find a process with the process identifier 2032.

Related

How can I show the netstat command in powershell without the 0 in the Local address?

I hope I could explain, sorry for my english
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1160
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:5040 0.0.0.0:0 LISTENING 8864
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:7680 0.0.0.0:0 LISTENING 14052
TCP 0.0.0.0:49664 0.0.0.0:0 LISTENING 964
TCP 0.0.0.0:49665 0.0.0.0:0 LISTENING 872
TCP 0.0.0.0:49666 0.0.0.0:0 LISTENING 1696
TCP 0.0.0.0:49667 0.0.0.0:0 LISTENING 1448
TCP 0.0.0.0:49668 0.0.0.0:0 LISTENING 3380
TCP 0.0.0.0:49710 0.0.0.0:0 LISTENING 944
but what i want
Local Address
135
445
5040
5357
7680
49664
49665
49666
49667
49668
49710
Also, how can I show this on the screen with what code?

Get-NetTCPConnection is the powershell-equivalent of netstat, and it helpfully separates out the port numbers you're looking for. For example, here's what it looks like normally:
Get-NetTCPConnection -LocalAddress 0.0.0.0 -State Listen
LocalAddress LocalPort RemoteAddress RemotePort State AppliedSetting OwningProcess
------------ --------- ------------- ---------- ----- -------------- -------------
0.0.0.0 58369 0.0.0.0 0 Listen 3892
0.0.0.0 49677 0.0.0.0 0 Listen 792
0.0.0.0 49672 0.0.0.0 0 Listen 3900
And then to display just the port numbers, you can add Select-Object:
Get-NetTCPConnection -State Listen |
Select-Object -ExpandProperty LocalPort
58369
49677
49672
edit: To filter by listening address, you can use the -LocalAddress parameter, or use Where-Object:
# Using LocalAddress
Get-NetTCPConnection -LocalAddress 0.0.0.0,127.0.*,192.168.* -State Listen
LocalAddress LocalPort RemoteAddress RemotePort State AppliedSetting OwningProcess
------------ --------- ------------- ---------- ----- -------------- -------------
127.0.0.1 62522 0.0.0.0 0 Listen 3432
0.0.0.0 58369 0.0.0.0 0 Listen 3892
127.0.0.1 50595 0.0.0.0 0 Listen 16596

If the string output is acceptable, then one of the easiest ways to achieve your desired result is to simply remove the unwanted string with regex. However it will mess up the formatting.
(netstat -ano) -replace '0\.0\.0\.0:'
Proto Local Address Foreign Address State PID
TCP 135 0 LISTENING 868
TCP 445 0 LISTENING 4
TCP 5040 0 LISTENING 7288
TCP 5357 0 LISTENING 4
TCP 5985 0 LISTENING 4
TCP 6783 0 LISTENING 5128
TCP 47001 0 LISTENING 4
TCP 49664 0 LISTENING 976
TCP 127.0.0.1:6463 0 LISTENING 14660
TCP 127.0.0.1:6800 0 LISTENING 7468
TCP 127.0.0.1:8094 0 LISTENING 4348
This is a huge drawback from Powershell's object based output. You could try to correct the alignment manually if you so desire..
(netstat -ano) -replace '0\.0\.0\.0:(\d+)','$1 '
Proto Local Address Foreign Address State PID
TCP 135 0 LISTENING 868
TCP 445 0 LISTENING 4
TCP 5040 0 LISTENING 7288
TCP 5357 0 LISTENING 4
TCP 5985 0 LISTENING 4
TCP 6783 0 LISTENING 5128
TCP 47001 0 LISTENING 4
TCP 127.0.0.1:8094 0 LISTENING 4348
TCP 127.0.0.1:8763 0 LISTENING 5128
TCP 127.0.0.1:9527 0 LISTENING 5128
TCP 127.0.0.1:37014 0 LISTENING 4576
Again, these examples really only benefit the user viewing it. If you want to use the data later on, you'd have to parse it. At this point you really should look at the powershell alternatives such as Cpt.Whale's answer shows.

If not using Get-NetTCPConnection
Here's an example of how to correctly parse netstats output, similar to Get-NetTCPConnection
Objects are Created Automatically from a Regex's Capture Group Names
$RegexNetstat = #'
(?x)
# parse output from: "netstat -a -n -o
# you do not need to skip or filter lines like: "| Select-Object -Skip 4"
# because this correctly captures records with empty States
^\s+
(?<Protocol>\S+)
\s+
(?<LocalAddress>\S+)
\s+
(?<ForeignAddress>\S+)
\s+
(?<State>\S{0,})?
\s+
(?<Pid>\S+)$
'#
if (! $NetstatStdout) {
$NetstatStdout = & netstat -a -n -o
}
# If you're on Pwsh7 you can simplify it using null-*-operators
# $NetstatStdout ??= & netstat -a -n -o
function Format-NetStat {
param(
# stdin
[Parameter(Mandatory, ValueFromPipeline)]
[AllowEmptyString()]
[AllowNull()]
[Alias('Stdin')]
[string]$Text
)
process {
if ($Text -match $RegexNetstat) {
$Matches.Remove(0)
$hash = $Matches
$hash['Process'] = Get-Process -Id $hash.Pid
$hash['ProcessName'] = $hash['Process'].ProcessName
$hash['LocalPort'] = $hash['LocalAddress'] -split ':' | select -last 1
[pscustomobject]$Matches
}
}
}
Piping Results
They are true objects, so you can pipe, filter, group, etc. as normal. (I cached Stdout for this demo, so you can compare output of the same results)
usage:
$Stats = $NetstatStdout | Format-NetStat
$stats | Format-Table
Your Original Column Layout
PS> $stats | Ft -AutoSize Protocol, LocalPort, ForeignAddress, State, PID
Protocol LocalPort ForeignAddress State Pid
-------- --------- -------------- ----- ---
TCP 135 0.0.0.0:0 LISTENING 1484
TCP 445 0.0.0.0:0 LISTENING 4
TCP 808 0.0.0.0:0 LISTENING 5608
TCP 5040 0.0.0.0:0 LISTENING 9300
TCP 5357 0.0.0.0:0 LISTENING 4
TCP 5432 0.0.0.0:0 LISTENING 7480
TCP 11629 0.0.0.0:0 LISTENING 14400
TCP 27036 0.0.0.0:0 LISTENING 9196
TCP 49664 0.0.0.0:0 LISTENING 1116
TCP 49665 0.0.0.0:0 LISTENING 880
TCP 49666 0.0.0.0:0 LISTENING 1012
TCP 49667 0.0.0.0:0 LISTENING 1272
TCP 49668 0.0.0.0:0 LISTENING 3440
TCP 49669 0.0.0.0:0 LISTENING 4892
TCP 49678 0.0.0.0:0 LISTENING 1096
TCP 57621 0.0.0.0:0 LISTENING 14400
TCP 1053 127.0.0.1:1054 ESTABLISHED 22328
TCP 1054 127.0.0.1:1053 ESTABLISHED 22328
TCP 5354 0.0.0.0:0 LISTENING 5556
TCP 5354 127.0.0.1:49671 ESTABLISHED 5556
TCP 5354 127.0.0.1:49672 ESTABLISHED 5556
TCP 6463 0.0.0.0:0 LISTENING 16780
TCP 7659 127.0.0.1:7660 ESTABLISHED 18428
TCP 7660 127.0.0.1:7659 ESTABLISHED 18428
TCP 7661 127.0.0.1:7662 ESTABLISHED 4792
TCP 7662 127.0.0.1:7661 ESTABLISHED 4792
TCP 7665 127.0.0.1:7666 ESTABLISHED 1340
TCP 7666 127.0.0.1:7665 ESTABLISHED 1340
TCP 7667 127.0.0.1:7668 ESTABLISHED 11212
TCP 7668 127.0.0.1:7667 ESTABLISHED 11212
Originally from: Parsing Native Apps/Invoke-Netstat

Get specific value from `netstat` command in windows

when i run command netstat -ano I have:
PS Y:\PowerShell> netstat -ano
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 376
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:2222 0.0.0.0:0 LISTENING 2364
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 1748
TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:6081 0.0.0.0:0 LISTENING 2556
TCP 0.0.0.0:8001 0.0.0.0:0 LISTENING 3772
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING 4
But what I really wanna get is:
Active Connections
PID
4
376
4
2364
1748
4
2556
3772
4
I can't use: netstat -ano| select PID because it's not powershell command.

PowerShell version of netstat is Get-NetTCPConnection and it will return with objects.
Get-NetTCPConnection -State Listen

You may use the command below to list only PIDs:
Get-NetTCPConnection -State Listen | Select-Object -ExpandProperty OwningProcess

What does the Recv-Q values in a Listen socket mean?

My program runs in trouble with a netstat output like bellow. It cannot receive a packet. What does the Recv-Q value in the first line mean? I see the man page, and do some googling, but no result found.
[root#(none) /data]# netstat -ntap | grep 8000
tcp 129 0 0.0.0.0:8000 0.0.0.0:* LISTEN 1526/XXXXX-
tcp 0 0 9.11.6.36:8000 9.11.6.37:48306 SYN_RECV -
tcp 0 0 9.11.6.36:8000 9.11.6.34:44936 SYN_RECV -
tcp 365 0 9.11.6.36:8000 9.11.6.37:58446 CLOSE_WAIT -
tcp 364 0 9.11.6.36:8000 9.11.6.37:55018 CLOSE_WAIT -
tcp 364 0 9.11.6.36:8000 9.11.6.37:42830 CLOSE_WAIT -
tcp 364 0 9.11.6.36:8000 9.11.6.37:56344 CLOSE_WAIT -
tcp 0 364 9.11.6.34:38947 9.11.6.36:8000 FIN_WAIT1 -
tcp 364 0 9.11.6.36:8000 9.11.6.37:52406 CLOSE_WAIT -
tcp 365 0 9.11.6.36:8000 9.11.6.37:53603 CLOSE_WAIT -
tcp 364 0 9.11.6.36:8000 9.11.6.37:47522 CLOSE_WAIT -
tcp 364 0 9.11.6.36:8000 9.11.6.34:48191 CLOSE_WAIT -
tcp 364 0 9.11.6.36:8000 9.11.6.37:51813 CLOSE_WAIT -
tcp 364 0 9.11.6.36:8000 9.11.6.34:57789 CLOSE_WAIT -
tcp 364 0 9.11.6.36:8000 9.11.6.37:34252 CLOSE_WAIT -
tcp 364 0 9.11.6.36:8000 9.11.6.34:38930 CLOSE_WAIT -
tcp 365 0 9.11.6.36:8000 9.11.6.37:44121 CLOSE_WAIT -
tcp 365 0 9.11.6.36:8000 9.11.6.37:60465 CLOSE_WAIT -
tcp 365 0 9.11.6.36:8000 9.11.6.37:37461 CLOSE_WAIT -
tcp 0 362 9.11.6.34:35954 9.11.6.36:8000 FIN_WAIT1 -
tcp 364 0 9.11.6.36:8000 9.11.6.37:55241 CLOSE_WAIT -
P.S.
See also at https://groups.google.com/forum/#!topic/comp.os.linux.networking/PoP0YOOIj70

Recv-Q is the Receive Queue. It is the number of bytes that are currently in a receive buffer. Upon reading the socket, the bytes are removed from the buffer and put into application memory. If the Recv-Q number gets too high, packets will be dropped because there is no place to put them.
More info here netstat

JBoss can not startup because of port in use

All, I am not familiar with the JBoss, recently I was working with it because of job, now I am stuck with a problem when I start up the JBoss. After searching the answer in the google , I didn't found anything helpful, Hope you can help me to review it . thanks.
The main exception of JBoss start up said.
13:30:07,653 INFO [ServerInfo] Java version: 1.7.0_05,Oracle Corporation
13:30:07,653 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 23.1-b03,Oracle Corporation
13:30:07,654 INFO [ServerInfo] OS-System: Windows 7 6.1,x86
13:30:10,515 INFO [Server] Core system initialized
13:30:19,756 INFO [EncryptedSystemPropertiesService] Loaded system properties from: file:/D:/AA7.2.0/av.7.2.0/av.biz/conf/av/ServerConfig.properties
13:30:19,778 INFO [EncryptedSystemPropertiesService] Loaded system properties from: file:/D:/AA7.2.0/av.7.2.0/av.biz/conf/av/system.properties
13:30:21,692 INFO [WebService] Using RMI server codebase: http://joe-wang.achievo.com:3083/
13:30:21,693 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
13:30:22,666 WARN [ServiceController] Problem starting service jboss:service=WebService
java.lang.Exception: Port 3083 already in use.
at org.jboss.web.WebServer.start(WebServer.java:233)
at org.jboss.web.WebService.startService(WebService.java:322)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
Firstyly I thought there is some process already use the port 3083. So I use the dos command to show all the port status .
netstat -a
The below is all the port list .
Proto Local Address Foreign Address State
TCP 0.0.0.0:21 joe-wang:0 LISTENING
TCP 0.0.0.0:80 joe-wang:0 LISTENING
TCP 0.0.0.0:82 joe-wang:0 LISTENING
TCP 0.0.0.0:135 joe-wang:0 LISTENING
TCP 0.0.0.0:443 joe-wang:0 LISTENING
TCP 0.0.0.0:445 joe-wang:0 LISTENING
TCP 0.0.0.0:902 joe-wang:0 LISTENING
TCP 0.0.0.0:912 joe-wang:0 LISTENING
TCP 0.0.0.0:1025 joe-wang:0 LISTENING
TCP 0.0.0.0:1026 joe-wang:0 LISTENING
TCP 0.0.0.0:1027 joe-wang:0 LISTENING
TCP 0.0.0.0:1045 joe-wang:0 LISTENING
TCP 0.0.0.0:1054 joe-wang:0 LISTENING
TCP 0.0.0.0:1316 joe-wang:0 LISTENING
TCP 0.0.0.0:1322 joe-wang:0 LISTENING
TCP 0.0.0.0:2074 joe-wang:0 LISTENING
TCP 0.0.0.0:2137 joe-wang:0 LISTENING
TCP 0.0.0.0:2138 joe-wang:0 LISTENING
TCP 0.0.0.0:2140 joe-wang:0 LISTENING
TCP 0.0.0.0:2382 joe-wang:0 LISTENING
TCP 0.0.0.0:3389 joe-wang:0 LISTENING
TCP 0.0.0.0:8787 joe-wang:0 LISTENING
TCP 0.0.0.0:8890 joe-wang:0 LISTENING
TCP 0.0.0.0:8898 joe-wang:0 LISTENING
TCP 0.0.0.0:8988 joe-wang:0 LISTENING
TCP 0.0.0.0:9089 joe-wang:0 LISTENING
TCP 0.0.0.0:54321 joe-wang:0 LISTENING
TCP 0.0.0.0:56789 joe-wang:0 LISTENING
TCP 10.50.70.133:139 joe-wang:0 LISTENING
TCP 10.50.70.133:445 ACA-SERVER:45627 ESTABLISHED
TCP 10.50.70.133:1411 cs109p1:5050 ESTABLISHED
TCP 10.50.70.133:1450 sip105p2:5050 ESTABLISHED
TCP 10.50.70.133:1461 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2265 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2274 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2302 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2327 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2333 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2343 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2345 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2349 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2397 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2454 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2455 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2456 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2457 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2458 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2459 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2460 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2461 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2462 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2463 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2465 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2466 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2467 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2468 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2469 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2470 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2471 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2472 tmg01:8080 ESTABLISHED
TCP 10.50.70.133:2495 sitesz:epmap TIME_WAIT
TCP 10.50.70.133:2496 sitesz:1025 ESTABLISHED
TCP 10.50.70.133:2498 tmg01:8080 TIME_WAIT
TCP 10.50.70.133:2499 tmg01:8080 TIME_WAIT
TCP 10.50.70.133:2500 tmg01:8080 TIME_WAIT
TCP 10.50.70.133:2501 tmg01:8080 TIME_WAIT
TCP 10.50.70.133:2502 tmg01:8080 TIME_WAIT
TCP 10.50.70.133:2503 tmg01:8080 TIME_WAIT
TCP 10.50.70.133:2504 tmg01:8080 TIME_WAIT
TCP 10.50.70.133:2505 tmg01:8080 TIME_WAIT
TCP 10.50.70.133:2506 tmg01:8080 TIME_WAIT
TCP 127.0.0.1:1355 joe-wang:1356 ESTABLISHED
TCP 127.0.0.1:1356 joe-wang:1355 ESTABLISHED
TCP 127.0.0.1:1405 joe-wang:1406 ESTABLISHED
TCP 127.0.0.1:1406 joe-wang:1405 ESTABLISHED
TCP 127.0.0.1:1448 joe-wang:1449 ESTABLISHED
TCP 127.0.0.1:1449 joe-wang:1448 ESTABLISHED
TCP 127.0.0.1:1777 joe-wang:0 LISTENING
TCP 127.0.0.1:1777 joe-wang:31000 ESTABLISHED
TCP 127.0.0.1:2075 joe-wang:0 LISTENING
TCP 127.0.0.1:8307 joe-wang:0 LISTENING
TCP 127.0.0.1:12001 joe-wang:0 LISTENING
TCP 127.0.0.1:31000 joe-wang:1777 ESTABLISHED
TCP 192.168.98.1:139 joe-wang:0 LISTENING
TCP 192.168.198.1:139 joe-wang:0 LISTENING
TCP [::]:21 joe-wang:0 LISTENING
TCP [::]:80 joe-wang:0 LISTENING
TCP [::]:82 joe-wang:0 LISTENING
TCP [::]:135 joe-wang:0 LISTENING
TCP [::]:443 joe-wang:0 LISTENING
TCP [::]:445 joe-wang:0 LISTENING
TCP [::]:1025 joe-wang:0 LISTENING
TCP [::]:1026 joe-wang:0 LISTENING
TCP [::]:1027 joe-wang:0 LISTENING
TCP [::]:1045 joe-wang:0 LISTENING
TCP [::]:1316 joe-wang:0 LISTENING
TCP [::]:1322 joe-wang:0 LISTENING
TCP [::]:2074 joe-wang:0 LISTENING
TCP [::]:2137 joe-wang:0 LISTENING
TCP [::]:2138 joe-wang:0 LISTENING
TCP [::]:2140 joe-wang:0 LISTENING
TCP [::]:2382 joe-wang:0 LISTENING
TCP [::]:3389 joe-wang:0 LISTENING
TCP [::]:8890 joe-wang:0 LISTENING
TCP [::]:8898 joe-wang:0 LISTENING
TCP [::]:8988 joe-wang:0 LISTENING
TCP [::]:9089 joe-wang:0 LISTENING
TCP [::]:54321 joe-wang:0 LISTENING
TCP [::]:56789 joe-wang:0 LISTENING
TCP [::1]:2075 joe-wang:0 LISTENING
TCP [::1]:8307 joe-wang:0 LISTENING
TCP [::1]:12001 joe-wang:0 LISTENING
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1434 *:*
UDP 0.0.0.0:3600 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5355 *:*
UDP 0.0.0.0:54847 *:*
UDP 0.0.0.0:56477 *:*
UDP 0.0.0.0:57586 *:*
UDP 0.0.0.0:64553 *:*
UDP 10.50.70.133:137 *:*
UDP 10.50.70.133:138 *:*
UDP 10.50.70.133:1900 *:*
UDP 10.50.70.133:55282 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:49890 *:*
UDP 127.0.0.1:50195 *:*
UDP 127.0.0.1:50469 *:*
UDP 127.0.0.1:52636 *:*
UDP 127.0.0.1:54848 *:*
UDP 127.0.0.1:55285 *:*
UDP 127.0.0.1:56474 *:*
UDP 127.0.0.1:62117 *:*
UDP 192.168.98.1:137 *:*
UDP 192.168.98.1:138 *:*
UDP 192.168.98.1:1900 *:*
UDP 192.168.98.1:55283 *:*
UDP 192.168.198.1:137 *:*
UDP 192.168.198.1:138 *:*
UDP 192.168.198.1:1900 *:*
UDP 192.168.198.1:55284 *:*
UDP [::]:123 *:*
UDP [::]:500 *:*
UDP [::]:1434 *:*
UDP [::]:4500 *:*
UDP [::]:5355 *:*
UDP [::1]:1900 *:*
UDP [::1]:55281 *:*
UDP [fe80::35f5:46d0:818f:3594%16]:1900 *:*
UDP [fe80::35f5:46d0:818f:3594%16]:55280 *:*
UDP [fe80::b01e:59e5:ee84:87f9%11]:1900 *:*
UDP [fe80::b01e:59e5:ee84:87f9%11]:55278 *:*
UDP [fe80::b4e4:39b:b59a:9463%14]:1900 *:*
UDP [fe80::b4e4:39b:b59a:9463%14]:55279 *:*
But I found the 3083 is not in the port list above . Could anyone tell me why? Did I missed something? Thanks for you kindly help.

Without knowing what environment you are running, hard to say what it is. Here is explanation for Windows:
Port Number: 3083 (Windows 7/Windows Vista/ Windows XP/Windows Server family)
TL1 Telnet--
Protocol Used : tcp/udp
Service Type : tl1-telnet
Known Port 3083 exploits: Yes
Known Port 3083 Security Risks: Yes

You have to Change port Number.
Run the eclipse click on server and change
1.

socket exception in Jboss

I'm getting a socket exception as follows:
2010-12-30 11:49:16,921 WARN [org.jboss.system.ServiceController] Problem starting service jboss:service=HAJNDI
java.rmi.server.ExportException: Listen failed on port: 1101; nested exception is:
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
Any thoughts on why I might be getting this exception are appreciated. I can post the output of a "netstat -a" call if needed.
Thanks!
EDIT: using JBoss 4.2.3
netstat -a:
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 FCBDT11:0 LISTENING
TCP 0.0.0.0:445 FCBDT11:0 LISTENING
TCP 0.0.0.0:1025 FCBDT11:0 LISTENING
TCP 0.0.0.0:1026 FCBDT11:0 LISTENING
TCP 0.0.0.0:1027 FCBDT11:0 LISTENING
TCP 0.0.0.0:1046 FCBDT11:0 LISTENING
TCP 0.0.0.0:1050 FCBDT11:0 LISTENING
TCP 0.0.0.0:1051 FCBDT11:0 LISTENING
TCP 0.0.0.0:1433 FCBDT11:0 LISTENING
TCP 0.0.0.0:2382 FCBDT11:0 LISTENING
TCP 0.0.0.0:3389 FCBDT11:0 LISTENING
TCP 0.0.0.0:5357 FCBDT11:0 LISTENING
TCP 0.0.0.0:34740 FCBDT11:0 LISTENING
TCP 0.0.0.0:56339 FCBDT11:0 LISTENING
TCP 10.10.1.129:139 FCBDT11:0 LISTENING
TCP 10.10.1.129:1109 lga15s16-in-f83:https ESTABLISHED
TCP 10.10.1.129:1164 fcexchange01:1098 ESTABLISHED
TCP 10.10.1.129:1166 fcexchange01:1098 ESTABLISHED
TCP 10.10.1.129:1170 fcexchange01:1098 ESTABLISHED
TCP 10.10.1.129:21642 channel5-02-01-snc4:http ESTABLISHED
TCP 10.10.1.129:21703 channel5-02-01-snc4:http ESTABLISHED
TCP 10.10.1.129:23628 fcdomsvr01:1025 ESTABLISHED
TCP 10.10.1.129:24585 208.51.35.200:http ESTABLISHED
TCP 10.10.1.129:24609 63-233-110-210:http ESTABLISHED
TCP 10.10.1.129:24737 www-10-02-snc5:http ESTABLISHED
TCP 10.10.1.129:25022 74.125.226.155:http CLOSE_WAIT
TCP 10.10.1.129:25033 lga15s16-in-f100:http CLOSE_WAIT
TCP 10.10.1.129:25036 a96-17-160-9:http ESTABLISHED
TCP 10.10.1.129:25253 a96-6-46-48:http ESTABLISHED
TCP 10.10.1.129:25255 a96-6-46-48:http ESTABLISHED
TCP 10.10.1.129:25256 a96-6-46-48:http ESTABLISHED
TCP 10.10.1.129:25257 a96-6-46-48:http ESTABLISHED
TCP 10.10.1.129:25258 a96-6-46-48:http ESTABLISHED
TCP 10.10.1.129:25259 a96-6-46-48:http ESTABLISHED
TCP 10.10.1.129:25260 a96-6-46-48:http ESTABLISHED
TCP 10.10.1.129:25261 208.51.35.184:http ESTABLISHED
TCP 10.10.1.129:25292 a96-6-46-25:http ESTABLISHED
TCP 10.10.1.129:25296 a96-6-46-25:http ESTABLISHED
TCP 10.10.1.129:25413 fctdomsvr02:1025 ESTABLISHED
TCP 10.10.1.129:25443 lga15s16-in-f100:http ESTABLISHED
TCP 10.10.1.129:25523 lb1:http ESTABLISHED
TCP 127.0.0.1:1074 app:40000 ESTABLISHED
TCP 127.0.0.1:1101 app:27015 ESTABLISHED
TCP 127.0.0.1:5354 FCBDT11:0 LISTENING
TCP 127.0.0.1:27015 FCBDT11:0 LISTENING
TCP 127.0.0.1:27015 app:1101 ESTABLISHED
TCP 127.0.0.1:40000 FCBDT11:0 LISTENING
TCP 127.0.0.1:40000 app:1074 ESTABLISHED
TCP 127.0.0.1:56342 FCBDT11:0 LISTENING
TCP [::]:135 FCBDT11:0 LISTENING
TCP [::]:445 FCBDT11:0 LISTENING
TCP [::]:1025 FCBDT11:0 LISTENING
TCP [::]:1026 FCBDT11:0 LISTENING
TCP [::]:1027 FCBDT11:0 LISTENING
TCP [::]:1050 FCBDT11:0 LISTENING
TCP [::]:1051 FCBDT11:0 LISTENING
TCP [::]:1433 FCBDT11:0 LISTENING
TCP [::]:2382 FCBDT11:0 LISTENING
TCP [::]:3389 FCBDT11:0 LISTENING
TCP [::]:5357 FCBDT11:0 LISTENING
TCP [::]:34740 FCBDT11:0 LISTENING
TCP [::]:56339 FCBDT11:0 LISTENING
TCP [::1]:56342 FCBDT11:0 LISTENING
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1434 *:*
UDP 0.0.0.0:2799 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5355 *:*
UDP 0.0.0.0:53087 *:*
UDP 0.0.0.0:58816 *:*
UDP 0.0.0.0:60517 *:*
UDP 10.10.1.129:137 *:*
UDP 10.10.1.129:138 *:*
UDP 10.10.1.129:1900 *:*
UDP 10.10.1.129:5353 *:*
UDP 10.10.1.129:54713 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:53088 *:*
UDP 127.0.0.1:54714 *:*
UDP 127.0.0.1:60514 *:*
UDP 127.0.0.1:61263 *:*
UDP 127.0.0.1:62543 *:*
UDP [::]:123 *:*
UDP [::]:500 *:*
UDP [::]:1434 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:4500 *:*
UDP [::]:5355 *:*
UDP [::]:58817 *:*
UDP [::]:60518 *:*
UDP [::1]:1900 *:*
UDP [::1]:5353 *:*
UDP [::1]:54712 *:*
UDP [fe80::701d:2146:c800:f6ff%11]:546 *:*
UDP [fe80::701d:2146:c800:f6ff%11]:1900 *:*
UDP [fe80::701d:2146:c800:f6ff%11]:54711 *:*

It's failing to bind a socket to port 1100 because that port is already in use by another process.
Try TCPView, that should help you diagnose which process is listening on which port.