One Windows Client can not find UrBackup-Server while other Windows and Linux Clients do

rmm · September 13, 2016, 8:34am

We’ve got an UrBackup-Server installed in a FreeNas-Jail. It works great (Love your product). Several Linux and Windows clients are connected to it and work.
But we’ve got one client, installed on a Windows Standard Server 2012 which just doesnt manage to discover the Server. There is nothing meaningful in the clients logs (I’ll attach them anyway). As we can see out of the server logs, the server finds the client, but then fails to connect to it. I tried to restart the client computer after software installation, reinstalling the UrBackup client, disabling all firewalls, giving the Server an Ip-Hint, restarting server and client. But nothing succeeded so far.
Here are the logs:
client:

2016-09-13 09:58:29: Loaded -fileserv- plugin
2016-09-13 09:58:29: Loaded -fsimageplugin- plugin
2016-09-13 09:58:29: Loaded -cryptoplugin- plugin
2016-09-13 09:58:29: urbackupserver: Server started up successfully!
2016-09-13 09:58:29: FileSrv: Backup privileges set successfully
2016-09-13 09:58:29: FileSrv: Backup privileges set successfully 
(SE_SECURITY_NA
ME)
2016-09-13 09:58:29: FileSrv: Backup privileges set successfully 
(SE_RESTORE_NAM
E)
2016-09-13 09:58:29: Started UrBackupClient Backend...
2016-09-13 09:58:29: FileSrv: Binding UDP socket at port 35622...
2016-09-13 09:58:29: FileSrv: done.
2016-09-13 09:58:29: FileSrv: Disabling new behavior...
2016-09-13 09:58:29: Filesystem. 
Vol="\\?\Volume{7f302aa4-05f7-11e4-80b4-806e6f6
e6963}\" Name="system-reserviert" Type="ntfs" VPaths=0 Size=366997504
2016-09-13 09:58:29: FileSrv: Servername: -RMI-Windows-std-2012-
2016-09-13 09:58:29: FileSrv: Server started up successfully
2016-09-13 09:58:29: FileSrv: UDP Thread startet
2016-09-13 09:58:29: Bootable flag set for volume
2016-09-13 09:58:29: Found potential candidate: 
\\?\Volume{7f302aa4-05f7-11e4-80
b4-806e6f6e6963}\ Score: 103
2016-09-13 09:58:29: Filesystem. 
Vol="\\?\Volume{c46b4cfa-102f-11e4-80be-d872a7c
4d58b}\" Name="auslagerung" Type="ntfs" VPaths=1 Size=21471686656
2016-09-13 09:58:29: Bootable flag not set for volume
2016-09-13 09:58:29: Filesystem. 
Vol="\\?\Volume{7f302aa5-05f7-11e4-80b4-806e6f6
e6963}\" Name="system" Type="ntfs" VPaths=1 Size=160692170752
2016-09-13 09:58:29: Filesystem is System partition. Skipping...
2016-09-13 09:58:29: Filesystem. 
Vol="\\?\Volume{7f15a5ee-6e25-11e6-80eb-806e6f6
e6963}\" Name="" Type="" VPaths=1 Size=-1
2016-09-13 09:58:29: Bootable flag not set for volume
2016-09-13 09:58:29: Selected volume 
\\?\Volume{7f302aa4-05f7-11e4-80b4-806e6f6e
6963}
2016-09-13 09:58:29: System dir: C:\Windows
2016-09-13 09:58:29: Volpath: \\.\C:
2016-09-13 09:58:29: Device is not GPT formatted (0)
2016-09-13 09:58:29: Found no EFI System Partition
2016-09-13 09:58:30: urbackupserver: No available slots... starting new 
Worker
2016-09-13 09:58:30: ClientService cmd: STATUS 
DETAIL#pw=uWrvWf1vx33PkZcFQOavgjX
9fq72SO
2016-09-13 09:58:30: ClientService cmd: 
STATUS#pw=uWrvWf1vx33PkZcFQOavgjX9fq72SO
2016-09-13 09:58:30: ClientService cmd: 
STATUS#pw=uWrvWf1vx33PkZcFQOavgjX9fq72SO
2016-09-13 09:58:30: ClientService cmd: STATUS 
DETAIL#pw=uWrvWf1vx33PkZcFQOavgjX
9fq72SO
2016-09-13 09:58:30: ClientService cmd: 
STATUS#pw=uWrvWf1vx33PkZcFQOavgjX9fq72SO
2016-09-13 09:58:30: Looking for old Sessions... 0 sessions
2016-09-13 09:58:30: Internet mode not enabled
2016-09-13 09:58:31: ClientService cmd: STATUS 
DETAIL#pw=uWrvWf1vx33PkZcFQOavgjX
9fq72SO
2016-09-13 09:58:32: ClientService cmd: STATUS 
DETAIL#pw=uWrvWf1vx33PkZcFQOavgjX
9fq72SO
2016-09-13 09:58:33: ClientService cmd: STATUS 
DETAIL#pw=uWrvWf1vx33PkZcFQOavgjX
9fq72SO

and server (ignore the time, the server is in the wrong timezone):

2016-09-13 00:49:48: Socket has error: 61                                                                                           
2016-09-13 00:49:49: Socket has error: 61                                                                                           
2016-09-13 00:49:50: Socket has error: 61                                                                                           
2016-09-13 00:49:50: Socket has error: 61                                                                                           
2016-09-13 00:49:51: Socket has error: 61                                                                                           
2016-09-13 00:49:51: Connecting to ClientService of "RMI-Windows-std-2012" failed: Sending Identity to client "RMI-Windows-std-2012"
 failed. Retrying soon...                                                                                                           
2016-09-13 00:49:51: Socket has error: 61                                                                                           
2016-09-13 00:49:52: Socket has error: 61                                                                                           
2016-09-13 00:49:51: Socket has error: 61                                                                                           
2016-09-13 00:49:52: Socket has error: 61                                                                                           
2016-09-13 00:49:52: Socket has error: 61                                                                                           
2016-09-13 00:49:53: Socket has error: 61                                                                                           
2016-09-13 00:49:53: Socket has error: 61                                                                                           
2016-09-13 00:49:54: Socket has error: 61                                                                                           
2016-09-13 00:49:54: Socket has error: 61                                                                                           
2016-09-13 00:49:55: Socket has error: 61                                                                                           
2016-09-13 00:49:55: Socket has error: 61                                                                                           
2016-09-13 00:49:56: Socket has error: 61                                                                                           
2016-09-13 00:49:56: Socket has error: 61                                                                                           
2016-09-13 00:49:57: Socket has error: 61                                                                                           
2016-09-13 00:49:57: Socket has error: 61                                                                                           
2016-09-13 00:49:58: Socket has error: 61                                                                                           
2016-09-13 00:49:59: Socket has error: 61                                                                                           
2016-09-13 00:49:59: Socket has error: 61                                                                                           
2016-09-13 00:50:00: Socket has error: 61                                                                                           
2016-09-13 00:50:00: Socket has error: 61                                                                                           
2016-09-13 00:50:01: Socket has error: 61                                                                                           
2016-09-13 00:50:01: Socket has error: 61                                                                                           
2016-09-13 00:50:02: Socket has error: 61                                                                                           
2016-09-13 00:50:02: Socket has error: 61                                                                                           
2016-09-13 00:50:03: Socket has error: 61                                                                                           
2016-09-13 00:50:03: Socket has error: 61                                                                                           
2016-09-13 00:50:04: Socket has error: 61                                                                                           
2016-09-13 00:51:01: Connecting to ClientService of "RMI-Windows-std-2012" failed: Sending Identity to client "RMI-Windows-std-2012"
 failed. Retrying soon...                                                                                                           
2016-09-13 00:52:11: Connecting to ClientService of "RMI-Windows-std-2012" failed: Sending Identity to client "RMI-Windows-std-2012"
 failed. Retrying soon...                                                                                                           
2016-09-13 00:53:21: Connecting to ClientService of "RMI-Windows-std-2012" failed: Sending Identity to client "RMI-Windows-std-2012"
 failed. Retrying soon...                                                                                                           
2016-09-13 00:54:31: Connecting to ClientService of "RMI-Windows-std-2012" failed: Sending Identity to client "RMI-Windows-std-2012"
 failed. Retrying soon...                                                                                                           
2016-09-13 00:55:41: Connecting to ClientService of "RMI-Windows-std-2012" failed: Sending Identity to client "RMI-Windows-std-2012"
 failed. Retrying soon...                                                                                                           
2016-09-13 00:56:51: Connecting to ClientService of "RMI-Windows-std-2012" failed: Sending Identity to client "RMI-Windows-std-2012"
 failed. Retrying soon...                                                                                                           
2016-09-13 00:58:01: Connecting to ClientService of "RMI-Windows-std-2012" failed: Sending Identity to client "RMI-Windows-std-2012"
 failed. Retrying soon...                                                                                                           
2016-09-13 00:59:11: Connecting to ClientService of "RMI-Windows-std-2012" failed: Sending Identity to client "RMI-Windows-std-2012"
 failed. Retrying soon...                                                                                                           
2016-09-13 01:00:21: Connecting to ClientService of "RMI-Windows-std-2012" failed: Sending Identity to client "RMI-Windows-std-2012"
 failed. Retrying soon...                                                                                                           
2016-09-13 01:01:31: Connecting to ClientService of "RMI-Windows-std-2012" failed: Sending Identity to client "RMI-Windows-std-2012"
 failed. Retrying soon...                                                                                                           
2016-09-13 01:02:41: Connecting to ClientService of "RMI-Windows-std-2012" failed: Sending Identity to client "RMI-Windows-std-2012"
 failed. Retrying soon...                                                                                                           
2016-09-13 01:03:52: Connecting to ClientService of "RMI-Windows-std-2012" failed: Sending Identity to client "RMI-Windows-std-2012"
 failed. Retrying soon...

There are a whole lot of these socket errors. But I’ve got also logs where he couldn’t connect to the client and there where no socket errors around at all, so I don’t think that they are the reason.
I don’t know if the ports of the client should be open before it discovered the urbackup server, but here an nmap of the client:

PORT STATE SERVICE
35621/tcp closed unknown
35622/tcp closed unknown
35623/tcp closed unknown
35622/udp open|filtered unknown

On the working clients also the tcp ports 35621 and 35623 are open.
Any hints?

ttrammell · September 13, 2016, 4:00pm

Most times I have seen this in logs on Linux machines: "Socket has error: "
A restart has fixed; however, some people have also said leaving it has also fixed it.

Two suggestions for you, that come after a question:

Q: Can you see your client in your web interface at least?

If you cannot: On the Windows client under C:\Program Files\UrBackup there are two files called server_idents.txt and new_server_idents.txt. Delete them and restart the service.
If you can: In your web interface, download a client download of that specific client, and install it on that machine. Restart the service. (May also need to delete the two .txt files and restart the service again afterwards if that does not help.)

Used Network Ports: UrBackup - Server administration manual

rmm · September 13, 2016, 4:21pm

Q: Can you see your client in your web interface at least?

No, I can not.
When I add the IP-Address of the Client as hint, he says it is online,
but doesn’t recognize it, or but it on to the list. Propably he just
does a ping to verify that?

If you cannot: On the Windows client under C:\Program Files\UrBackup
there are two files called server_idents.txt and
new_server_idents.txt. Delete them and restart the service.
*

Those files do not exist on the client.

As it seems the Server finds the client (according to the log), so I
guess the client must be answering to the server-broadcast, but then the
Server never manages to connect to the client, and so the client never
creates those files. (I don’t have a deeper insight into the whole
client/server-discovery process, but I guess that’s more or less what’s
happening).

You’d have any other hints?

ttrammell · September 13, 2016, 4:44pm

Scratch the last post, I just realized you posted a client log.

Without those bserver_idents.txt[/b] files, it cannot locate a server to use. Do you at least have the C:\Program Files\UrBackup folder, or no?

rmm · September 14, 2016, 10:00am

yes, the folder exists, with all the executables and other stuff in it.
There is also a subfolder urbackup with some database files.

ttrammell · September 14, 2016, 12:40pm

Well…

If your ports are unblocked, no firewalls are messing with you, you have the client folder with no server identification…

All I got left is manually mapping the client; beyond that, I do not know.

UrBackup will auto-discover any client in the same sub-network. If you have a 10.0.0.0/8 address, you should have 0 problems; but a server on a 10.0.0.0/8 to a client on 172.168.0.0/16 is supposed to have problems performing local backups.

I mean, you can try making a server_idents.txt file and putting in the server identity located under (your) Web-Interface -> Status -> Add New Client

I have never manually mapped a client, just more or less going off of what I see in the UrBackup folder, and it may or mat not work. Just giving you a heads up.

rmm · September 16, 2016, 12:12pm

thanks a lot for your help.
I decided to not lose more time, and backup the machine from “outside”,
it’s running in a virtual machine, so it’s easily possible.

rmm · September 21, 2016, 10:56am

btw. It had nothing to do with urBackup. A colleague of mine complained that several other services are behaving completely crazy on that server. We did a complete reinstall, and now everything is working.