Do this:Drew said:I start my dedicated server, and then I start my ESF and join my own server on the same comp. Then I open my console and find that error.
From that file, you will be able to determine which program is listening on port 27015 (and preventing HLDS from listening on that port). The port is the number after the IP address and colon.Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1024
-- unknown component(s) --
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:4400 0.0.0.0:0 LISTENING 1616
TCP 188.8.131.52:139 0.0.0.0:0 LISTENING 4
TCP 192.168.0.200:139 0.0.0.0:0 LISTENING 4
TCP 127.0.0.1:2978 127.0.0.1:2979 ESTABLISHED 2696
TCP 127.0.0.1:2979 127.0.0.1:2978 ESTABLISHED 2696
TCP 192.168.0.200:2746 184.108.40.206:5190 ESTABLISHED 408
Yeah, how about no.Spunky said:Forget what Kurt' said...
What I posted was the solution to that problem (i.e. finding which process was already listening on the port that HLDS was attempting to use), not whatever you were just posting about. Read more carefully please, because you're just adding even more to the confusion.WARNING: UDP_OpenSocket: port: 27015 bind: WSAEADDRINUSE
NET Ports: server 27015, client 27005
Could not get TCP/IP address, TCP/IP disabled
Uh, yes?Drew said:Basically your telling me that RCON is the only thing that I, and other admins can use?