SAS Open Ports

Long after ( at least 5 minutes ) i receive the update there are still at least four ports established with SAS......this ONLY happens with SAS updates and no others
Uncomfortable

 

Which version of SAS? Free or Pro? And how do you check this?

 

i believe you mean 'active connections' rather than 'open ports'. they should time out and close after a period of inactivity.

what are you monitoring the connections with? = port explorer?

 

I am using paid for version. The ports are not on a Time Wait status as one would expect, but 'Established' and for an inordinate amount of time. This has been the case for many weeks, although it stopped behaving this way after my post.

 

Just checked using version 4.0.1138 and my database was up to date. The connections all closed down within a few seconds of the answer back from SAS server. Does this occur on yours when you have an update or anytime you check updates. I have mine set to manual updates only.

 

If SAS auto updates then fine. If I initiate an update they stay on Established until I close the no update window or until SAS finishes the updating then they stay on Close_Wait forever unless I exit the program. (Nick I've asked about this awhile back)

Port Explorer 20 mins after an update...

 

The Close_wait is showing that the program as received a FIN from server (to close connection) but the OS is waiting for the program to actually close its connection (There is no time_out to this that I know of anymore, so it will remain in this state until the actual application closes (or forced to close by user) the connection.

It would indicate a problem/bug.

 

I receive updates manually. Just now i allowed the connection to remain established for a full three minutes before manually closing it. There is no Close_Wait time. Occasionally the connection will behave as it should, but not very often. and again, i have only seen this behavior w/SAS.

 

Establised connections do have a timeout, but I need to check as there are various. Normally, established connections are terminated by Program/server.

EDIT:
Have these problems been reported directly to vendor?

 

OK...
btw..good morning

 

Yes, good morning.

I will try to find time later to look at this on VM,...

EDIT:

I can take an hour now to look at this, I will download the "Free Version" and check the connections/timeouts made,

 

I will give Nick a mail @SAS HQ.

 

Sorry, I cannot check this today,... have been interrupted/called away. I will look at this as soon as I can.

Regards,

 

OK....i have not reported to vendor. I check in here before reporting problems.

 

I have installed SAS (free version), it did close all connections correctly after the initial update.

I will leave it installed for a day or 2 to keep a check.

[It is currently listening on localhost UDP 1077.]

 

Just to clarify,

Was it the main program that kept the connection, or was it the SSUPDATE.exe that is in the temp folders.

 

After a re-boot I am now seeing the same as reported.

The connection is being left active.
The end of data is acknowledge, but the program is not then sending a ack/rst to close the connection.

It does need reporting to vendor.

 

Both
I saw your post #17 Stem.....for the time being i have dropped the program.......i would think he has seen this thread.
Thank you for your concern.

 

Does this also happen with the 3.9 version or is it just the 3.9 version that does this?

 

The programs i was using were the last four betas.

 

OK, that would be v4 ReleaseCandidates.
I can't see it in 3.9, but perhaps other users can.

 

I was looking at the latest (free) release from vendors site. (file version 3.9.0.100

 

I saw the same issues with free version 3.9 and i am thinking the Pro version also.

 

WININet (the built-in windows library) that we use to do our Internet transfers is the one leaving those ports "open" - they are doing nothing and cannot harm your system or explose your system to any danger. Windows appear to try and "cache" the port access to they appear to be left open even after our application has properly closed the ports.

 

Your application is not closing the connections. I have full logs on this.

First log after manual update. The connections are closed. (duration < 1 sec)



Second log after re-boot. Manual update. The top 3 connections are not closed by your application. The last packets sent are "ack" (duration 6.5 minutes)


On each manual update since, the connections are not closed by the application.


I can post full packet info if required.