WideFS on RedHat 9.0

[TheCrazedLog]

Hey..Im new :D

Im trying to run WideFS on a RedHat 9.0 machine via WINE emulator. Its taken me three days hard work to get as far as I have, so dont tell me its not gonna work. ITS GONNA WORK!!! :D

Everything is installed correctly, as far as I can tell. I start FS on my Xp machine, and then run WideFS. WideFS connects correctly (though it says that it is waiting for connection for about 1/2 a second every say...4 - 5 seconds.

Then I try FSGarmin or FSFlightMax. Both tell me (in different words) that they cannot find the session that FS is running.

The Linux firewall is down. My personal firewall is down. I have recompiled the linux machine to read NTFS volumes. FSFlightmax/FSGarmin have been installed correctly as Remote mode. I am using FSFlightMax remote for FSFlightmax. I have mounted the FS2002 share on my Linux machine using this command:

mount -t smbfs -o username=Anthony,password=(never you mind :D),rw //Anthonys/FS2002 /usr/share/wine-c/FS2002

I know that this has been mounted correctly. I have checked and rechecked, using file editing and renaming.

My network is working correctly. Both machines can access each other and the internet. There are no security barriers that affect their communication as far as I know. The only thing possible would be write protection, and Im confident that has been disabled.

The protocol is TCP/IPv4.

I only really have one conclusion left: Linux uses a program called Samba to access Windows shares. Window shares its file using a protocol called SMB. I suspect the protocol that Samba uses is a bit different, or works in a different way, just enough to throw things out of kilter.

Anyone got any ideas?

Thanks

Anthony

note: Sorry for cross posting..but this does belong both in this forum and in the FSFlightmax/FSGarmin one. I dont know which program is at fault here.

[Pete Dowson]

WideFS connects correctly (though it says that it is waiting for connection for about 1/2 a second every say...4 - 5 seconds.

Check the Log files -- both WideServer and WideClient produce logs. It sounds as if one end is disconnecting. If you don't run any applications at all the Server will reset every so often (adjustable) but it shouldn't be that often. It sounds like there's so other error -- but the log should tell you.

Then I try FSGarmin or FSFlightMax. Both tell me (in different words) that they cannot find the session that FS is running.

Not a good choice to test with I think. I'm not sure about FSGarmin, but most certainly to get FlightMax working on WideFS you need to install it on the FS machine AND a remote version on the client. The remote version is a separate download and install. THEN the latter needs to access all the data in the FS installation in order to build its databases and so forth. It is pretty complicated -- there was a lot of instructions for this on the website. I'm sorry, but I don't have the details myself.

I suspect FSGarmin is in a similar boat.

All this is entirely indepedent of their dealings with WideFS by the way.

FSFlightmax/FSGarmin have been installed correctly as Remote mode. I am using FSFlightMax remote for FSFlightmax.

Ahright. So you have found all that stuff. I think they still need to access FS folders directly and may even need their FS counterparts at least partly if not wholy installed. I hope someone who's got all this working can help you.

Regards,

Pete

[TheCrazedLog]

Ok log files:

Wideserver.log:

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

Using blocksize guide of 4096 bytes

Date (dmy): 17/05/03, Time 13:35:53.257: Server name is ANTHONYS

56021 Auto restart after delayed stoppage!

56021 Initialising server socket now

89980 Restarting service due to total lack of use

239104 Incoming connection Accepted ok (skt=1636)

239184 Connected to computer "Linux" (skt=1636)

240546 Incoming connection Accepted ok (skt=1612)

240666 Connected to computer "Linux" (skt=1612)

241948 Incoming connection Accepted ok (skt=1596)

242068 Connected to computer "Linux" (skt=1596)

243480 Incoming connection Accepted ok (skt=1580)

....

3846001 Closing down now ...

Memory managed: Offset records: 0 alloc, 0 free

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

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

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

Wideclient.log:

********* WideClient.DLL Log [version 5.50] *********

Date (dmy): 17/05/03, Time 14:37:01.048: Client name is Linux

766 Attempting to connect now

781 Connection made okay!

2181 send() failed [0 bytes] after 40 retries, request depth is 42

2219 Ready to try connection again

2231 Attempting to connect now

2243 Connection made okay!

3771 send() failed [0 bytes] after 40 retries, request depth is 42

3808 Ready to try connection again

3818 Attempting to connect now

3831 Connection made okay!

5200 send() failed [0 bytes] after 40 retries, request depth is 42

5245 Ready to try connection again

5256 Attempting to connect now

5268 Connection made okay!

6631 send() failed [0 bytes] after 40 retries, request depth is 42

6668 Ready to try connection again

6678 Attempting to connect now

6691 Connection made okay!

8004 send() failed [0 bytes] after 40 retries, request depth is 42

8046 Ready to try connection again

8056 Attempting to connect now

8068 Connection made okay!

8801 Connection closed by server!

8839 Ready to try connection again

8850 Attempting to connect now

8862 Connection made okay!

8895 send() done [37 bytes] after 22 retries, request depth is 2

10152 send() failed [0 bytes] after 40 retries, request depth is 42

10165 Ready to try connection again

10182 Attempting to connect now

10197 Connection made okay!

10326 New Client Application: "fsflightmax_remote" (Id=11)

11466 send() failed [0 bytes] after 40 retries, request depth is 43

11482 Ready to try connection again

11493 Attempting to connect now

11561 Connection made okay!

12870 send() failed [0 bytes] after 40 retries, request depth is 42

12883 Ready to try connection again

12900 Attempting to connect now

12923 Connection made okay!

14250 send() failed [0 bytes] after 40 retries, request depth is 42

14264 Ready to try connection again

14280 Attempting to connect now

14293 Connection made okay!

15650 send() failed [0 bytes] after 40 retries, request depth is 42

15670 Ready to try connection again

[TheCrazedLog]

Hmm something has chopped off the end of that message. It probably deserved it :D

This is what I was trying to say at the end:

Hmmm well by that it looks that something in between is playing funny buggers. It seems to be getting to the server..just not staying on there long enough...hmmm

Ill just have to sit down and work out what is stuffing it up.

Thanks!

Anthony

[Pete Dowson]

You didn't need to include the whole logs! Since they are so repetitive an extract would have done.

The server isn't receiving the messages from the clients so it times them out and they re-connect each time.

The fact that the client sends are piling up may mean they are being blocked at the client end rather than simply getting lost or discarded at the server. I don't know what would do that except a bad Ethernet card (which I've certainly had on occasion).

Or maybe the emulation software for WinSock2 on the Linux system isn't implementing all the options? The "no coalescing" one comes to mind -- you could try turning that off (add "TCPcoalesce=Yes" to the [Config] section of the WideClient.ini file -- it's an undocumented option. It introduces stutters in TCP/IP because of the Winsock action of waiting and coalescing small blocks into bigger ones).

You could try IPX/SPX as well. It is a lot faster really, just more troublesome on WinNT/XP systems, but better on Win98.

Good luck!

Pete

[TheCrazedLog]

Ahh finally found that dang edit button :)

Ok well after a bit under a week of hard work on this, I am out of ideas. I simply have nothing left to try, so Im asking anyone and everyone: CHUCK IDEAS AT ME!

Ive tried to get IPX working on Linux. OOoooh boy. Talk about an uphill battle. More like a vertical wall but anyway. If someone can tell me how to get IPX going, id be very grateful!

Looking at the logs, it tells me Error 100404 I think it was. Something about "Not supporting that socket." If you want, I can dig the log out again for the precise error message. If it was windows, or a GUI, id have some chance of fixing it. But its command line only for this as far as I can tell...and there my chances plummit close to 0.

[Pete Dowson]

Looking at the logs, it tells me Error 100404 I think it was. Something about "Not supporting that socket." If you want, I can dig the log out again for the precise error message.

The error numbers don't go up that high. Maybe 10040 or 10044? The numbers and their messages are just those returned by Winsock (or, in your case, presumably an emulation of WinSock?). Here's a full list for you (in name order, not number. sorry). Looks like yours was 10044? If so then the Linux implementation of WinSock does not support the facilities needed by WideFS. In case it helps, these are the calls used by WideFS to obtain a socket:

For IPX/SPX (uses SPX, sequential packets)

socket(AF_NS, SOCK_SEQPACKET, NSPROTO_SPX) :

For TCP/IP (uses IP streaming, not UDP)

socket(AF_INET, SOCK_STREAM, 0);

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

The following is a list of possible error codes returned by the WSAGetLastError call, along with their extended explanations. Errors are listed in alphabetical order by error macro. Some error codes defined in Winsock2.h are not returned from any function—these are not included in this topic.

WSAEACCES

(10013)

Permission denied.

An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST).

Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4 SP4 or later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4 SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.

WSAEADDRINUSE

(10048)

Address already in use.

Typically, only one usage of each socket address (protocol/IP address/port) is permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that wasn't closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt(SO_REUSEADDR). Client applications usually need not call bind at all—connect chooses an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is committed. This could happen with a call to another function later, including connect, listen, WSAConnect, or WSAJoinLeaf.

WSAEADDRNOTAVAIL

(10049)

Cannot assign requested address.

The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local machine. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote machine (for example, address or port 0).

WSAEAFNOSUPPORT

(10047)

Address family not supported by protocol family.

An address incompatible with the requested protocol was used. All sockets are created with an associated address family (that is, AF_INET for Internet Protocols) and a generic protocol type (that is, SOCK_STREAM). This error is returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, for example, in sendto.

WSAEALREADY

(10037)

Operation already in progress.

An operation was attempted on a nonblocking socket with an operation already in progress—that is, calling connect a second time on a nonblocking socket that is already connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already been canceled or completed.

WSAECONNABORTED

(10053)

Software caused connection abort.

An established connection was aborted by the software in your host machine, possibly due to a data transmission time-out or protocol error.

WSAECONNREFUSED

(10061)

Connection refused.

No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running.

WSAECONNRESET

(10054)

Connection reset by peer.

An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket.) This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.

WSAEDESTADDRREQ

(10039)

Destination address required.

A required address was omitted from an operation on a socket. For example, this error is returned if sendto is called with the remote address of ADDR_ANY.

WSAEFAULT

(10014)

Bad address.

The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument, which is a SOCKADDR structure, is smaller than the sizeof(SOCKADDR).

WSAEHOSTDOWN

(10064)

Host is down.

A socket operation failed because the destination host is down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT.

WSAEHOSTUNREACH

(10065)

No route to host.

A socket operation was attempted to an unreachable host. See WSAENETUNREACH.

WSAEINPROGRESS

(10036)

Operation now in progress.

A blocking operation is currently executing. Windows Sockets only allows a single blocking operation—per- task or thread—to be outstanding, and if any other function call is made (whether or not it references that or any other socket) the function fails with the WSAEINPROGRESS error.

WSAEINTR

(10004)

Interrupted function call.

A blocking operation was interrupted by a call to WSACancelBlockingCall.

WSAEINVAL

(10022)

Invalid argument.

Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket—for instance, calling accept on a socket that is not listening.

WSAEISCONN

(10056)

Socket is already connected.

A connect request was made on an already-connected socket. Some implementations also return this error if sendto is called on a connected SOCK_DGRAM socket (for SOCK_STREAM sockets, the to parameter in sendto is ignored) although other implementations treat this as a legal occurrence.

WSAEMFILE

(10024)

Too many open files.

Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread.

WSAEMSGSIZE

(10040)

Message too long.

A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram was smaller than the datagram itself.

WSAENETDOWN

(10050)

Network is down.

A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets DLL runs over), the network interface, or the local network itself.

WSAENETRESET

(10052)

Network dropped connection on reset.

The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. It can also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed.

WSAENETUNREACH

(10051)

Network is unreachable.

A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host.

WSAENOBUFS

(10055)

No buffer space available.

An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.

WSAENOPROTOOPT

(10042)

Bad protocol option.

An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.

WSAENOTCONN

(10057)

Socket is not connected.

A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. Any other type of operation might also return this error—for example, setsockopt setting SO_KEEPALIVE if the connection has been reset.

WSAENOTSOCK

(10038)

Socket operation on nonsocket.

An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.

WSAEOPNOTSUPP

(10045)

Operation not supported.

The attempted operation is not supported for the type of object referenced. Usually this occurs when a socket descriptor to a socket that cannot support this operation is trying to accept a connection on a datagram socket.

WSAEPFNOSUPPORT

(10046)

Protocol family not supported.

The protocol family has not been configured into the system or no implementation for it exists. This message has a slightly different meaning from WSAEAFNOSUPPORT. However, it is interchangeable in most cases, and all Windows Sockets functions that return one of these messages also specify WSAEAFNOSUPPORT.

WSAEPROCLIM

(10067)

Too many processes.

A Windows Sockets implementation may have a limit on the number of applications that can use it simultaneously. WSAStartup may fail with this error if the limit has been reached.

WSAEPROTONOSUPPORT

(10043)

Protocol not supported.

The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call requests a SOCK_DGRAM socket, but specifies a stream protocol.

WSAEPROTOTYPE

(10041)

Protocol wrong type for socket.

A protocol was specified in the socket function call that does not support the semantics of the socket type requested. For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM.

WSAESHUTDOWN

(10058)

Cannot send after socket shutdown.

A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving, or both have been discontinued.

WSAESOCKTNOSUPPORT

(10044)

Socket type not supported.

The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all.

WSAETIMEDOUT

(10060)

Connection timed out.

A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.

WSATYPE_NOT_FOUND

(10109)

Class type not found.

The specified class was not found.

WSAEWOULDBLOCK

(10035)

Resource temporarily unavailable.

This error is returned from operations on nonblocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established.

WSAHOST_NOT_FOUND

(11001)

Host not found.

No such host is known. The name is not an official host name or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database.

WSA_INVALID_HANDLE

(OS dependent)

Specified event object handle is invalid.

An application attempts to use an event object, but the specified handle is not valid.

WSA_INVALID_PARAMETER

(OS dependent)

One or more parameters are invalid.

An application used a Windows Sockets function which directly maps to a Win32 function. The Win32 function is indicating a problem with one or more parameters.

WSAINVALIDPROCTABLE

(OS dependent)

Invalid procedure table from service provider.

A service provider returned a bogus procedure table to Ws2_32.dll. (Usually caused by one or more of the function pointers being null.)

WSAINVALIDPROVIDER

(OS dependent)

Invalid service provider version number.

A service provider returned a version number other than 2.0.

WSA_IO_INCOMPLETE

(OS dependent)

Overlapped I/O event object not in signaled state.

The application has tried to determine the status of an overlapped operation which is not yet completed. Applications that use WSAGetOverlappedResult (with the fWait flag set to FALSE) in a polling mode to determine when an overlapped operation has completed, get this error code until the operation is complete.

WSA_IO_PENDING

(OS dependent)

Overlapped operations will complete later.

The application has initiated an overlapped operation that cannot be completed immediately. A completion indication will be given later when the operation has been completed.

WSA_NOT_ENOUGH_MEMORY

(OS dependent)

Insufficient memory available.

An application used a Windows Sockets function that directly maps to a Win32 function. The Win32 function is indicating a lack of required memory resources.

WSANOTINITIALISED

(10093)

Successful WSAStartup not yet performed.

Either the application hasn't called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times.

WSANO_DATA

(11004)

Valid name, no data record of requested type.

The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable.

WSANO_RECOVERY

(11003)

This is a nonrecoverable error.

This indicates some sort of nonrecoverable error occurred during a database lookup. This may be because the database files (for example, BSD-compatible HOSTS, SERVICES, or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error.

WSAPROVIDERFAILEDINIT

(OS dependent)

Unable to initialize a service provider.

Either a service provider's DLL could not be loaded (LoadLibrary failed) or the provider's WSPStartup/NSPStartup function failed.

WSASYSCALLFAILURE

(OS dependent)

System call failure.

Returned when a system call that should never fail does. For example, if a call to WaitForMultipleObjects fails or one of the registry functions fails trying to manipulate the protocol/name space catalogs.

WSASYSNOTREADY

(10091)

Network subsystem is unavailable.

This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. Users should check:

That the appropriate Windows Sockets DLL file is in the current path.

That they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one Winsock DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded.

The Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly.

WSATRY_AGAIN

(11002)

Nonauthoritative host not found.

This is usually a temporary error during host name resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful.

WSAVERNOTSUPPORTED

(10092)

Winsock.dll version out of range.

The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Check that no old Windows Sockets DLL files are being accessed.

WSAEDISCON

(10101)

Graceful shutdown in progress.

Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence.

WSA_OPERATION_ABORTED

(OS dependent)

Overlapped operation aborted.

An overlapped operation was canceled due to the closure of the socket, or the execution of the SIO_FLUSH command in WSAIoctl.

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

Hope this helps,

Pete

[TheCrazedLog]

(10044)

Socket type not supported.

The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all.

Thats the one. It both helps and doesnt help.

Hmm...thanks anyway!

Anthony