Suddenly unable to connect via widefs

[BigRick]

Well, I'm at a loss. Suddenly WideFS is not wanting to connect between my computers. I get no connect message from either the client or the server. This is in the log file:

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

Date (dmy): 20/03/09, Time 13:17:41.406: Client name is VISTA_64

141 Attempting to connect now

7157 Trying TCP/IP host "Ricks-Toy" port 8002 ...

7157Okay, IP Address = 192.168.0.100

28157 Error on client pre-Connection Select() [Error=10060] Connection timed out

28157 Ready to try connection again

29204 Attempting to connect now

52672 ****** End of session performance summary ******

52672 Total time connected = 0 seconds

52672 Reception maximum: 0 frames/sec, 0 bytes/sec

52672 Transmission maximum: 0 frames/sec, 0 bytes/sec

52672 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

52672 **************** Individual client application activity ****************

52672 Client 3312 requests: 5 (Ave 5/sec), Data: 270 bytes (270/sec), Average 54 bytes/Process

52672 ********* Log file closed (Buffers: MaxUsed 1, Alloc 5 Freed 5 Refused 0) *********

Now before anyone hollers "it must be your firewall", bear in mind that I've turned the Windows firewall OFF and no change. Still wont connect. Also, with the firewall on, I've set up port 8002 with TCP on BOTH machines to be allowed to pass thru the firewall. In addition, in the ServerName and Protocol are defined in the WideClient.Ini file. I've also tried it without defining them. In addition, I'm running no other firewall. It WAS working fine for over 4 yrs, then suddenly BOOM, down she went. I made no changes at all to my system. I'm running the most current versions and both are registered. Suggestions? I'm basically shut down now since ALL my FS utilities run on my 2nd computer. Thanx.

-Rick

[Pete Dowson]

This is in the log file:

That's only half the story. Where's the Server's log file?

It WAS working fine for over 4 yrs, then suddenly BOOM, down she went. I made no changes at all to my system.

Well, someone has, obviously! ;-0

Pete

[BigRick]

What? Can't deduce problems with 1/2 the story? lol I thought about that other log after I posted the 1st one. Here's the server log:

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 20/03/09, Time 13:26:00.092: Server name is RICKS-TOY

101557 Initialising TCP/IP server

101573 Initialising IPX/SPX server

101573 IPX/SPX socket() failed [Error=10044] Socket type not supported

101573 Failed to start IPX/SPX Server

101573 Initialising UDP/IP server

102680 Broadcasting service every 1000 mSecs

113148 Restarting service due to total lack of use

113164 Failed to start IPX/SPX Server

150307 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 *********

Not sure if the IPX/SPX is the problem since that seems to be failing.

-Rick

[Pete Dowson]

Here's the server log

Hmm. All that shows is that nothing is arriving at all from your client.

So, it has to be either firewall, or a selected name or IP address which is incorrect, or simply that your Network isn't working.

Have you checked the actual network? I've had network cards/ chips fail before, and switches/hubs come to that.

Check the INI files again. In fact better that that, show me them, both of them, Server and Client. There's nothing else to go on here. All the logs indicate that the two PCs aren't communicating, full stop.

Not sure if the IPX/SPX is the problem since that seems to be failing.

No, it just means you haven't installed that protocol. Microsoft made it optional a while back now.

Regards

Pete

[BigRick]

Here is the server ini file:

[Config]

AdvertiseService=1

AutoRestart=0

AutoUpdateTime=13

MaximumBlock=4096

NoStoppedRestarts=Yes

Port=8002

Port2=9002

RestartTime=10

SendTimeout=15

TCPcoalesce=No

Very basic and no changes made by me. Here is the client ini file:

[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=476,32,601,85

ServerName=Ricks-Toy

Protocol=TCP

All I changed to try to get it to work again is specifying the Servername and Protocol. Other than that, it's default. I can access all FOUR of my computers thru my home network with no problems. Each can communicate with the other. It's specifically WideFS that seems to have the prob. One thing I have not done yet is put it on one of my other computers and try to connect to the server located on my FS machine that way. That's next, I suppose. If it DOES connect, that would narrow the prob down to a single computer. As a side note, it was working and then went down in the middle of the flight. Connection was fine until then. After that, it would not reconnect.

-Rick

[Pete Dowson]

All I changed to try to get it to work again is specifying the Servername and Protocol. Other than that, it's default. I can access all FOUR of my computers thru my home network with no problems. Each can communicate with the other. It's specifically WideFS that seems to have the prob.

wideFS is only using simple, standard TCP, UDP or IPX protocol, about as simple as you can get, copied from Microsoft examples. something is certainly blocking it completely. There's nothing I can see wrong with the INI files or Logs. There's simply nothing getting through.

Have you tried UDP at all, just in case it's only the TCP side that broken? I think windows Explorer uses UDP, idf it is Explorer you mean by " thru my home network".

narrow the prob down to a single computer. As a side note, it was working and then went down in the middle of the flight. Connection was fine until then. After that, it would not reconnect.

Certainly sounds like hardware put like that. Software doesn't normally behave like that.

Regards

Pete

[BigRick]

Alright, well, I got both of my laptops to connect with no problem. So, seems to be just my main FS util computer. After beating my head against the table for about 10 minutes, I decided to try something simple. I rebooted the machine. And lo! It connects! Sometimes knowing quite a bit about computers can make you overlook the simple solution. That will teach me. Thanx anyway!

-Rick

[Pete Dowson]

... I decided to try something simple. I rebooted the machine. And lo! It connects!

Erisn't that something you do regularly anyway? It's a PC left on all the time?

Sounds like something glitched and corrupted something in the lower levels somewhere. Anyway, glad you sorted it!

Regards

Pete

[BigRick]

Nope! I leave my PCs on all the time. The 2 desktops anyway. The 2 laptops I turn off. I'll leave it at that since I don't want to start that major debate about "leave them on/turn them off" that I've seen for YEARS. Take it easy.

-Rick