Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details

If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.

EG Locking Port after a few minutes..

If you have a question or need help, this is the place to be.
Post Reply
abuttino
Experienced User
Posts: 144
Joined: Sun Jun 02, 2013 4:01 am

EG Locking Port after a few minutes..

Post by abuttino »

I have the AutoRemote plugin and it communicates on ANY specified port.

When I use this plugin on Windows Server 2008 R2 or Windows Server 2012, the port gets locked up after a few minutes and won't honor any incoming messages.

I've spoken with the developer about this and he is just as baffled as I am.

For your convenience, I've attached the plugin to this post for anyone to figure out why this would lock up..

From my firewall

Time reported by the Microsoft Forefront TMG Firewall Service: 3.076 seconds
Testing http://tzplchvtpa-hy2.mydomain.local:100/
Category: Connectivity error
Error details: 10061 - No connection could be made because the target machine actively refused it.

From netstat ÔÇôa

TCP 0.0.0.0:100 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:100 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:101 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:101 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:111 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:135 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:445 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:1039 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:1047 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:1048 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:1815 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:1816 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:2049 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:2179 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:3389 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:47001 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:49152 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:49153 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:49154 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:49155 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:49156 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:49174 TZPLCHVTPA-HY2:0 LISTENING
TCP 0.0.0.0:49175 TZPLCHVTPA-HY2:0 LISTENING
TCP 10.0.0.11:139 TZPLCHVTPA-HY2:0 LISTENING
TCP 10.0.0.11:1816 10.0.0.111:57624 CLOSE_WAIT
TCP 10.0.0.11:1816 10.0.0.111:57625 CLOSE_WAIT
TCP 10.0.0.11:1816 10.0.0.111:57626 CLOSE_WAIT
TCP 10.0.0.11:1816 10.0.0.111:57627 CLOSE_WAIT

I have used port 100, 101 1815, 1816 and a couple others in the 1000 range in the past, now they are left open, even after a machine reboot.

BTW, this is all internal, there is absolutely no firewall on the machine in question.
Attachments
__init__.py
(81.42 KiB) Downloaded 104 times
Top
abuttino
Experienced User
Posts: 144
Joined: Sun Jun 02, 2013 4:01 am

Re: EG Locking Port after a few minutes..

Post by abuttino »

More on this..

After extensive reading last night, I found this actually might be a bug in Evenghost where it doesn't properly release ports after the program is closed. Some things in the C++/C# code could be changed to fix this problem.

I did find out that at logoff the ports ARE released. This is a lot more promising than having to shut down 5 virtual machines.

Pako? Anyone?
Top
Post Reply

Return to “General Support”