Lan Connect To A Server Connected To Internet
Browser_ICE
Join Date: 2002-11-04 Member: 6944Members
Join Date: 2002-11-04 Member: 6944Members
<div class="IPBDescription">Lan connect to an NS Internet server</div> I have 2 PCs where one I'm trying to do an NS Internet server. When I have the 2nd PC trying to connect to it, my NS on my client PC bombs out with "<b>Could not connect to game server Reason : could not complete connection attempt</b>".
My client PC doesn't have Internet access. It's connected to my Internet one via Ethernet cable. I've been using this network configurations for months without problems (access in both ways fully working). My main PC isn't setup for Internet connection sharing because my client PC is my office laptop. So when I'm not using my small network, I want my main PC to be fully fonctional for internet and games, as a client PC. Besides I don't want to keep installing/uninstalling Internet access everytimes my laptop isn't connected to my main PC.
So being said, what's wrong with the client PC trying to connect to my main PC acting as a 1.01 server for internet ?
My client PC doesn't have Internet access. It's connected to my Internet one via Ethernet cable. I've been using this network configurations for months without problems (access in both ways fully working). My main PC isn't setup for Internet connection sharing because my client PC is my office laptop. So when I'm not using my small network, I want my main PC to be fully fonctional for internet and games, as a client PC. Besides I don't want to keep installing/uninstalling Internet access everytimes my laptop isn't connected to my main PC.
So being said, what's wrong with the client PC trying to connect to my main PC acting as a 1.01 server for internet ?
Comments
(I haven't run a half life server for almost a year now)
What I previously had was DSl/Cable, and a local lan all going into the same set of computers. Since the DSL/Cable connections both only had one IP address, I had to somehow manage to make all computers on the network see both of those. That was done using a linux box to load balance the connections out, plus some creative firewalling. Ah, now what does this have to do with haflife/Ns?
Well one of the servers was my DoD mod server running on halflife. It had 2 network cards in it. One went to the linux firewall, and that optained the "Real world" Ip. (Something like 64.11.22.33) the other network card was setup for an address of 192.168.10.15 (This being because my internal network used the 192.168.10.xxx range)
Now when you start the hlds.exe program, you can specify what IP it uses. This is obviously there for machines with dual interfaces, etc. So I'd startup: hlds.exe -ip 64.11.22.33 (etc etc)
Now, all of my 192.168.10.xxx numbere connections all went to therir own hub. That hub was uplinked to the linux firewall box, and that did the routing between subnets. (Non essential data for the topic at hand, but I thought I would share..)
Point being, on my other 192.168.10.xxx machines, to connect to my server, I would just fireup halflife from the command line: hl.exe -game ns -console -numericping -noipx once it had started, I'd bring down the console, and type: connect 192.168.10.15 (That being the IP of the Internal Interface Nic card on the game server..) This worked flawlessly every time.
Key things to remember. Have a sperate hub/switch for your Local lan segment (192.168.10.xxx) uplink that hub to another.. on the other hub, plug in your cable-dsl-router or whatever you use to share the connection.
Note: I don't know how this would work if you're not using a router. Sorry. Also, please excuse the poor typing. English is not my native tongue, and I am severely dyslexic.
<!--emo&::skulk::--><img src='http://www.unknownworlds.com/forums/html/emoticons/skulk.gif' border='0' valign='absmiddle' alt='skulk.gif'><!--endemo-->