SOLVED: Cannot connect to Steam Master Server

[Xb0x3r]

Maybe you should just try to use a new Linux distribution, I personally use Red Hat Server ES 5 Update 2. It should be packed with any possible driver you could need (If not, good luck compiling one). I like it because the firewall can be easily disabled and it seems to run the srcds quite well. I cannot criticize or recommend CentOS 5 seeing as how I've never used it, but sometimes it cant hurt to have a change.

[swatmajor1]

I would gladly try another OS, but since I don't have physical access to the box, and I already have everything setup for my website, VoiP, etc, it wouldn't be in my best interest to swich out so soon.

Maybe I'll look into another Linux distro with the next server I might get.

[Mooga]

Contact your server provider.
You might need to request access to some ports.

[swatmajor1]

UPDATE: I testing connecting with my frewall turned on and off, no success. So, I'm guessing either Steam doesn't like my server, or something else.

Also, to Mooga, I run the server box, with all ports, IP's and domains attached, so...yeah. Anyway, I'll just have to keep going at this til it works, or die trying.

[swatmajor1]

Hi there,

I thought I would send an update on this. Steam has FINALLY sent me a reply for the ticket I sent a while back, and this is what they had to say:

"Hello Jim,

Thank you for contacting Steam Support.

Unfortunately, we cannot offer direct support for Dedicated server issues. You may, however, be able to find helpful information in the Dedicated Server forums."

Well, thanks Valve. And here I thought that if anyone could help me, it would be the creators of the programme.

So, here is a summary of what's wrong with my server/s.

• Server will not connect to Steam Master Servers, thus not shown on internet list
• Tested server via VPN, no errors
• All required ports are opened. also tested with firewall off, no difference.
  

Again, if there is NAYONE who can help me, it would be great

[css]

The problem is always you. Valve has made the program and the program is used on tens of thousands of servers. None of them have your problem. You've got the problem. It's you that makes the problem. That's why you get that kind of generic reply from Valve.

Double, triple-check and forever-check the settings until you get your server online. Don't think for a second that the fault is in the program. It's not. It's you.

Be real. This is what you've been writing:

Quote:To me honest, I have no idea what half this means, so any help explaining it would be great.

You've got the server box, but you can't understand it.

For reference take a look what I was talking with SerajewelKS at http://forums.srcds.com/viewtopic/7686 . He's real professional who debugged the problem on very low network level. Eventually he got the problem solved - seemingly the same problem you've got - but he really knew what he was doing.

My guess is that your ISP has firewall even though they've denied it. As long as you don't know how to setup your own UDP server on port 27015 or dump the raw network data on UDP ports this conversation is useless. We can throw up different ideas which all fail because nobody can really know what's truly happening.

Your best chance is that you get one-in-a-million-fluke and there's someone else on this forum with the same hosting company running Source server on his server.

Sad but true.

[swatmajor1]

I'm hurt, I'm really am. Don't you think I haven't tried all of this. I got all of my network data, contacted my Host Provider, and nothing. All my ports are open, and there isn't anything using the ports which the servers need. I checked the debug log, nothing recorded, and yes, I had -debug on.

I have even been using tcptrack to monitor my connections, and from what I'm seeing, there is an idle point on the IP's which are the steam ones. I have also got a video recording all connections prior to starting my CSS server, to when it shows the Could Not Connect message.

A video, 1.1MB, can be downloaded here, at http://www.swatmajor1-hq.com/index.php?option=com_jdownloads&Itemid=60&task=view.download&cid=4

I have also used netstat -anp, which tells me what programs are using what IP's and ports, and nothing which conflicts with the required steam ports shows.

So, I ask you, the srcds community, what possible reason could there be for my server not connecting to the Steam Master Servers.

Signing off,

Swatmajor1

[swatmajor1]

Ok, going through my packet monitor, I have come across this:

ICMP dest unrch (pkt fltrd) (56 bytes) from 203.89.74.45 to 119.63.204.26 on eth0

This happens several times, until the CSS server gives up and says it can't connect.

Is this the type of data you require to make an assessment, or is it just useless packet drops?

A video showing all data collected when starting up a CSS server can be found here: http://www.swatmajor1-hq.com/files/CSS%20Server%20Active%20Connections%20-%20IPTraf.swf

Now I think we are in business here. So I'm guessing that there is a server or something between my server and the Steam ones, whether it be on either end, it isn't sending me the packets sent by Steam back to me, so it can't create the connection.

Signing off,

Swatmajor1

[swatmajor1]

Ok, I have just used tcpdump on port 27011, and here is the output from the execution of the CSS server command.

Code:

23:23:02.204507 IP host.swatmajor1.com.27015 > 72-165-61-189.dia.static.qwest.net.27011: UDP, length 1
23:23:02.204526 IP host.swatmajor1.com.27015 > 69.28.151.162.27011: UDP, length 1

From what I'm reading here is that anything I send to the Steam Servers are getting through, but the packets from the Steam servers are not.

Also, here is a piece of info from IPTraf:

Code:

ICMP dest unrch (pkt fltrd) (56 bytes) from 203.89.74.45 to 119.63.204.26 on eth0

I gather that the packets sent back to me are being rerouted somewhere along the line, and are not reaching me.

I have sent everything I have gathered to my host provider, since if there is anything which is to do with their hardware, I'll ask them to allow the packets through.

Well, at least now I have a decent idea what and why my server isn't behaving properly. Maybe now I can fix this, once and for ALL .

Signing off,

Swatmajor1