Everything Server cannot connect

Discussion related to "Everything" 1.5 Alpha.
Post Reply
laxarus
Posts: 6
Joined: Tue Apr 23, 2024 6:52 pm

Everything Server cannot connect

Post by laxarus »

Hello,
I tried everything I could think of but cannot manage to get it connected and working.

PC A has everything server plugin installed and PC B is trying to connect.

Allowed UDP and TCP incoming port 14630 on PC A. When trying to connect from pc B, I am getting "Unable to add network index. Failed to connect 0" error.
PC A and PC B are all on the same subnet.
I tried opening the same ports on PC B.
I tried to use ip:port, FQDN:port, FQDN, combinations to connect.
PC A and PC B can ping each other and shares work just fine.

Tried to see the wireshark output and saw the request
Image
Any help pls?
void
Developer
Posts: 15402
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything Server cannot connect

Post by void »

The debug output should show more information about the connection failure:
  • In Everything 1.5, from the Tools menu, under the Debug submenu, click Start debug logging.
  • Attempt to connect to your Everything Server.
  • From the Tools menu, under the Debug submenu, click Stop debug logging.
    ---This will open your %TEMP%\Everything Debug Log.txt in Notepad.
  • Could you please post the output here or post anonymously here.
laxarus
Posts: 6
Joined: Tue Apr 23, 2024 6:52 pm

Re: Everything Server cannot connect

Post by laxarus »

Hey Void,

Thanks for the assistance. I sent the debug report with the link you provided for PC B when trying to connect to PC A.

I see this error on the log.

2024-04-24 04:32:05.602: OS_WINSOCK_SOCKET WAIT error 10060
void
Developer
Posts: 15402
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything Server cannot connect

Post by void »

Thank you for the debug log.



10060 is WSAETIMEDOUT

Connection timed out.
A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.



Could be your firewall blocking Everything?

Seems odd that there's a timeout, unless something is dropping the packet.

Please try temporarily allowing Everything.exe through your firewall, or temporarily disabling your firewall to determine if this is the cause.



Please try connecting from the local machine with localhost.



I'll also update the Everything for the next alpha release to show error 10060 in the UI instead of error 0
laxarus
Posts: 6
Joined: Tue Apr 23, 2024 6:52 pm

Re: Everything Server cannot connect

Post by laxarus »

I did try to connect it from localhost but it is still the same. Everything.exe, UDP and TCP 14630 ports are allowed through the windows firewall. Everything is binded to every interface "*".
Everything is running as service and with admin privilidges at the same time.
Please, see below screenshots.
iwicnF6.png
iwicnF6.png (69.53 KiB) Viewed 251 times
And some more logs trying to connect from localhost.

Code: Select all

2024-04-24 14:43:16.452: sizeof (DLGTEMPLATEEX) 104 158
2024-04-24 14:43:24.562: OS_WINSOCK_SOCKET WAIT error 10061
2024-04-24 14:43:24.562: Failed to connect 0
2024-04-24 14:43:24.562: sizeof (DLGTEMPLATEEX) 104 124
2024-04-24 14:43:38.059: OS_WINSOCK_SOCKET WAIT error 10061
2024-04-24 14:43:38.059: Failed to connect 0
2024-04-24 14:43:51.280: OS_WINSOCK_SOCKET WAIT error 10061
2024-04-24 14:43:51.280: Failed to connect 0
Last edited by void on Wed Apr 24, 2024 12:04 pm, edited 2 times in total.
Reason: trimmed log and fixed image link
void
Developer
Posts: 15402
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything Server cannot connect

Post by void »

Thanks for your reply and new logs.

Error 10061 is: WSAECONNREFUSED
Connection refused.
No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running.



Does the issue persist if you change Bind to interfaces to an empty string?
empty string = bind to all interfaces.
* will not work, you need to specify each absolute interface in a semicolon (;) delimited list.
For example: 127.0.0.1;10.0.0.1;192.168.0.1
All of these addresses need to belong to the server.
laxarus
Posts: 6
Joined: Tue Apr 23, 2024 6:52 pm

Re: Everything Server cannot connect

Post by laxarus »

That did the trick. Removing the bind and making it blank got me connected immediately both from local and remote hosts.
It is weird that binding does not work though.
void
Developer
Posts: 15402
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything Server cannot connect

Post by void »

I'm curious, where did you get the * from?

Should I add support for *?
laxarus
Posts: 6
Joined: Tue Apr 23, 2024 6:52 pm

Re: Everything Server cannot connect

Post by laxarus »

I don't remember where it came from. I might have added it or defaults?. Generally, in linux or for similar applications, to bind the all interfaces, it is common to use "*", that might be why I put it there.
laxarus
Posts: 6
Joined: Tue Apr 23, 2024 6:52 pm

Re: Everything Server cannot connect

Post by laxarus »

Thanks for clearing this up. Putting the details for binding in docs would be very much helpful.
void
Developer
Posts: 15402
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything Server cannot connect

Post by void »

Thanks for your reply.

I've added to the docs:

Set Bind to interfaces to a semicolon list of interfaces, for example: to the limit to local access only, set to: localhost
(leave empty to bind to all interfaces)



I will look into adding support for *
(looks like I need to do this at the plugin level as it's getaddrinfo that resolves the binding address)
Post Reply