Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
This address is in French so the translation Many servers with load balancing, I'm sure you will find the site on the net that will explain to you in detail how to do better on steam!
Also not sure what you tried to accomplish with your 2nd ip address 192.168.1.5?
You either use different port on the same ip address. Or give the box a secondary ip adress and then you can use the same port on both ip addresses. Only then you would need to use the +ip switch.I recommend to use only one ip though and use different ports. Depending on what you will use make sure your portforwarding is matching your setup.
Wouldn't you also need to put in -console to see the server output at all?
Or does GMOD handle this different then other source servers?
This is how I would try it:
C:\scrds\srcds.exe -console -game garrysmod +map gm_construct +exec server.cfg
C:\scrds2\srcds.exe -console -game garrysmod -port 27016 +map gm_construct +exec server.cfg
If this works fine then you can try to modify it with your darkrp gamemode.
Nowadays, for security reasons, sometimes you need to call isp if you want to host things, and also, make sure your isp arent under any CGNAT (which shares public ip with multiple clients)
Also, you dont need client commands on the server, they dont do anything, same as server commands on clients(except listen servers).
ex:
This arg basically says "when connecting to a server, use the port 27005 to connect"..
Which does not make sense at all.
Same thing goes to cl_ commands, those are for clients, sv_ commands for servers.
Also, srcds don't work on port range.. must specify a single port.
If you dont know how to make a rule for the windows firewall, then just disable it, windows firewall on most cases its just annoying and useless.
Sorry my bad english.
server 1: 192.168.1.6 hosting the server on port 27015
server 2: 192.168.1.7 hosting the server on port 27115 ( I just separate servers by 100)
Setup port forward for port 27015 to go to IP 192.168.1.6 and port 27115 to go to 192.168.1.7
on the startup line use the command switches to specify the port like
-ip 0.0.0.0 -port 27015
-ip 0.0.0.0 -port 27115
client port doesn't need to be changed - it is just a hint for the client port that they should use, but the client can choose to use a different port if it desires.. eg: if 5 people are connecting from the same IP, they will each use a different client port.
When someone wants to join, they just can specify both the IP and the port and will join the server that is running on the port they specify