Widefs Error Connection using Wideclient p8R (FMCA) software

[pat2807]

Hi Peter,

I'm trying to use Widefs with the FMCA Software by P8R Group. From a client PC with Wideclient running I have this error conenction found in LOG File:

********* WideServer.DLL Log [version 6.71] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 16/12/06, Time 16:41:57.718: Server name is EMILIO-ARFXKHD9

487672 Initialising TCP/IP server

487859 Initialising IPX/SPX server

487859 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family

487859 Failed to start IPX/SPX Server

487859 Initialising UDP/IP server

488156 Broadcasting service every 1000 mSecs

499031 Restarting service due to total lack of use

499047 Failed to start IPX/SPX Server

8847219 Incoming connection Accepted ok (skt=3496) TCP

8847594 Connected to computer "KT-HAU11R2HXKPP" running WideClient version 6.710 (skt=3496) TCP

8847609 Auto send stopped before sending all data (0 of 359 sent), Error=10038 (skt=3496) TCP

8849703 Auto send stopped before sending all data (0 of 266 sent), Error=10038 (skt=3496) TCP

..........

Can you help me?

Thanks

Emilio.

[Pete Dowson]

I'm trying to use Widefs with the FMCA Software by P8R Group. From a client PC with Wideclient running I have this error conenction found in LOG File:

...

8847609 Auto send stopped before sending all data (0 of 359 sent), Error=10038 (skt=3496) TCP

8849703 Auto send stopped before sending all data (0 of 266 sent), Error=10038 (skt=3496) TCP

Looks like it is being blocked.

Where's the Client Log? There are always two ends to a connection.

Regards

Pete

[pat2807]

Hi Peter,

thank you. I try again and I attach log files. I'm waiting for helping.

Thanks

LOG Files.zip

LOG Files.zip

[Pete Dowson]

thank you. I try again and I attach log files. I'm waiting for helping.

Hmm. I'm afraid all the logs show is that the communication between the two PCs is being blocked by something. I don't know if this is some firewall settings on one or the other, and I cannot really solve Network problems remotely. I think you need to sort out your firewalls and get the Network fully operational, then try again.

Regards

Pete

[pat2807]

Hi Pete,

I just supposed your think, infact I deactivated Xp firewalls on both Pcs, but nothing. I have tried another test, i.e. I start FS9 on notebbok and I connected Wideclient from Desktop. In this way the p8r software runs fine. Now I try to understand where is the difference of Lan connections betwenn two PCs. I have another suspect. In the desktop is installed also FSX, but when I tested this didn't run. Boh!!!!

I wrote also to development team of p8r software. I'm waiting for some help.

If I will be able to remove problem i will inform you.

Thanks.

Bye, Emilio.

[Pete Dowson]

I deactivated Xp firewalls on both Pcs, but nothing.

Something else is wrong then.

I have tried another test, i.e. I start FS9 on notebbok and I connected Wideclient from Desktop. In this way the p8r software runs fine.

Well, it it the Client which connects TO the Server, so perhaps this shows the blockage is on the Desktop. something is getting in the way, for sure.

I have another suspect. In the desktop is installed also FSX, but when I tested this didn't run. Boh!!!!

FSX didn't run at all?

I'm wondering if something in your Network Settings on the desktop are wrong. maybe uninstalling and re-installing your Network card & drivers would sort something out?

If I will be able to remove problem i will inform you.

Yes, please tell me what happens. I'd like to know what the problem turns out to be!

Regards

Pete

[pat2807]

Hi Pete,

thanks for your suggestions, but while you answered me i did a systematic test about only your widefs without any other software. I registered LOG and INI files during my test steps on both directions.

I attach a zip file containing the dumped files. I would like that you will see these because I think that probably you can find the problem.

I thank you again for your courtesy, but I think that these items will be useful also for you.

Emilio

LOG Files.zip

[Pete Dowson]

I registered LOG and INI files during my test steps on both directions.

INI files don't change in any interesting ways. They only record defaults. Unless you change them. Do you? It doesn't look like it.

The logs don't show anything different. Sorry.

Regards

Pete

[pat2807]

Hi Pete,

excuse me but I noted that in the log file from notebook to desktop a connection and soon after a disconnection for time out, therefore for a short time the connection is on than goes in off for time out.

--------------------------------------------------------------------------------

Attempting to connect now

891 Server = EMILIO-ARFXKHD9

951 Trying TCP/IP host "EMILIO-ARFXKHD9" port 8002 ...

951Okay, IP Address = 192.168.1.10

4466 Connection made okay! <<<<<----------------------

40698 Timed out response: connection assumed lost! <<<<---------

40698 Ready to try connection again

-------------------------------------------------------------------------------

after repeat ever the same cycle!!!!!!

If it is problem of networking probably it could not possible to activate a short time connection, infact the notebook would not connect at all!!!!

What does mean ? Perhaps is it possible to modify some parameter in order to mantain ever the connection?

In technical documentation i read that it's possible to activate a detailed dumping. Do you think that it can help in some way?

Thanks

[Pete Dowson]

excuse me but I noted that in the log file from notebook to desktop a connection and soon after a disconnection for time out, therefore for a short time the connection is on than goes in off for time out./quote]

But you have to look at both ends -- look at the Server log.

If it is problem of networking probably it could not possible to activate a short time connection, infact the notebook would not connect at all!!!!

It is most certainly a Networking problem, because there is nothing else that WideFs is doing which is going wrong.

If it isn't being blocked it most certainly isn't working correctly, and I'm afraid I am not enough of a Networking expert to diagnose it from here. Have you been through all of the hints in the documentation I provide? They have been collected over the years from user's submissions -- i.e. from practical results. The documentation embodies ALL I know about networking, and some things I don't know.

It may even be a driver or hardware fault, so re-installing or swapping things over may show things differently. I myself have had three Network cards go faulty over the years, and the symptoms they gave were similar -- messages blocking, sumcheck errors, timeouts.

Check all the settings. If you want more advice on Networks you may find that Katy Pluta, on the FS2004 Forum, can help -- I've often had to ask her myself.

If I was in your position I would be using a trial and error approach, trying each thing in turn till I found out what was causing the problem. One of the first things to do is see if there are any other processes running which may interfere with networking.

What does mean ? Perhaps is it possible to modify some parameter in order to mantain ever the connection?

In technical documentation i read that it's possible to activate a detailed dumping. Do you think that it can help in some way?

You can set "Log=DebugAll" in both INI files and generate very large logs, but you won't get any more details about the errors that are occurring, simply because if errors occur they are logged anyway. It may help to see the context in which they do occur. But if you do this, keep things very short or the logs will be too large to plough through!

Regards

Pete