Now I got me a brand new spanking dedicated server that has terminal access for me to gain entry to it. I load HLDS_v1120 and NSP (Current Versions). Get the below problem so then I send email to the providers asking if they block any ports or have hidden firewalls which they say "No". And I have not had time to install my own yet, I went straight to installing NSP.

Servers load fine CS and NS, logout of remote access. And then do below.

Ok. I have done this several times to see and double check, I load the a server I close the remote access go into the server through Steam get in server run around for 5 seconds get out, and then load HLSW and wait for it to see the server once it sees the server I go try to login the server again and I cant, it times out. Seems to me that only one connection is allowed at a time on this IP, there has to be something in the works here. And I know its not me, cause I had two other guys do exactly what I just did.

Thanks for any help here, been working on this for 8 hours going through forums and sending support tickets. And cant seem to figure it out.

Ok, slow down man. I don't know what the hell your problem is as your post is a little less than coherent.

1) You have steam installed and updated?
2) NSP is properly installed?
3) The server loads but then crashes? Or just timesout when someone tries to connect?

RDC should have NO impact on the server. Best case would be to leave your RDC connection active, try and connect, and see if there is an error in the server console.

1) HLDS_v1120.exe installed and updated using HLDSUpdatetool.exe
2) NSP is properly installed keeping file structure.
3) No errors in HLDS seen when attempting to connect to server and clients timeout.

This is wierd to me its either it lets one client connect and then leave, soon as something else makes contant with it like HLSW the other way of connection is not allowed like for a client connecting.

Thanks.

Sorry to waste time, turns out it was my ISP (Comcast) upgrading there equipment and causing problems on the network.

That could do it.
Glad its working now.