windows 10 DCS server

[july865]

anyone tried running a DCS server with windows 10 ver. 9926 with any success?

game runs.

server is visible on LAN only and works. but thats it. no one outside the LAN can connect.

DMZ'd the server, added rules to the router, and firewall, disable FW.

uninstalled, reinstalled, ran as admin. deleted the network.cfg file, cleared all the netsh caches, etc, etc. all the usual stuff found on here tried and failed.

my game computer can host without issues. tried swapping the router setup with the Win10 machine, still nothing. windows preview community is no help

i know its preview, just testing.

any suggestions?

[HiJack]

Server works perfectly in Windows 10 9926. You must have done something wrong on your router. You should "port forward" TCP 10308 and UDP 10308.

[july865]

[ATTACH]112823[/ATTACH]

i have without success. even uninstalled and re installed LAN drivers.

[HiJack]

[ATTACH]112823[/ATTACH]

i have without success. even uninstalled and re installed LAN drivers.

What Internet router do you have?

[Pman]

agreed, sounds like a routing issue to me

 

Pman

[Maxzouz]

[ATTACH]112823[/ATTACH]

i have without success. even uninstalled and re installed LAN drivers.

 

I think that you need to specify your local network address where the server is running. Something like 192.168.x.x in "Service user".

 

And you don't have to add the 10309 just set the range to 10308 ~ 10308 and you'll be just fine.

 

 

Regards

 

Max

[HiJack]

I belive he has configured this on the wrong page in his router. There should be a page to use for "port forwarding" to get around the NAT of the router. And the address is needed to the server/host running the DCS server, typically 192.168.0.x. Guides on how to set up port forwarding is here:

http://portforward.com/english/routers/port_forwarding/

[july865]

i had it configured to port forwarding didnt work. then tried port triggering since i have 2 machines that i use to host (my gaming rig and the Win10 machine).

netgear is weird when you have 2 machines that require the same ports opened. so port triggering seemed a better approach.

i had added port 10309 to try everything i could to open the server.

[Shahdoh]

Not sure if this will work for you, but it might be worth a shot. In Windows 7 a little while back, I had the same issue. Everything was setup up perfectly, and yet, it did not work. I finally changed the IP address of the server machine, updated the port forwarding accordingly and BINGO! It worked and has been working great since!

 

Good luck!

[Looney]

I use a netgear router as well and almost have the same screen as in your screenshot. Service user should hold the IP adress of the server machine for the forwarding to work properly. If you use DHCP, you'll need to recheck the port fowarding from time to time as the IP adress of the server may change when the lease ends.

[BitMaster]

i had it configured to port forwarding didnt work. then tried port triggering since i have 2 machines that i use to host (my gaming rig and the Win10 machine).

netgear is weird when you have 2 machines that require the same ports opened. so port triggering seemed a better approach.

i had added port 10309 to try everything i could to open the server.

 

 

Ehhhm,

 

Netgear behaves totally fine there.

 

You must not use one and the same port twice in a Port Forwarding config file. If you do so then upon loading the linux module at least will refuse to do so and stop. There are 65535 Ports, you must only use them ONCE in a firewall's NAT based set of rules to bypass the NAT.

 

If you need two sets of those ports you will have to use different external IP's or different ports for the server internally OR use different ports on your router ( like always +5000 ) but redirect them to the standard port in your LAN, that is also valid.

 

If you dont have multiple WAN IP's your best choice is to change ports for DCS in DCS and configure 2 sets of rules.

IF you cant change the module listeneing port(s) you can use the billiard bounce redirect as described before, the +5000 thing.

 

2 FTPs on 21 tcp ( data on 20 udp doesnt matter as it is outbound and iniciated from inside ):

 

1.FTP: Port 21 21client<-->21router<-->21server

2.FTP: Port 2121 21clientY<-->2121router<-->2121server

or

2.FTP(+5000) : Port 5021 21client<-->5021router<-->21server

 

those are basically the different variants of port forwarding in principle

 

each knode can talk at it's own port, there just needs to be someone who knows what the initial port is to get the handshake done, the rest is usually all handled on different ports and also protocols.

 

You should know how a IPv4 LAN works and what PFW is or you have limited chances to succeed by also knowing exactly what you have done.

 

Bit

[BitMaster]

addendum:

 

Variant 1 and 2 works on the same OS, the 2.+5000 thing needs at least two OS's as you can also only use one port only for ONE program at a time. You may also not try to use 21tcp for app A and 21udp for app B, that will also not work afaik in PortFW rules.

 

So if you run the 2 DCS servers on 1 OS you will need to reconfigure one of them DCS's to use a different port(s) to listen to incoming requests.

[BitMaster]

a workaround for 2 OS's are: another NIC in your PC or another virtual IP adress from windows network config. The latter one is for free but shares hardware, not good if you want to avoid lag.