Open alchokem opened 8 years ago
It's been 5 days... Any assistance you can provide would be appreciated.
Sorry, I forgot to reply. I can't think of anything that would help. It's not your ISP, it is local to your computer. If netstat doesn't find anything, then I cannot imagine what could be locking the port.
Is the account running WOL a local administrator on the computer?
Would you believe it...it's your very own optional service, WOLAgent, that causes this issue. At the time I installed your WakeOnLAN product, I installed this optional component which as you know creates a service that starts automatically. Stop this service and all is well. BTW, the command you suggested, "netstat -ab", does not reveal the fact that WOLAgent has gained exclusive access to this port, but the command "netstat -noa" does.
Oh, I'm glad you found it. Good catch. I never considered that someone would run the agent on the same machine.
I will update the documentation when I can find the time.
When attempting to start the Listener, I receive the following error. Following your suggestions for resolution, I have disabled "Simple TCP/IP Services" and using "Netstat -ab", I found no app is using this port. Have the same issue with Port 7. I've confirmed with my ISP, Cox Communications, they are not blocking these ports.
Any other suggestions? Thanks