»CypherJF Posted January 5, 2014 Report Posted January 5, 2014 (edited) I have a subgame2 installation, running on Win 2008 R2 (64bit) server, and one thing I'm noticing is that if the population of my server goes to an odd number, Continuum lists the zone as red. If the population is even, it turns green. I've also confirmed the behavior using a custom UDP packet app to ping the "ping" port (ie: server port + 1) and I get receive timed out messages. Anyone have this issue before? Anyone else potentially running on a newer OS (64 bit)? Note, it seems to start happening after 5 people, we think. Edit: at this point, I can run a UDP ping on the physical host successfully when I'm not able to do so remotely. Would this imply somewhere in the networking stack is causing it to drop the packet maybe? Edited January 5, 2014 by CypherJF Quote
PoLiX Posted January 5, 2014 Report Posted January 5, 2014 I remember a lot of oddities with windows server 2003 and 2005, so wouldn't doubt it carried over to 2008. I think it was also only the web version on 2003, don't recall which 2005 caused issues. You might start searching MGB's forums around that. Quote
»CypherJF Posted January 5, 2014 Author Report Posted January 5, 2014 More oddity, it appears to only occur if the population is at 6 (?). We've gone up to 8 people tonight (inc bots) and ping worked at that point. Will have to keep an eye out if we can get more population in there to see if there are other levels where it acts up. I'm keeping the option of downgrading to Win Server 2003 - 64bit in my back pocket. Quote
»CypherJF Posted January 8, 2014 Author Report Posted January 8, 2014 I don't know why I didn't think about this earlier, I ended up writing a fake UDP ping application which listened for the request and gave a response. I set it to an active port only configured on my Continuum instance and let the population # increase with each ping "hit". So it started with 0, and rotated upwards. I watched for the first 20 or so responses and only when the population = 6, the response was never received by Continuum. It's definitely something on the host or it's network stack that's dropping the packet - the server-code that I wrote isn't receiving any runtime exceptions when it occurs. Quote
Dr Brain Posted January 9, 2014 Report Posted January 9, 2014 Open up wireshark and see what happens. Quote
»CypherJF Posted January 10, 2014 Author Report Posted January 10, 2014 (edited) Open up wireshark and see what happens. I did and UDP was sent out over the network adapter. However, it never arrived to the remote destination(s). But late last night everything randomly started to work without any corrective action on my side. Host says they didn't change anything either. So that's that. <_< Edited January 10, 2014 by CypherJF Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.