OldCrow

Registered Users
  • Content count

    765
  • Joined

  • Last visited

Community Reputation

0 Green Tag

About OldCrow

  • Rank
    WWII ONLINE BUILDER [GOLD]
  • Birthday
  1. 209 at 183ms (ouch!)
  2. Nope, it's not just a dialup problem. I've had this problem since the initial 1.19 release, and I'm on a 128K dedicated digital ISDN connection. BTW just FYI, T1 is not gigabit..if you're referring to a telecom T1 line, it's roughly 1.5 megabit. Unless you just meant that you have a T1 coming into your gigabit ethernet LAN.
  3. Same here, it's been a problem ever since 1.19. I've even gone so far as to completely wipe my machine and reload XP Pro/SP2 (it was due for a wipe anyway), but that still did not fix the problem. I can play infantry, and push atgs/aa guns, that's it. If I drive or fly any vehicle I get the dreaded CTHL usually within 1-2 minutes. I've updated every driver available. I've defragged. I've completely reinstalled the game. I've used the NT compatibility trick. I've used just about every variation in the settings app possible. I've turned off the firewall on my router. KFS1's netcheck utility runs fine. NOTHING changes the cthl problem. For their sake, I too hope they get this problem fixed before the retail release, or it's going to be June 6, 2001 all over again. System specs ----------------- 128K dedicated ISDN digital connection (nailed up 24x7) Pentium 4 3.3GHz Asus P4C800-E Deluxe MB w/1GB DDR400 250GB EIDE HDD Nvidia 5900 Ultra AGP 8x w/256MB, driver version 6.14.0010.7772 On-board SoundMAX AC97 integrated sound, driver version 5.12.0001.3890 On-board Intel ethernet controller Windows XP Professional w/SP2 and all critical updates NO XP firewalling enabled, no third party firewall software
  4. Ok, what did they change now? Yesterday they took the servers down temporarily. Was it some sort of server side change? Ever since then, things have gone from bad to worse. At least before, even though I couldn't fly aircraft or drive vehicles without getting disconnected within a few minutes, I could still, for some strange reason, play as infantry. Playing infantry is not my favorite role to play but it's better than not being able to play at all. But now, ever since they did, well, whatever it is they did, I can barely even do that now. Now about 80% of the time, I have to hit ctrl-alt-del and kill ww2.exe because it is no longer responding. On the off chance that I do actually get into the game, I can't change personas or brigades because when I do, the persona screen or the brigade screens come up empty. And even when I *do* manage to spawn in as infantry, I no longer get any mission debriefings. <rant> What is up? I sure hope they are making some progress somewhere because my patience is wearing very thin here. If I was a regular subscriber I could just cancel, but seeing as I'm a gold builder, I'm beginning to feel especially screwed. </rant> Sorry, had to blow off some steam. But I *do* hope they figure this out, and soon. Edit: I should add, that I am getting this behaviour on all three of my home machines, one of which has a completely fresh install if XP SP2 that I reloaded just to test with.
  5. I've only seen the "deterministic network enhancer" thing on PC's that had a VPN client of some sort installed, unless I'm mistaken.
  6. Same here..never had this problem on the beta servers.
  7. They are working on the problem. I worked with KFS1 last week to help and try to isolate the issue. I sent them several packet dumps of some disconnected sessions and they were going to analyze them, but I have not heard back. Rest assured though, they are very aware of the issue and are working as hard as they can to try to fix the problem.
  8. Training server works fine for me, too. Weird.
  9. Nope, same problem. I have probably spent 10 hours since the 1.19 release fudging around with various tcp settings on both my router and my desktop to no avail About all I've been able to do is extend the amount of time before disconnect from 30 seconds to 5 minutes.
  10. I have an older 1Ghz P3 box that I had retired so last night I fired it up, and reloaded a fresh install of XP on it and did all of the updates, and then copied, verbatim, my ww2ol installation from my primary machine. Oddly enough, it works fine - no disconnects (although of course it's slow as hell). So that eliminates my internet connection. All that leaves now is either my hardware or my XP installation :/ I went through the registry on both boxes and did a line by line comparison of all the IP & TCP settings and copied every setting from the fresh box back to my primary box, but it didn't make any difference. I'm stumped. I sure don't want to have to reload my primary machine, I've got tons of stuff on it ::bleh::
  11. Stay away from it if your main purpose is for internet gaming and the like. I made that mistake and ended up scrapping it and going with ISDN like 3 months later. Latency is baaadddd. WW2OL was for the most part unplayable.
  12. I'm running Windows XP SP2 and I tried increasing my MTU size from the default to 1500 and also the TTL from 64 to 96 and it helped some, but I'm still disconnected after about 5 minutes (instead of after 30 seconds or so before).
  13. Unfortunately the server patch to fix the auto-disconnect/mtu issue didn't fix my problem, either
  14. Yeah, it is strange. Thanks for you help though
  15. I am only selectively filtering traffic inbound (TO my PC) to specific ports on my router. I allow every port except for a certain few, namely the tcp/udp ports 137/138/139 etc, but everything else is allowed. All traffic outbound (FROM my PC) is allowed. Ports 27015-27025 are the ports that the Playnet servers are listening on, that my wwiiol client would connect to (running netstat -an while running the game you can see this). I can spawn in as tank/infantry/aircraft/whatever, and can see other players momentarily before I get the connection lost message. Seems to range anywhere from 30 seconds to 5 minutes before I get kicked out. I was actually able to fly from calais to dover today before getting disconnected. I run dual monitor and kept a few active ssh/web windows open on the other monitor just to check traffic, connectivity, etc., and all seems to be okie dokie with my ISP connection as far as I can discern. But just to be on the safe side, I temporarily disabled all firewalling on my router and verified that I could make an inbound connection to any port on my PC from a unix box I have colo'd at another ISP using nmap and other tools, and tried again, but got the same results. ::scratches head:: Any other ideas? EDIT: Just noticed something new - even after I get the "Connection to Host Lost!" pop-up, I can still send/receive chat on my chat bar. Here is some output that I captured- Connections (using netstat -an from cmd line) - filtered for Playnet IP's only The Launch Window where you type in your name and password to launch ===================================================== Active Connections Proto Local Address Foreign Address State TCP 192.168.0.106:1845 66.28.224.240:27015 ESTABLISHED After hitting enter at the launch window ============================ Active Connections Proto Local Address Foreign Address State TCP 192.168.0.106:1845 66.28.224.240:27015 TIME_WAIT Before the Splash Screen comes up ======================= Active Connections Proto Local Address Foreign Address State TCP 192.168.0.106:1845 66.28.224.240:27015 TIME_WAIT After the Splash Screen comes up ======================== Active Connections Proto Local Address Foreign Address State TCP 192.168.0.106:1845 66.28.224.240:27015 TIME_WAIT TCP 192.168.0.106:1846 66.28.224.143:27017 ESTABLISHED TCP 192.168.0.106:1847 66.28.224.142:27018 ESTABLISHED While in the UI ========== Active Connections Proto Local Address Foreign Address State TCP 192.168.0.106:1845 66.28.224.240:27015 TIME_WAIT TCP 192.168.0.106:1847 66.28.224.142:27018 ESTABLISHED TCP 192.168.0.106:1848 66.28.224.144:27016 ESTABLISHED After getting the "Connection to Host Lost!" message ===================================== Active Connections Proto Local Address Foreign Address State TCP 192.168.0.106:1847 66.28.224.142:27018 ESTABLISHED