No, they are not. I'm tired of you propagating this lie. I'm running a dedicated server at this very moment, with nothing forwarded to the machine but UDP port 27015.Spunky said:The correct ports to forward are 27000 - 27030 UDP/TCP both enabled.
That's because you need ports 27000-27030 TCP/UDP enabled!Drew said:Here, I'll give you all the info: All I have is ESF 1.2.3 installed, EVM Core only(just the sprites and stuff), and a model pack. I'm using ESF 1.2.3 dedicated server. UDP Port: 27015. No one joins anymore. I used to get alot of people in my dedicated server when I first got it, but I get none at all anymore..not even in 3 hours. I put in sv_lan 0 too, btw. Also I get this error in my console at server startup:
WARNING: UDP_OpenSocket: port: 27015 bind: WSAEADDRINUSE
NET Ports: server 27015, client 27005
Could not get TCP/IP address, TCP/IP disabled
No. You won't.Spunky said:@DD - I'll stick with my little "lie" until the day I die.
And you're inferring that from... what? Even knowing nothing about Winsock, you could atleast search for the error on Google and see that you have no idea what you're talking about.Spunky said:That's because you need ports 27000-27030 TCP/UDP enabled!
That's our problem. The client and the server both use port 27015, and two processes can't use the same port simultaneously.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.