IPX/SPX client

[fredP]

My complement Peter,

I connected wideFS not over a direct network but over my internet connection. OK the TCP/IP did not function might have been my firewall etc but with the IPX/SPX client. I tried out the FS flight keeper and connected from both computers with SB to VATSIM. Now the fun has just started.

Thank's

Fred.

[Pete Dowson]

I connected wideFS not over a direct network but over my internet connection. OK the TCP/IP did not function might have been my firewall etc but with the IPX/SPX client. I tried out the FS flight keeper and connected from both computers with SB to VATSIM.

Interesting way to do it. I wasn't aware that IPX/SPX could be used over the Internet. I suppose something must be putting an IP wrapper around it? How do you sort the addressing out -- for IPX/SPX I don't give an IP address or server name, there's no place for them, only for the local network number and network adapter's MAC address (=serverNode). Hmm.

Regards,

Pete

[fredP]

Hello Peter,

Here are my settings and the widefs.dll . I see some settings have changed but in the client I still have Use TCPIP=no . I did not manage to connect with TCPIP but after I changed the client to useTCP=No and wrote in the client ServerNode=35491.7538.0.0.XXX it connected up imediatly.Could it be that after connecting up with the IPX/SPX server node that it uses both server and client names to connect. As I did not write in these names or the IP address of the sever in the client config. Please do not look at the frame rates etc as this was just a test I had other programs email etc running at the time.

(The X's are to cover up IP addresses etc

From Server

[Config]

Port=8002

SeverIPAddr=192.168.2.XXX

AutoRestart=0

AutoUpdateTime=13

MaximumBlock=4096

NoStoppedRestarts=Yes

RestartTime=10

SendTimeout=15

TCPcoalesce=No

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

[user]

Log=Errors+

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

[ClientNames]

1=RON-QHO8QG6I9XX

From Client

[Config]

Port=8002

ServerNode=35491.7538.0.0.XXX

Window=4,4,808,580

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

PollInterval=2000

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

UseTCPIP=No

WaitForNewData=500

MaxSendQ=100

WhenMaxSendQ=Recon

SendScanTime=10

Priority=3,1,2

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

[user]

Log=Errors+

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

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 02/01/05, Time 14:14:07.899: Server name is FRED

39978 Initialising TCP/IP server

40068 Initialising IPX/SPX server

40108 ServerNode=35491.7538.0.0.256

51194 Restarting service due to total lack of use

52496 Incoming connection Accepted ok (skt=520)

52506 Connected to computer "RON-QHO8QG6I9XX" (skt=520)

92664 Incoming connection Accepted ok (skt=336)

441665 Connected to computer "RON-QHO8QG6I9XX" (skt=336)

478438 Incoming connection Accepted ok (skt=432)

723681 Connected to computer "RON-QHO8QG6I9XX" (skt=432)

743970 Incoming connection Accepted ok (skt=3876)

885924 Connected to computer "RON-QHO8QG6I9XX" (skt=3876)

904211 Incoming connection Accepted ok (skt=3784)

1034318 Connected to computer "RON-QHO8QG6I9XX" (skt=3784)

1054607 Incoming connection Accepted ok (skt=3844)

1191093 Connected to computer "RON-QHO8QG6I9XX" (skt=3844)

1209870 Incoming connection Accepted ok (skt=3776)

1312788 Client socket unused for too long: removing (skt=520)

1312798 Client socket unused for too long: removing (skt=336)

1312798 Client socket unused for too long: removing (skt=432)

1312798 Client socket unused for too long: removing (skt=3876)

1312798 Client socket unused for too long: removing (skt=3784)

1312798 Client socket unused for too long: removing (skt=3844)

1312798 Client socket unused for too long: removing (skt=3776)

1312868 Incoming connection Accepted ok (skt=3800)

1341169 Connected to computer "RON-QHO8QG6I9XX" (skt=3800)

1363080 Incoming connection Accepted ok (skt=3792)

1511804 Connected to computer "RON-QHO8QG6I9XX" (skt=3792)

1533445 Incoming connection Accepted ok (skt=3732)

1681628 Connected to computer "RON-QHO8QG6I9XX" (skt=3732)

1703900 Incoming connection Accepted ok (skt=3836)

1860345 Connected to computer "RON-QHO8QG6I9XX" (skt=3836)

1879173 Incoming connection Accepted ok (skt=3692)

2006476 Connected to computer "RON-QHO8QG6I9XX" (skt=3692)

2029489 Incoming connection Accepted ok (skt=3896)

2190881 Connected to computer "RON-QHO8QG6I9XX" (skt=3896)

2209888 Incoming connection Accepted ok (skt=3880)

2344001 Connected to computer "RON-QHO8QG6I9XX" (skt=3880)

2365342 Incoming connection Accepted ok (skt=3936)

2510961 Connected to computer "RON-QHO8QG6I9XX" (skt=3936)

2530639 Incoming connection Accepted ok (skt=5388)

2667216 Connected to computer "RON-QHO8QG6I9XX" (skt=5388)

2685993 Incoming connection Accepted ok (skt=5700)

2807387 Connected to computer "RON-QHO8QG6I9XX" (skt=5700)

2826214 Incoming connection Accepted ok (skt=5720)

2957623 Connected to computer "RON-QHO8QG6I9XX" (skt=5720)

2976611 Incoming connection Accepted ok (skt=5732)

3107969 Connected to computer "RON-QHO8QG6I9XX" (skt=5732)

3126957 Incoming connection Accepted ok (skt=5744)

3258676 Connected to computer "RON-QHO8QG6I9XX" (skt=5744)

3277303 Incoming connection Accepted ok (skt=5768)

3406148 Connected to computer "RON-QHO8QG6I9QZ" (skt=5768)

3427649 Incoming connection Accepted ok (skt=5776)

3577104 Connected to computer "RON-QHO8QG6I9XX" (skt=5776)

3597864 Incoming connection Accepted ok (skt=5796)

3743143 Connected to computer "RON-QHO8QG6I9XX" (skt=5796)

3763182 Incoming connection Accepted ok (skt=5808)

3904234 Connected to computer "RON-QHO8QG6I9XX" (skt=5808)

3923542 Incoming connection Accepted ok (skt=5440)

4057815 Connected to computer "RON-QHO8QG6I9XX" (skt=5440)

4078835 Incoming connection Accepted ok (skt=6760)

4220679 Connected to computer "RON-QHO8QG6I9XX" (skt=6760)

4239196 Incoming connection Accepted ok (skt=5988)

4779863 Incoming connection Accepted ok (skt=7896)

4779924 Connected to computer "RON-QHO8QG6I9XX" (skt=7896)

4819941 Incoming connection Accepted ok (skt=7764)

4833611 Connected to computer "RON-QHO8QG6I9XX" (skt=7764)

5318318 Client socket unused for too long: removing (skt=3800)

5318418 Client socket unused for too long: removing (skt=3792)

5318428 Client socket unused for too long: removing (skt=3732)

5318428 Client socket unused for too long: removing (skt=3836)

5318468 Client socket unused for too long: removing (skt=3692)

5318468 Client socket unused for too long: removing (skt=3896)

5318488 Client socket unused for too long: removing (skt=3880)

5318558 Client socket unused for too long: removing (skt=3936)

6801721 Client socket unused for too long: removing (skt=5388)

6801731 Client socket unused for too long: removing (skt=5700)

6801731 Client socket unused for too long: removing (skt=5720)

6801741 Client socket unused for too long: removing (skt=5732)

6801761 Client socket unused for too long: removing (skt=5744)

6801761 Client socket unused for too long: removing (skt=5768)

6801781 Client socket unused for too long: removing (skt=5776)

6801781 Client socket unused for too long: removing (skt=5796)

6801781 Client socket unused for too long: removing (skt=5808)

6801781 Client socket unused for too long: removing (skt=5440)

6801801 Client socket unused for too long: removing (skt=6760)

6801811 Client socket unused for too long: removing (skt=5988)

6801821 Client socket unused for too long: removing (skt=7896)

13585956 Closing down now ...

Memory managed: Offset records: 168 alloc, 168 free

Internal LAN buffers, maximum used: 1, refused: 0

Throughput maximum achieved: 36 frames/sec, 3224 bytes/sec

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

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

[Pete Dowson]

... after I changed the client to useTCP=No and wrote in the client ServerNode=35491.7538.0.0.XXX it connected up imediatly.

That's a very odd "ServerNode". The first two numbers are the "Network Number" and the last three the MAC address -- theoretically at least. The MAC address is the actual hardware identity of a Network Interface Card.

It looks like you have something installed which is converting that non-hardware Server Node addressing into something for the Internet connection and wrapping the data for the internet. Weird.

This is all a bit beyond me I'm afraid.

Is this on WinXP? Try running "IPXROUTE config" from a DOS window and see what get's listed. Check the section in the current WideFS document entitled 2. Server Node may need specifying for IPX/SPX.

I'd be most interested to see what IPXROUTE says. Every case so far of an incorrect Server Node, the one reported has actually been this one:

13330.61389.0.0.512

which appears to be some sort of Loopback Adapter installed by XP. The current WideServer implementation looks for this one specifically and runs IPXROUTE itself to find the "true" local server node.

Regards,

Pete

[fredP]

Hi Peter,

This is from the server computer

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:\Dokumente und Einstellungen\Fred>IPXROUTE config

NWLink IPX-Routing- und Quellrouting-Steuerungsprogramm v2.00

Num Name Netzwerk Knoten Rahmen

================================================================

0. Internal a38a721d 000000000001 [None ]

1. IpxLoopbackAdapter a38a721d 000000000002 [802.2]

2. LAN-Verbindung 00000000 0030847acf89 [802.2]

3. NDISWANIPX 00000000 f8b920524153 [EthII] -

Legende

=======

- inaktive WAN-Leitung

and from the client computer

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Ron>IPXROUTE config

NWLink IPX Routing and Source Routing Control Program v2.00

Num Name Network Node Frame

================================================================

1. IpxLoopbackAdapter 1234cdef 000000000002 [802.2]

2. Local Area Connection 2 00000000 000854131900 [802.2]

3. NDISWANIPX 00000000 06fb20524153 [EthII] -

Legend

======

- down wan line

C:\Documents and Settings\Ron>

I Have XP home as Server and XP pro as client.

But I cannot complain as everything works for some reason perfect.

Fred.

[Pete Dowson]

0. Internal a38a721d 000000000001 [None ]

1. IpxLoopbackAdapter a38a721d 000000000002 [802.2]

2. LAN-Verbindung 00000000 0030847acf89 [802.2]

3. NDISWANIPX 00000000 f8b920524153 [EthII]

Okay. Somehow, something extra is installed on your system. The "Internal" entry doesn't appear on any of my XP PCs at all.

Both the Internal and Loopback Adapter entries have the same strange Network Number, but this is not the same one as I and others get for the "Loopback Adapter", which is interesting. The value "a38a721d" gives you your 35491.7538 (hex 8AA3 and 1D72 respectively).

The correct ServerNode which would give you a direct connection to the Server in IPX/SPX mode is the "LAN" one:

00000000 0030847acf89

which would have provided:

ServerNode=0.0.12288.31364.35279

At present, in WideServer 6.44, I only run IPXROUTE to get the list when the ServerNode Windows gives me is the one I knew about as "LoopBack Adapter" (13330.61389.0.0.512). It looks like I should run it whenever the Network Number provided is something non-zero.

I am making some small changes to WideFS at present, so maybe i can send you a version to try in due course.

and from the client computer

1. IpxLoopbackAdapter 1234cdef 000000000002 [802.2]

2. Local Area Connection 2 00000000 000854131900 [802.2]

3. NDISWANIPX 00000000 06fb20524153 [EthII] -

Yes, this is like all the others I've seen. If this had been your Server, WideServer would have run IPXROUTE for you and obtained the Local Area Connect 2 entry as correct.

But I cannot complain as everything works for some reason perfect.

Trouble is I don't like things I don't understand. I can only guess that the extra "Internal" entry you have on the Server is somehow doing this. It couldn't be Internet Connection Sharing, could it? Or do you have something special installed on the Server?

Regards,

Pete

[fredP]

Hello Peter,

It couldn't be Internet Connection Sharing, could it?

I have a SMC Barricade WLAN router. The two computers are connected to the WLAN router with the network cable interface I have only a notebook connected by wireless at the moment to the router. I have another computer that I will test with WLAN and WideFS as soon as I have a bit of time. If you want to send me any WideFS versions to me to try out please feel welcome to do so and tell me the tests you would like me to carry out for you.

Thanks again

Fred.P

[Pete Dowson]

I have a SMC Barricade WLAN router. The two computers are connected to the WLAN router with the network cable interface

Hmmm. I use a router too, but it doesn't add that "Internal" entry in IPXROUTE's list. Strange. Something is obviously installed in that PC which isn't on any of the others I've met.

Never mind. I am changing WideServer so that it will list the alternative ServerNodes in the Log. The correct one, normally, for IPX/SPX links from clients wil be the "LAN" connection one, generally with a Network Number of 0.

If you want to send me any WideFS versions to me to try out please feel welcome to do so and tell me the tests you would like me to carry out for you.

I don't need to actually send you a test version because you've already run IPXRoute and shown the results. The only test which would be useful, please, is if you could put the ServerNode I decoded for you into your Client INI (just put a ';' in front of the current line so it is easy to re-instate afterwards). i.e.

ServerNode=0.0.12288.31364.35279

If that works then I know I'll be listing the right ones when I do issue the next WideFS update.

Thanks!

Pete

[fredP]

Hello Peter,

I have tried out what you wanted

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

Date (dmy): 06/01/05, Time 09:31:03.113: Client name is RON-QHO8QG6I9QZ

61 Attempting to connect now

91 Trying IPX/SPX on Port 8002, Node 0.0.12288.31364.35279 ...

91 Connection made okay!

With the node from my server

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

Date (dmy): 06/01/05, Time 09:37:17.638: Client name is RON-QHO8QG6I9QZ

1232 Attempting to connect now

1312 Trying IPX/SPX on Port 8002, Node 35491.7538.0.0.256 ...

1382 Connection made okay!

I hope that has helped you.

Fred.

[Pete Dowson]

I hope that has helped you.

Yes, thank you! My deductions were correct in respect of the list of "routes" in IPXROUTES. I shall go ahead with the changes to WideServer so that they will be listed in cases like your Server too.

Thanks again. I will be releasing an interim Beta (6.442), for both WideServer and WideClient, later today. I'll put them as an attachment to an Announcement, above, if you would like to try them. Full details will be included.

Regards,

Pete

[fredP]

Thats fine by me as I am at home today so I have time to try it out. Some software companys would be proud if they had a help desk suport forum as good and as fast as yours Peter.

Thanks

Fred.