Jump to content

Home

Network Problems


prof123

Recommended Posts

Hello,

 

I'm trying to setup a dedicated server on a network. The server is working fine but I'm having a problem. There are 2 other computers on the same network as the server. One can connect to the server just fine, while the other cannot. The computer that cannot connect can identify the server is online through jedi outcast, it reports a ping of roughly 400 ms, and when I attempt to connect, I'm never able to enter the game and it just keeps counting.

 

The difference between the computer on the network that does work, and the one that does not is that one is running Sygate home office software that allows the 2 other computers to obtain an IP address. There is no firewall involved in this setup. The computer running the sygate software is the one that cannnot connect to the jedi knight dedicated server.

 

I assume this sygate software is part of the problem connecting to the jedi knight dedicated server. I cannot modify the network setup, and the Sygate software is the only method in allowing the other 2 computers to obain IP address.

 

If anyone has any ideas that might solve the problem I'm having please let me know.

 

Thanks,

Brian

Link to comment
Share on other sites

I've never used sygate and this may not apply, but maybe....

 

 

If sygate is acting as a dhcp server, and is assigning reserved IP's to your clients. It may just be a matter of disconnected IP ranges. For example maybe the sygate box has a real IP the server is running on, and the clients have a psuedo IP. If nothing is routing from 192.168.0.0 to your public ip then it wouldn't work for sure.

Link to comment
Share on other sites

Thank you both for your replies.

 

KnightHawk, my sygate software is functioning as a dhcp server and is assigned IP's to the clients. You suggest that the problem might be nothing is routing from 192.168.0.0 to my public ip. What I can tell you is that other clients not on my network, via the internet, can access my jedi knight server. I know this because people have played on my server before. Does this eliminate your theory from being a possible source of the problem?

 

Thanks,

Brian

Link to comment
Share on other sites

No not at all. That's just what I"m saying. Your JK2 server is the one with the public IP. The other 2 internal machines are not. So it makes sense that only internet players can connect to the server. Your internal machines would have to have some sort of NAT in place to provide a way for the internal machines to connect.

 

 

NAT = Network Address Translation

Link to comment
Share on other sites

To clarify, when you say "public ip" do you just mean the IP i get from my cable ISP? Or are you refering to the IP that is being registered through the Jedi Knight 2 server? Below I have detailed my current network setup: (The dash's are needed in order to maintain spaces)

 

 

------------------------ Cable Modem

 

------------------------------- |

 

---------------------------- Switch

 

--------------------- / ------- | --------- \

 

------------- Sygate ------- JKII ---------- Comp

------------- Comp -------- Server ------- 192.168.X.X

------------- IP from ------- Comp

------------- Cable ISP ----192.168.X.X

 

 

After reading your post again, I want to clarify that the Sygate software is running on a different computer than the JKII server software. And that my third computer, running neither the Sygate software nor the JKII server, can connect to the JKII server just fine. This third computer also obtains a "psuedo IP" for internet access.

 

Now, you mention NAT technology as a means of possibly solving my problem. I beleive certain routers have NAT technology. Is there a way to implement NAT through software, not hardware?

 

Thanks again for your help,

Brian

Link to comment
Share on other sites

The difference between the computer on the network that does work, and the one that does not is that one is running Sygate home office software that allows the 2 other computers to obtain an IP address. There is no firewall involved in this setup. The computer running the sygate software is the one that cannnot connect to the jedi knight dedicated server.

 

Does the game show up as an Internet or Local game on your Sygate machine? You should be connecting locally via your lan - ping should be a lot less than 400.

Try forcing a connection by bringing down the game console and typing \connect xxx.xxx.xxx.xxx where xxx.xxx.xxx.xxx is the IP address of your JK2 server (probably 192.168.0.2 or 3).

 

You would need to use NAT if you want the outside world to see your server, but we can discuss that after we have got all your local clients working ;)

 

What I can tell you is that other clients not on my network, via the internet, can access my jedi knight server. I know this because people have played on my server before.

 

I can't see how this is possible without using NAT with your current set up. Are you sure you have not already set up any 'Access Rules' in Sygate (which is just port forwarding in Sygate speak)?

Link to comment
Share on other sites

Yes, I am a bit confused about the whole set up. It looks as if all computers are connected to the outside world (internet). Allthough, you have only one official ip. Maybe thats why the sygate-server can not connect to the other servers. I would recommend a seperation of your local network and the official network. Then one of the servers need to work as a gateway. He should have two network interfaces. One connected to the cable modem, the other one connected to the switch. The gateway computer should do also the routing. Then you would need to set up NAT such that the internet beleeves that the JO server is running on your gateway/router machine.

 

BTW, I cant see the benefit of DHCP. You are managing only 2-3 local ip-adresses, right? So if you think you can live without it, you could use the following ip-adresses:

 

192.168.0.1 router/gateway (sygate local address)

192.168.0.10 JO-Server

192.168.0.11 Other PC

 

Netmask would be 255.255.255.0

The gateway on 192.168.0.10 and 192.168.0.11 is 192.168.0.1

 

My set up is as follows: I have a router with a build in fire wall. I connect the switch to it, which is connected to my computers. For the JO-Server I configured NAT on the router.

Link to comment
Share on other sites

I agree with you Nuke. For my setup I use Sygate on my gateway as a router/NAT. This gateway has my ADSL usb modem as my external/internet network interface and a standard nic connected to a switch for my internal network.

 

I believe Sygate has a built in function called 'Single NIC' which creates a virtual NIC for the internal network (assigning itself 192.168.0.1 IP address), which would appear to be what Brian is using, by his diagram. I have not used this feature so I am guessing :) It is meant to simplify things for end users so they don't have to install an extra nic, but it seems to course more confusion to me.

 

I agree about DHCP also. If NAT is to be used to forward ports then there is no guarantee that your JK server will be assigned the same IP address all the time, so any Access Rules set up would need to be changed. I would recommend manually setting up IP addresses or if this is not possible, put your JK server on the machine that is running Sygate. That would be the simplest solution as it would not require any port forwarding and you could leave your DHCP as it is.

Link to comment
Share on other sites

Jasco,

 

that brings a bit light into this. It might be the feature he uses. "Single NIC" makes it possible to have two IPs one the same Network Interface Card (NIC). I think thats not a good feature and I dont know of anybody who has asked for that. But I think I understand now the network graph.

 

However, so now the sysbase computer has two ip-adresses one local and one official from the provider. The others have IPs they got from the dhcp server on the sygate computer. I assume also that NAT is active, mapping all relevant ports (23???) from the sygate computer to the JO-Server. Hence, the sygate computer can not use this ports for his own purpose? In that case the JO-would not work on the sygate machine. Would that solve the puzzle?

Link to comment
Share on other sites

Originally posted by Jasco Smlee

I agree about DHCP also. If NAT is to be used to forward ports then there is no guarantee that your server will be assigned the same IP address all the time, so any Access Rules set up would need to be changed. I would recommend manually setting up IP addresses or if this is not possible, put your JK server on the machine that is running Sygate. That would be the simplest solution as it would not require any port forwarding and you could leave your DHCP as it is.

 

Right you are: one should either use NAT or DHCP. The access lists or NAT tables would be useless if the ip changes.

Link to comment
Share on other sites

I assume also that NAT is active, mapping all relevant ports (23???) from the sygate computer to the JO-Server. Hence, the sygate computer can not use this ports for his own purpose? In that case the JO-would not work on the sygate machine. Would that solve the puzzle?

 

I think you probably hit the nail on the head there! Brian, perhaps if you tried running your server or client on a different port to the default?

Link to comment
Share on other sites

Thx, Jasco

 

Well it might be that either one of the following changes of the config would solve the issue:

 

1/ Put the JO-Game on the sygate computer and disable the access lists. Use the former JO-Server to connect locally to the game

 

2/ Remove sygate and put it on the JO-Server (do not configure access lists)

Link to comment
Share on other sites

Strange, I thought I posted a reply already. Well, for whatever reason it didnt seem to get posted, and thus the delay in my response.

 

You are correct in assuming I'm using the single nic option in sygate.

 

Nuke, those 2 suggestions would work but I cannot modify the server setup. The reason being is I'm moving soon and it would not be worth the time to redo all my software when I'm moving in just 1 week.

 

So I thank you both for your help, but I will halt my attempts to get the server setup until I've moved. At that time I will setup my network accordingly as to not run into the same problem. When I encountered this problem 2 weeks ago, I felt like I had plenty of time to set it up before I move, but I guess not.

 

So thanks again,

Brian

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...