iforrage Posted June 5, 2011 Report Share Posted June 5, 2011 Hi. WideFS was working fine since installation, including yesterday. Then this morning, it won't connect. When I disabled/re-enabled widefs, it said getting ready, then a few seconds later said not able to serve. Here's the log output: ********* WideServer.DLL Log [version 7.705] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 05/06/11, Time 11:13:07.758: Server name is HOME 15694 Initialising TCP/IP server 15694 Initialising IPX/SPX server 15694 IPX/SPX socket() failed [Error=10044] Socket type not supported 15694 Failed to start IPX/SPX Server 15694 Initialising UDP/IP server 16099 Broadcasting service every 1000 mSecs Thanks, Jesse Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 5, 2011 Report Share Posted June 5, 2011 Hi. WideFS was working fine since installation, including yesterday. Then this morning, it won't connect. When I disabled/re-enabled widefs, it said getting ready, then a few seconds later said not able to serve. Here's the log output: That's just the first 18 seconds. When was a client started? Log fragments aren't of much use I'm afraid, you need to close FS before getting the log, and i'd certainly also need to see the Client log -- every connection has two ends! ;-) BTW the "Not able to serve" message only normally occurs if your copy is not registered. If there's no connection it simply says "waiting for clients". It only checks registration before starting in the first place, so I've no idea exactly what you are seeing, and it isn't being logged, but I assume those details were in the previous log before you disabled and re-enabled it (why do that?). The FSUIPC log would show registration validity. Pete Link to comment Share on other sites More sharing options...
iforrage Posted June 5, 2011 Author Report Share Posted June 5, 2011 Hi Pete, It flashed for a second or two (not able to serve), then it went to "Waiting for clients." But, it never connected. I disabled/re-enabled to see if it would jar something and re-establish the connection with the client computer, which it did not. I don't understand, I've made no changes, it just stopped working. Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 5, 2011 Report Share Posted June 5, 2011 It flashed for a second or two (not able to serve), then it went to "Waiting for clients." But, it never connected. I disabled/re-enabled to see if it would jar something and re-establish the connection with the client computer, which it did not. I don't understand, I've made no changes, it just stopped working. I still can't help without information. As I said, I need to see both WideServer and WideClient logs, for the failing part (not after to disable and reenable, which will lose the information in the log). And please close both FS and WideClient down first. The FSUIPC log may also be useful. I did mention all this in my last reply. Now another day goes by ... :mellow: Something evidently changed. If not by you then maybe you have a hardware failure. But really I cannot hazard a guess from here. Information may well help, do you see? Regards Pete Link to comment Share on other sites More sharing options...
iforrage Posted June 5, 2011 Author Report Share Posted June 5, 2011 Oh yeah, sorry Pete. I thought I attached the logs. Oops. In any event, I have got it working. I had to add the "servername" and "protocol" lines to the client ini file. Didn't have to before, tho. :blink: Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 6, 2011 Report Share Posted June 6, 2011 Oh yeah, sorry Pete. I thought I attached the logs. Oops. In any event, I have got it working. I had to add the "servername" and "protocol" lines to the client ini file. Didn't have to before, tho. :blink: They are needed if the Broadcast's aren't getting through from the Server. This could be down to any of these reasons: 1. Something else is using port 9002 on one of the PCs. 2. The two PCs are not in the same workgroup 3, The operating system in the Client predates the broadcasting facility (earlier than XP SP1). Regards Pete Link to comment Share on other sites More sharing options...
Ferry Spaan Posted June 7, 2011 Report Share Posted June 7, 2011 Hi Jesse, This is odd... Yesterday I had exactly the same problem. I also followed the same logic as you have done, but not a clue. I decided to download FSUIPC4 and WideFS again and to reinstall it. This solved it for me. I have used FSUIPC and WideFS for many years now, but this was the first time to have this issue. The day before , not a single glitch. No installs of other applications, nothing else. Decided not to worry about it, untill I noticed this threat :) Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 7, 2011 Report Share Posted June 7, 2011 This is odd... Yesterday I had exactly the same problem. I also followed the same logic as you have done, but not a clue. I decided to download FSUIPC4 and WideFS again and to reinstall it. This solved it for me. I have used FSUIPC and WideFS for many years now, but this was the first time to have this issue. Unless the versions you downloaded were different from the ones you had installed, I can't see how reinstallation could have made any difference. FSUIPC certainly won't run if it is corrupted (it uses the Windows digital signature system to check that). Regards 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