Wide Client Does Not Connect

[Chazrt22]

I have been using WideClient for years. All of a sudden it doesn't connect. Below are various log entries.

Any recommendations?

Thanks,

Chaz

; PLEASE SEE the documentation for parameter details

; ==================================================

[Config]

Port=8002

AdvertiseService=1

AutoRestart=0

AutoUpdateTime=13

MaximumBlock=4096

NoStoppedRestarts=Yes

Port2=9002

RestartTime=10

SendTimeout=15

TCPcoalesce=No

; -----------------------------------------------

[user]

Log=Errors+

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 01/12/11, Time 09:43:04.484: Server name is FLIGHT-DECK

61578 Initialising TCP/IP server

61641 Initialising IPX/SPX server

61703 ServerNode=0.0.5120.17698.31759

61703 Initialising UDP/IP server

62078 Broadcasting service every 1000 mSecs

72922 Restarting service due to total lack of use

221594 Closing down now ...

Memory managed: Offset records: 0 alloc, 0 free

Read buffer usage: 0 alloc, 0 free, max in session: 0

Write buffer usage: 0 alloc, 0 free, max in session: 0

Throughput maximum achieved: 0 frames/sec, 0 bytes/sec

Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec

********* Log file closed *********

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 01/12/11, Time 09:10:03.312: Server name is FLIGHT-DECK

24359 Initialising TCP/IP server

24391 Initialising IPX/SPX server

24406 ServerNode=0.0.5120.17698.31759

24406 Initialising UDP/IP server

26125 Broadcasting service every 1000 mSecs

35672 Restarting service due to total lack of use

; PLEASE SEE WideFS documentation for parameter details

; =====================================================

[Config]

ServerName=flight-deck

Protocol=TCP

Port=8002

Window=4,4,1032,746

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

MailslotTiming=2000,1000

PollInterval=2000

Port2=9002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

********* WideClient Log [version 6.72] Class=FS98MAIN *********

Date (dmy): 01/12/11, Time 09:46:14.140: Client name is DOWNLOADPC

406 Attempting to connect now

500 Trying TCP/IP host "flight-deck" port 8002 ...

500 ... Okay, IP Address = 72.3.199.16

9703 ****** End of session performance summary ******

9703 Total time connected = 0 seconds

9703 Reception maximum: 0 frames/sec, 0 bytes/sec

9703 Transmission maximum: 0 frames/sec, 0 bytes/sec

9703 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

9703 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

********* WideClient Log [version 6.72] Class=FS98MAIN *********

Date (dmy): 01/12/11, Time 09:11:35.165: Client name is DOWNLOADPC

468 Attempting to connect now

546 Trying TCP/IP host "flight-deck" port 8002 ...

546 ... Okay, IP Address = 72.3.199.16

7500 ****** End of session performance summary ******

7500 Total time connected = 0 seconds

7500 Reception maximum: 0 frames/sec, 0 bytes/sec

7500 Transmission maximum: 0 frames/sec, 0 bytes/sec

7500 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

7500 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

[Pete Dowson]

I have been using WideClient for years. All of a sudden it doesn't connect.

All of a sudden without any changes made to your system at all?

********* WideClient Log [version 6.72] Class=FS98MAIN *********

First off, your WideClient is out of date. Minimum supported is 6.86, and there's a 6.90 available which gives much improved UDP performance with FSUIPC 4.749 if you use BroadcastMode.

Second, the IP address being returned by Windows for your Server looks wrong:

500 Trying TCP/IP host "flight-deck" port 8002 ...

500 ... Okay, IP Address = 72.3.199.16

According to an IP search that turns out to be:

Hostname: 72.3.199.16 ISP: Rackspace Hosting

Country: United States

State/Region: California

City: San Francisco

Postal Code: 94103

Seems like your router is doing this? There are mentions of this sort of behaviour in the FAQ subforum thread "WideFS Server names translating into incorrect IP addresses".

I assume you are either using an old version of Windows on your client, or for some reason are using differently named Workgroups, because otherwise you'd be better off removing bother ServerName and Protocol out of your WideClient INI file and letting WideFS sort itself out automatically.

Regards

Pete

[Chazrt22]

Pete,

I got it working by adding the IP address and Protocol = TCP.

Appreciate the info you provided.

Cheers!

Chaz