Rainbow Six Vegas 2 Standalone Dedicated Server Setup

Please note: Replace <gamedir> with the location of where you installed the game to.

SADS = Standalone Dedicated Server.

Step I - Set Up Your Server

Now configure your SADS by editing the

<gamedir>\Binaries\R6VegasServerLaunch.bat

where the most important setting is to get listed in the Ubi Master Servers

1
2
3
SET ONLINEPLAY=1
SET ONLINE_USERNAME=<UbiUsername>
SET ONLINE_PASSWORD=<Password>

after making all other changes (you can also leave them to default for now), edit

<gamedir>\KellerGame\Config\PC\R6VegasServerConfig.ini

Default values on m_iRestrictedItems for those who want to leave the strange toys out of the multiplayer games are

1
2
3
4
5
m_iRestrictedItems[0]=1541
m_iRestrictedItems[1]=1792
m_iRestrictedItems[2]=1793
m_iRestrictedItems[3]=1794
m_iRestrictedItems[4]=1796`

this includes the Motion Sensor, Tear Gas, Gas Mask, GPS Device and the Radar Jammer.

Additional Maps from the Fan Pack and the Comcast Event Map are included as

1
2
3
4
5
6
7
8
;Comcast Event
m_iSelectedMaps[13]=214
;CQB Training - Dark
m_iSelectedMaps[14]=220
;Calypso Casino
m_iSelectedMaps[15]=221
;Murdertown - Dark
m_iSelectedMaps[16]=222`

After you completed your initial setup you can already run the server by double-clicking the R6VegasServerLaunch.bat we’ve just edited. You should see something like

1
2
3
4
5
Log: Loading map.
Log: Starting network.
DevNet: TcpNetDriver local address 192.168.0.20:3074
DevNet: TcpNetDriver public address 81.6.6.89:3074
DevNet: TcpNetDriver NAT Type: OPEN

or

1
2
3
4
5
Log: Loading map.
Log: Starting network.
DevNet: TcpNetDriver local address 192.168.0.20:3074
DevNet: TcpNetDriver public address 81.6.6.89:26778
DevNet: TcpNetDriver NAT Type: MODERATE`

Write down the port number behind the “public address”, in my case 26778.

Step II - Configure your router/firewall

First of all you need to configure two things:

  1. Firewall Rule
  2. Port Forwarding
    Some routers might do both at the same time or configure firewall rules for you, when you configure NAT port forwarding rules, if you chose to do so. Whichever is the case, make sure both is done.

According to the official Ubi Knowledgebase you need the following ports:


Login/Matchmaking services:

Outbound TCP 3074 (generally don’t need any configuration for this)

Gameplay:

Outbound UDP 3074-3174 (generally don’t need any configuration for this)

Inbound UDP 3074-3174 (on a firewall, you must allow inbound traffic on these ports, on a home router with NAT, must forward inbound traffic on these ports to your PC)

Custom Head:

Outbound TCP 10130 (generally don’t need any configuration for this)

Inbound TCP 10130 (on a firewall, you must allow inbound traffic on this port, on a home router with NAT, must forward inbound traffic on this port to your PC)

10130 is the default port used by the Custom Head feature. You can change this port in the Extras\Options\Multiplayer menu.

Voice Chat:

Outbound UDP 10140 (generally don’t need any configuration for this)

Inbound UDP 10140 (on a firewall, you must allow inbound traffic on this port, on a home router with NAT, must forward inbound traffic on this ports to your PC)

10140 is the default port used by the Voice Chat feature. You can change this port in the

Extras\Options\Multiplayer menu.


But now IMPORTANT; if you use your server behind a NAT-ed connection (which applies to most likely any home network and all servers which are not assigned public IPs), the server will use a high range UDP port, the one you’ve written down earlier, in my case UDP 26778:

UDP 26778, WAN IP (inbound)

which will have to be forwarded to

UDP 3074, LAN IP

thus you will have to make a NAT rule

UDP, PORT 26778, WAN IP -> UDP, PORT 3074, LAN IP

and a firewall rule which allows

UDP, ANY IP, ANY PORT -> UDP, LAN IP, PORT 3074 (WAN Interface)

All other ports can be forwarded according to the official documentation.

Share Comments