zepingouin

You've got the idea. This is mainly use by clients over the network to find and send requests to their respective servers. You'll find many explanations with Google. Regards Gerard

Oops, my mistake. It is the Broadcast Address for the subnet. My previous network was using 255.255.240.0 as subnet mask, hence the 192.168.15.255 broadcast address.

Hello Pete, 192.168.15.255 is a subnet mask. BTW, this pointed a discrepancy between PC's. A long time ago, I switched ADER to a fix IP address instead of using DHCP. I have a local DHCP server (and other services as well) running in a Linux box. This DHCP server allocates always the same specific address by looking at the MAC address. So, 192.168.2.7 was correct but not the subnet mask. Now, both PC's have 192.168.2.255 as subnet mask. I tried again without the ServerName parameter but no luck. This was not the problem. You say that Mailslot Protocol should use port 9002 instead of 138. I guess I have to find why this not the case. I used default INI files without modification, exception of ServerName and Protocol. ; 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+ ; =============================================== [ClientNames] 1=ROENTGEN ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] Port=8002 Window=43,44,886,589 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 ServerName=Ader Protocol=TCP ; ----------------------------------------------- [User] Log=Errors+ ; =============================================== Regards Gerard

Hello Pete, I added the following lines into WideClient.ini [Config] and the connection is working :) ServerName=Ader Protocol=TCP WideClient FS98 Eliminator - Connected ********* WideClient Log [version 6.78] Class=FS98MAIN ********* Date (dmy): 21/10/10, Time 21:01:38.613: Client name is ROENTGEN 156 Attempting to connect now 156 Trying TCP/IP host "Ader" port 8002 ... 156 ... Okay, IP Address = 192.168.2.7 172 Connection made okay! 145187 ****** End of session performance summary ****** 145187 Total time connected = 145 seconds 145187 Reception maximum: 2 frames/sec, 182 bytes/sec 145187 Reception average whilst connected: 1 frames/sec, 60 bytes/sec 145187 Transmission maximum: 0 frames/sec, 96 bytes/sec 145187 Transmission average whilst connected: 0 frames/sec, 19 bytes/sec 145187 Max receive buffer = 362, Max send depth = 1, Send frames lost = 0 145187 ********* Log file closed (Buffers: MaxUsed 1, Alloc 357 Freed 357 Refused 0) ********* ********* WideServer.DLL Log [version 6.78] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 21/10/10, Time 21:00:09.989: Server name is ADER 81968 Initialising TCP/IP server 81984 Initialising IPX/SPX server 81984 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 81984 Failed to start IPX/SPX Server 81984 Initialising UDP/IP server 82281 Broadcasting service every 1000 mSecs 88859 Incoming connection Accepted ok (skt=364) TCP 89140 Connected to computer "ROENTGEN" running WideClient version 6.780 (skt=364) TCP 234234 Error 10053: client socket disconnected at Client: removing (skt=364) TCP 405968 Close signalled to clients 407062 Closing down now ... Memory managed: Offset records: 15 alloc, 15 free Read buffer usage: 66 alloc, 66 free, max in session: 1 Write buffer usage: 15253 alloc, 15253 free, max in session: 1 Throughput maximum achieved: 2 frames/sec, 190 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 10 bytes/sec Average receive rate from "ROENTGEN": 0 frames/sec, 8 bytes/sec ********* Log file closed ********* Although, I don't know why SMB MailSlot Protocol is not working. Workgroups are the same, folder sharing over the network is working. You can download a Wireshark snapshot for investigation if useful. Regards Gerard

Hello, I use FS2004 with FSUIPC v3.98, WinXPpro SP2 on a desktop PC. I recently added WideFS v6.78 in order to use FS utilities from a laptop with WinXPpro SP3. I followed the book for installation and all is OK from server side. The problem is on client side. I monitored frames using Wireshark. I can see from client side incoming SMB Mailslot Protocol frames from server. Mailslot Name: \MAILSLOT\MS_WideServer When I run WideClient on the laptop, there is no outgoing frames at all. Client is waiting for connection. WideClient FS98 Eliminator - Waiting for a connection ********* WideClient Log [version 6.78] Class=FS98MAIN ********* Date (dmy): 20/10/10, Time 21:55:43.418: Client name is ROENTGEN 265 Attempting to connect now 1265 Trying to locate server: Need details from Server Broadcast 1265 Failed to connect: waiting to try again 3265 Attempting to connect now 67328 Trying to locate server: Need details from Server Broadcast 90593 ****** End of session performance summary ****** 90593 Total time connected = 0 seconds 90593 Reception maximum: 0 frames/sec, 0 bytes/sec 90593 Transmission maximum: 0 frames/sec, 0 bytes/sec 90593 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 90593 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* The question is why WideClient not sending frames ? I added ServerIPAddr with IP address of server into WideClient.ini with no success, still no outgoing frames. Is there a XP SP3 incompatibility ? Regards Gerard