> We might be jumping ahead here. what does work?? You look like a > netcafe, are you having trouble with your other cs servers that are > listed on the website? Are they setup different?
The other ones are 1.5 servers, which we can play cross-store because of both stores being on the same netblock. > Does the server come up correctly and add the master servers? Yes > Can you connect to it and authenticate internally? No > Can you do it externally? Yes > Are you getting any error messages? Incorrect steam userid ticket. (internal) > Is the server logging in using the same steam login as the client/game > your trying to connect with? No > Most likely its "port forwarding" but it doesn't get setup the same way *breath* here we go. Here's the problem. The stores are set up where the clients are assigned local addresses. (192.168.1.*). They are handed STEAM logins thru CAServer. All Cafe logins are handed to the clients on a dynamic basis due to CAserver. The server has it's seperate login "extremeserver". Because I want to have outside customers/other store's customers (we have 2 stores), play on the server, it was given an external address... 209.103.209.244, completely open to the internet. The problem is that when a local store computer (bgr), connects to the STEAM network, the STEAMnetwork assigns the UserID ticket of Badger's External, which is 209.103.209.250. However, when that client tries to connect to the server at 209.103.209.244, the STEAM server sees the clients IP address of 192.168.1.x, not 209.103.209.250, which the UID Ticket was assigned to. That's the problem. No, I dont have any aliases on my network card to give said card a 192.168.1.x address. I never had an issue with CS1.5 or the old HLDS 3.x (I've been around these parts for awhile now), because all the authentication was to make sure that your CDKey was valid. There is no port forwarding, I can connect from VFM (other store) just fine because the IP is the same as it was bound to the UID ticket. *sigh* I hope you understand my query now. You're probably asking yourself, "Why Adam, why don't you give all your client machines a public address?" 2 reasons 1) Security 2) Cost. Security comes into play where because they are all hidden in non-routable space, I dont have to worry about the newest WinXP bug making it's way into the store without a user bringing it in themselves. Cost comes into play considering we only have 16 addresses per store. That's 32 addresses total.. We have ((20 client computers + employee) * 2) + 9 servers + 2 routers. That's 53 IP addresses that I would have to get if I were to throw everything on a public. I see no reason to waste precious IPv4 addresses. However, my ISP may have found a workaround, in where I have to get a WIC card to add to my router (that's where the additional 300$ comes into play), and hopefully we can Force stuff to NAT thru that other interface. We'll see how it goes. I'm just disgusted that I have to pay monthly for this crap, and have to pay MORE to make it work. I personally wish Steam a death, a painful death upon the content servers are erased without a trace, and millions of people see the system for what it is, a way for content control(lockdown and restrictions) and more revenue, not a system that is user-friendly. However, that's just one mans view. It's probably been recited many times thru this list, however, I haven't read it considering I .filter all my messages nowadays. To each their own, however. Thanks, Adam ---------------------------------------------------- Adam 'Starblazer' Romberg Appleton: 920-738-9032 System Administrator Valley Fair: 920-968-7713 ExtremePC LLC -=- http://www.extremepcgaming.net _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
