Junji Posted March 12, 2005 Report Posted March 12, 2005 Hi Peter When I run a wideClient on any clientPC, "1 connected" is displayed on my title bar of FS2004. It's normal. Then I run another WideClient on any another client PC, but the display does not cout up (stay as "1 connected"). Though, this WideClient is working normally. After that, the display counts up 2,3,4 when I run another WideClients one by one. Something is wrong?? One more problem occurs in WIdeFS.. Blue screen sometimes appears on a cliet PC displaying "A fatal exception 0E has occured.......VXD WSIPX(01)....", and WideClient quits. To my surprise, after restarting WideClient, it works normally. WIDECLIENT0.LOG was as followings. Do some conflicts exist on IPX ?? Do you think these two problems are linked? I'm so sorry to bother you, but do you have any suggestions?? best regards Junji Hirayama http://hira-yama.com (Project J) ********* WideClient Log [version 6.47] Class=FS98MAIN ********* Date (dmy): 12/03/05, Time 01:44:26.010: Client name is P-350 110 Attempting to connect now 171 Trying IPX/SPX on Port 8002, Node 0.0.15650.5340.35337 ... 188 Connection made okay! 21228 New Client Application: "CDU" (Id=-312299) 59801 New Client Application: "PFD" (Id=-362451) 1353403 Connection closed by server! 1353418 Ready to try connection again 1353451 Attempting to connect now 1353451 Trying IPX/SPX on Port 8002, Node 0.0.15650.5340.35337 ... 1363901 Error on client pre-Connection Select() [Error=10061] Connection refused 1363936 Ready to try connection again 1363941 Attempting to connect now 1363941 Trying IPX/SPX on Port 8002, Node 0.0.15650.5340.35337 ... 1537046 Connection made okay! 1646128 Connection closed by server! 1646183 Ready to try connection again 1646185 Attempting to connect now 1646185 Trying IPX/SPX on Port 8002, Node 0.0.15650.5340.35337 ... 2492925 Connection made okay! 2835152 Connection closed by server! 2835161 Ready to try connection again 2835166 Attempting to connect now 2835166 Trying IPX/SPX on Port 8002, Node 0.0.15650.5340.35337 ... 3094846 WRITESTATEDATA received with bad data size! 3094846 0 ReadLocal: Offset=4BB5BF0, Size=107D4 3100965 Trying IPX/SPX on Port 8002, Node 0.0.15650.5340.35337 ...
Pete Dowson Posted March 12, 2005 Report Posted March 12, 2005 When I run a wideClient on any clientPC, "1 connected" is displayed on my title bar of FS2004. It's normal. Then I run another WideClient on any another client PC, but the display does not cout up (stay as "1 connected"). Though, this WideClient is working normally. Check the WideServer log. Each time a "connected" is shown, the count is increased. Likewise it is decreased on a disconnect. One more problem occurs in WIdeFS..Blue screen sometimes appears on a cliet PC displaying "A fatal exception 0E has occured.......VXD WSIPX(01)....", and WideClient quits. That is most certainly a problem with your Network drivers for IPX/SPX. There's no way WideFS can force such an error. Do some conflicts exist on IPX ?? Not for the 6 or so years WideFS has been using IPX/SPX successfully, no. The actual code to drive the network is straight out of Microsoft examples and is unchanged for many years. Do you think these two problems are linked? I doubt if the first is really a problem, but it is impossible to say because there's no information. You need to look in the WideServer Log. I'm so sorry to bother you, but do you have any suggestions?? Re-install the Network adapter on the Client giving problems. Look for better drivers. Check cables, hubs/switches. Try TCP/IP. Try updates to Windows, especially try Windows XP. Regards Pete
Junji Posted March 13, 2005 Author Report Posted March 13, 2005 Hi Peter Thank you very much for your reply. Some errors were in the WideserverLOG like this. --------------------------------------- 3512750 Retried 20 times: sends blocked for over 5 secs! (0 of 457 sent), Error=10035 (skt=380) 3514593 Send ok but needed 7 attempts! (441 of 441 sent) (skt=380) 3652000 Retried 20 times: sends blocked for over 5 secs! (0 of 336 sent), Error=10035 (skt=3888) 3657218 Retried 20 times: sends blocked for over 5 secs! (0 of 345 sent), Error=10035 (skt=3888) 3662203 Error 10035: sends blocked for too long! Removing client (skt=3888) --------------------------------------- My main PC for FS2004 is WindowsXP, and another clients are Windows98SE. Anyway, I'll check WideserverLOG in some conditions. And also I'll test TCP/IP (I have never tested). Thank you. Junji Hirayama
Pete Dowson Posted March 13, 2005 Report Posted March 13, 2005 Some errors were in the WideserverLOG like this. --------------------------------------- 3512750 Retried 20 times: sends blocked for over 5 secs! (0 of 457 sent), Error=10035 (skt=380) 3514593 Send ok but needed 7 attempts! (441 of 441 sent) (skt=380) 3652000 Retried 20 times: sends blocked for over 5 secs! (0 of 336 sent), Error=10035 (skt=3888) 3657218 Retried 20 times: sends blocked for over 5 secs! (0 of 345 sent), Error=10035 (skt=3888) 3662203 Error 10035: sends blocked for too long! Removing client (skt=3888) These won't account for an incorrect number of corrections shown. But they are worse, they are indications of problems which will cause jerky behavior on the affected clients. My main PC for FS2004 is WindowsXP, and another clients are Windows98SE. Until recently, in such a mixed system, I would certainly advise using TCP/IP not IPX/SPX, which gave me problems for a long time when mixing an XP server with Win98SE clients. However, using WinXP SP1 or SP2 I've had no problems. Are you using the original XP or SP1 or SP2? In any case, it sounds as if you have one suspect client. It will take a process of elimination to determine what is actually wrong with it. Regards, 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