szln6z Posted December 16, 2007 Report Posted December 16, 2007 Ok, starting to pull my hair out. I went to play FS9 today for the first time in about 1-2 months. WideClient connects okay, but when I run a program on the client machine, it thinks FS is not running. I do have checksum errors in the wideserver log, so I've been trying to clear those up (understand they're typically hardware issues) but I have done everything I can think of. I've searched the forum for suggestions. Here's what I've done: 1. Used a different Router. 2. Used different CAT 5 cable. 3. Sent the client machine thru a wireless card to eliminate the NIC and the cable. 4. Installed a different NIC in the server. 5. Installed WideClient on a completely different computer. 6. Reinstalled TCP/IP on both client and server. 7. Rolled back driver on server NIC (I had updated the driver about 3 weeks ago) 8. Shutdown NetNanny, which I installed about 3 weeks ago. (However, I'm not convinced that it was completely shutdown, but then again, I don't have any reason to be suspicious of it; anyone else have NetNanny running successfully with WideFS?) 9. Shutdown Windows Firewall (also about 3 weeks ago, I uninstalled Zone Alarm) 10. Went thru the Home Network Wizard on all computers. 11. Confirmed the DHCP settings in the router are correct and allowed IPs .5 to .10 for assigning computers. 12. Kicked everything.... kidding. Anyway, I get a new computer this week, so that I might solve the problem. But then again, it might not... I'm guessing the issue is somewhere in my Server machine based on the fact that I used two separate client machines with no luck. Any ideas greatly appreciated. James I'm using version 6.75 of WideFS and FSUIPC 3.75. All logs: ********* WideServer.DLL Log [version 6.75] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 16/12/07, Time 16:12:07.656: Server name is JAMES 58891 Initialising TCP/IP server 58891 Initialising IPX/SPX server 58906 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 58906 Failed to start IPX/SPX Server 58906 Initialising UDP/IP server 60219 Broadcasting service every 1000 mSecs 70000 Restarting service due to total lack of use 70000 Failed to start IPX/SPX Server 70360 Incoming connection Accepted ok (skt=4160) TCP 70516 Connected to computer "LAPTOP" running WideClient version 6.750 (skt=4160) TCP 70516 **** ERROR! Sumcheck or length fails on received socket 4160 block, len=208 (time=0) 72750 **** ERROR! Sumcheck or length fails on received socket 4160 block, len=27 (time=0) 83125 **** ERROR! Sumcheck or length fails on received socket 4160 block, len=75 (time=17655) 83906 **** ERROR! Sumcheck or length fails on received socket 4160 block, len=27 (time=18456) 84016 **** ERROR! Sumcheck or length fails on received socket 4160 block, len=27 (time=18586) 87531 **** ERROR! Sumcheck or length fails on received socket 4160 block, len=27 (time=0) 88094 **** ERROR! Sumcheck or length fails on received socket 4160 block, len=27 (time=22642) 91828 **** ERROR! Sumcheck or length fails on received socket 4160 block, len=27 (time=0) 102328 **** ERROR! Sumcheck or length fails on received socket 4160 block, len=25 (time=36903) 102438 **** ERROR! Sumcheck or length fails on received socket 4160 block, len=73 (time=37003) 103156 **** ERROR! Sumcheck or length fails on received socket 4160 block, len=25 (time=37704) 103281 **** ERROR! Sumcheck or length fails on received socket 4160 block, len=25 (time=37834) 107906 Error 10053: client socket disconnected at Client: removing (skt=4160) TCP 109000 Incoming connection Accepted ok (skt=3972) TCP 109110 Connected to computer "LAPTOP" running WideClient version 6.750 (skt=3972) TCP 127469 Error 10053: client socket disconnected at Client: removing (skt=3972) TCP 130063 Incoming connection Accepted ok (skt=3992) TCP 130125 Connected to computer "LAPTOP" running WideClient version 6.750 (skt=3992) TCP 136016 Error 10053: client socket disconnected at Client: removing (skt=3992) TCP 710860 Incoming connection Accepted ok (skt=916) TCP 712985 Connected to computer "LAPTOP" running WideClient version 6.750 (skt=916) TCP 712985 **** ERROR! Sumcheck or length fails on received socket 916 block, len=370 (time=0) 728625 **** ERROR! Sumcheck or length fails on received socket 916 block, len=75 (time=24365) 729297 **** ERROR! Sumcheck or length fails on received socket 916 block, len=27 (time=24996) 729344 **** ERROR! Sumcheck or length fails on received socket 916 block, len=27 (time=25096) 729469 **** ERROR! Sumcheck or length fails on received socket 916 block, len=27 (time=25196) 729625 **** ERROR! Sumcheck or length fails on received socket 916 block, len=27 (time=25326) 732063 Error 10053: client socket disconnected at Client: removing (skt=916) TCP 742969 Close signalled to clients 744078 Closing down now ... Memory managed: Offset records: 76 alloc, 76 free Read buffer usage: 110 alloc, 110 free, max in session: 1 Write buffer usage: 2527 alloc, 2527 free, max in session: 1 Total number of received blocks having sumcheck errors = 25 Throughput maximum achieved: 8 frames/sec, 6860 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 76 bytes/sec Average receive rate from "LAPTOP": 0 frames/sec, 30 bytes/sec ********* Log file closed ********* ********* WideClient Log [version 6.75] Class=FS98MAIN ********* Date (dmy): 16/12/07, Time 16:24:02.058: Client name is LAPTOP 411 Attempting to connect now 901 Server = JAMES 1021 Trying TCP/IP host "JAMES" port 8002 ... 1021Okay, IP Address = 192.168.2.5 6609 Connection made okay! 24365 New Client Application: "aiseparation" (Id=2704) 27009 ****** End of session performance summary ****** 27009 Total time connected = 18 seconds 27009 Reception maximum: 0 frames/sec, 0 bytes/sec 27009 Reception average whilst connected: 0 frames/sec, 0 bytes/sec 27009 Transmission maximum: 4 frames/sec, 133 bytes/sec 27009 Transmission average whilst connected: 1 frames/sec, 73 bytes/sec 27009 Max receive buffer = 0, Max send depth = 8, Send frames lost = 0 27009 **************** Individual client application activity **************** 27009 Client 2704 requests: 5 (Ave 0/sec), Data: 280 bytes (15/sec), Average 56 bytes/Process 27009 ********* Log file closed (Buffers: MaxUsed 8, Alloc 45 Freed 45 Refused 0) ********* ********* FSUIPC, Version 3.75 by Pete Dowson ********* Running on Windows Version 5.1 Build 2600 Service Pack 2 Verifying Certificate for "C:\Program Files\Flight Simulator 9\MODULES\FSUIPC.dll" now ... SUCCESS! Signature verifies okay! Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="James White" User Addr="jawhite@indy.rr.com" FSUIPC Key is provided WideFS Key is provided Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=6004B78F[6004B78F] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=255 5453 System time = 16:12:04 5453 C:\Program Files\Flight Simulator 9\ 5453 System time = 16:12:04, FS2004 time = 12:00:00 (00:00Z) 25313 C:\Documents and Settings\ASUS A8V\My Documents\Flight Simulator Files\Cessna Start.flt 25391 AIRCRAFT\c172\RealAirSimulationsC172SP.air 25688 Aircraft="Cessna Skyhawk 172SP Paint2" 37282 C:\Documents and Settings\ASUS A8V\My Documents\Flight Simulator Files\UI generated flight.flt 37828 Clear All Weather requested: external weather discarded 41063 Advanced Weather Interface Enabled 67235 Traffic File #18 = "scenery\world\scenery\traffic" 73188 Traffic File #21 = "scenery\world\scenery\traffic_01_ultimatec550" 73469 Traffic File #20 = "scenery\world\scenery\traffic_01_ultimatec402" 74141 Traffic File #23 = "scenery\world\scenery\traffic_01_ultimateka_f90" 75407 Traffic File #26 = "scenery\world\scenery\traffic_01_ultimatelear45" 279797 Traffic File #22 = "scenery\world\scenery\traffic_01_ultimategulfstream3" 751703 System time = 16:24:30, FS2004 time = 16:23:48 (21:23Z) 751703 *** FSUIPC log file being closed Memory managed: 0 Allocs, 2904 Freed ********* FSUIPC Log file closed ***********
Pete Dowson Posted December 17, 2007 Report Posted December 17, 2007 WideClient connects okay, but when I run a program on the client machine, it thinks FS is not running. I do have checksum errors in the wideserver log Ouch. Those have definitely got to be hardware. I have done everything I can think of. Tested the RAM on the Server? You've tried changing the NIC, but the errors might be further back, into the PC. Anyway, I get a new computer this week, so that I might solve the problem. But then again, it might not... I'm guessing the issue is somewhere in my Server machine based on the fact that I used two separate client machines with no luck. I'd be guessing the same in that case. Sorry, I can't think of anything else to try, excepting possibly trying SPX protocol which will be using a dsifferent buffer system I think. Otherwise you might like to ask Katy Pluta, maybe on the FS2004 Forum here. She's been pretty good at helping me out with network stuff on occasion. Regards Pete
szln6z Posted December 17, 2007 Author Report Posted December 17, 2007 Thanks for the feedback Pete. I'm just going to wait for the new computer and assume that will solve it. But to answer a few of your questions, I did replace the NIC; did not think to test the RAM, will consider that, good idea. Thanks for mentioning Katy; I'll check the other forum. Yeah, thought about trying SPX. This "server" computer will my son's, so a fresh XP install will eventually be in order. My gut feel is that's it's a software issue somewhere (I had a program called Snoopstick installed about 3 weeks ago, and during the uninstall on all 3 of my computers, it trashed TCP/IP; luckily, I found a fix on the Internet that brought everything back to life.... or did it....) James
szln6z Posted December 22, 2007 Author Report Posted December 22, 2007 Update: Net Nanny web filtering software was indeed the cause. So, be aware; however, the fix is easy! Just go into the Net Nanny Admin Tools and go to the Overrides. Set fs9.exe on the server and wideclient.exe on the client to be completely unfiltered. Just wanted to share this. James
Pete Dowson Posted December 31, 2007 Report Posted December 31, 2007 Update:Net Nanny web filtering software was indeed the cause. So, be aware; however, the fix is easy! Just go into the Net Nanny Admin Tools and go to the Overrides. Set fs9.exe on the server and wideclient.exe on the client to be completely unfiltered. Thanks. (Never heard of Net Nanny before -- a type of firewall presumably?) Happy New Year! Pete
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now