UPS700 Posted March 15, 2007 Report Share Posted March 15, 2007 I recently have had to rebuild my Wide client hard drive, since then I can not connect to the server. The following are the client.inl, client log and the server ini and log. [Config] ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port=8002 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 Window=105,16,593,57 ********* WideClient Log [version 6.70] Class=FS98MAIN ********* Date (dmy): 14/03/07, Time 11:24:01.250: Client name is BOBOWABO 500 Attempting to connect now 1546 Trying to locate server: Protocol not yet decided 1546 Failed to connect: waiting to try again 3562 Attempting to connect now 67562 Trying to locate server: Protocol not yet decided 2296890 ****** End of session performance summary ****** 2296890 Total time connected = 0 seconds 2296890 Reception maximum: 0 frames/sec, 0 bytes/sec 2296890 Transmission maximum: 0 frames/sec, 0 bytes/sec 2296890 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 2296890 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* ; 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=BOBOWABO 2=NOTEBOOK ( I am attemping to use Client BOBOWABO ********* WideServer.DLL Log [version 6.70] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 14/03/07, Time 11:17:32.682: Server name is UPS700 176906 Initialising TCP/IP server 176937 Initialising IPX/SPX server 176937 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 176937 Failed to start IPX/SPX Server 176937 Initialising UDP/IP server 178171 Broadcasting service every 1000 mSecs 188234 Restarting service due to total lack of use 188250 Failed to start IPX/SPX Server 16292812 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 ********* I even tried adding, ServerName=UPS700. That had no effect. I even compared my client ini with one sent to me by a friend, I saw no difference. Thanks, Bob Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 15, 2007 Report Share Posted March 15, 2007 I recently have had to rebuild my Wide client hard drive, since then I can not connect to the server.... 500 Attempting to connect now 1546 Trying to locate server: Protocol not yet decided 1546 Failed to connect: waiting to try again This simply means the Client is not seeing the Broadcasts from the Server. Either you are not using WinXP or Vista on both PCs or the Network isn't working correctly. I think you need them to be in the same workgroup. You don't need to rely on the broadcasts if you provide the ServerName= and Protocol= parameters in the WideClient.INI file. The automatic connection system, which works fine for 99% of cases is quite a recent addition, but in the past you always had to tell Wideclient how to find the Server. I even tried adding, ServerName=UPS700. That had no effect. That would stop it connecting to a different Server, assuming it ever saw any broadcasts at all, but it would still need to see UPS700's broadcast to determine the Protocol it should use. Try adding the Protocol parameter (e.g. Protocol=TCP). It may still not work -- if you are using WinXP or better on both PCs then the broadcasting would work fine if you had both PCs on the same subnet and in the same workgroup. If that sort of stuff is wrong they may not see each other in any case. I even compared my client ini with one sent to me by a friend, I saw no difference. That's not surprising considering the default INI is the same on every installation (how can it change if you don't change it?), and as it works in 99% of cases it is rarely changed. ;-) Regards Pete Link to comment Share on other sites More sharing options...
UPS700 Posted March 15, 2007 Author Report Share Posted March 15, 2007 I checked the workgroup name in each computer, one was HOME' and the other was HOME. I corrected that but it didn't help, I then added Protocol=TCP and just like magic, the two connected. Many Thanks, Bob Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 15, 2007 Report Share Posted March 15, 2007 I checked the workgroup name in each computer, one was HOME' and the other was HOME. I corrected that but it didn't help, I then added Protocol=TCP and just like magic, the two connected. The broadcasting from the Server isn't working then. You never said whether both your systems are running WinXP. Pete Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now