ENO Posted December 1, 2012 Posted December 1, 2012 Eh guys- I'm trying to work out some connection issues so I thought I'd describe my setup a bit and get some further input. Skate has also helped me a bit in another thread so I thank him for that but I seek more insight. Basically, my main internet connection comes from a cable ISP into a DCP3825 router which serves my client rig as well as my server rig. Though I haven't locked down my IPs... they haven't changed in a long time. My server rig is in a DMZ from that router, while my client is not (obviously). It seems that for some reason while I have no trouble connecting to other servers, I can't connect on my own. This seems to only be a problem with 7570 while when I rolled back my versions to 7286 it worked fine. I am running webroot software as well on all the machines- but I have them configured to accept operations relating to DCS. I've also heard of some software that you can use to monitor your network traffic- basically you set it up on one computer to watch network traffic from another. Anyone got any input on that? Server hosts- what other sort of diagnostic software do you run to ensure that things are running smoothly? Thanks guys. "ENO" Type in anger and you will make the greatest post you will ever regret. "Sweetest's" Military Aviation Art
BRooDJeRo Posted December 4, 2012 Posted December 4, 2012 (edited) Im not going into full details in public or people i dont physicaly know due to security reasons that are needed these days. What i can tell you is that only the standard DCS port is open from outside when the server is up. The portnumber is coupled to static intranet adresses in combination with the relevant hardware MAC adresses. This seems to work for me. If anything else does an attempt at connecting on other ports or portscans are being done than everything shows up in the logs of the routers. In other words everything out of the ordinary. Im not sure if that security is still in place for the intranet with DMZ settings. depends on the logsettings. The standard windows firewall has an eventviewer and most 3rd party firewall do too in advanced sections of the software. It shows everything trying to connect etc. A step further is a packetviewer/sniffer like Wireshark that has record options and such for later packet examination in case a 'The Funny Man' is paying you a visit. Edited December 4, 2012 by BRooDJeRo
ENO Posted December 4, 2012 Author Posted December 4, 2012 Okay so just to be clear... these UDP port changes are still being filtered down to 308-309 as they come into the server comp? I'm just curious because so many our our disconnects in the logs seem to appear after a UDP port change. Now that we seem to have nailed down our disconnect issues to tankers (KC-135)... I might tighten things back up a bit. But with that being said- it's been so smooth lately I'm hesitant to ruin it! Anyway- tried to dish out rep but need to "spread" again. Frick- every time... Thanks again Brood. "ENO" Type in anger and you will make the greatest post you will ever regret. "Sweetest's" Military Aviation Art
BRooDJeRo Posted December 7, 2012 Posted December 7, 2012 Yeah, there seems to be some stuff going on there isnt it. Im not sure if i should feel bad about it, but when i need to use settings that undercut the local network security then im sorry, then its no DCS server. I could live with a distinct series of ports, but opening it all up is nogo erea for me. There is a basic need of knowing what intended connections go where. For now thats officialy only 10308 or what you set yourself. Untill ED has officialy something else in the manual im going to stick to it. When having a KC135 tanker in a mission means lower security than you might want to concider removng it for the time being. But what do i know? Im raised by some people with a western society false fear mindset which i debate by securing myself. :doh:
Recommended Posts