Linux client sends wrong name to server


Hello all,
I’m facing a strange problem with one of my linux clients.
On startup the client sends back wrong name. Actually it sends back names of other valid Windows clients I have, which causes a total mess(Linux backups go to Windows clients)

What is the process to get/send back client name on a Linux client (Debian 9.8)?

The client log file shows:
2019-05-30 09:05:14: Started UrBackupClient Backend…
2019-05-30 09:05:14: FileSrv: Binding UDP socket at port 35622…
2019-05-30 09:05:14: FileSrv: done.
2019-05-30 09:05:14: FileSrv: Servername: -windows-hostname-here-
2019-05-30 09:05:14: FileSrv: Server started up successfully
2019-05-30 09:05:14: FileSrv: UDP Thread startet
2019-05-30 09:05:15: Final path: /
2019-05-30 09:05:15: Final path: /var
2019-05-30 09:05:15: Final path: /home
2019-05-30 09:05:15: Final path: /boot


It uses the name from the settings (that’s probably the problem) and if that isn’t configured it uses the hostname…
So the problem would be the server sending the wrong settings to a new client?


This linux client uses the default configuration. (Separate settings for this client - is NOT ticked)
I don’t think the server is pushing wrong client name but I may be wrong.

Do IPs play a role in clients/client cofig?

I’m asking because this linux client is also a router(and VPN server) and does SNAT/DNAT for some VPN clients, which are also UrBackup clients.

So once a Windows urbackup client is connected via VPN it does Internet based backup but the IP showed for client is not correct - the IP shown in UrBackup GUI is the one of the Linux client

Not sure if I was clear enough :slight_smile:
Let me know if more info is needed and what troubleshooting direction to go to next …

Thank you!


After manually changing the linux client name in the cfg file, today I see it shows a wrong name again.

As I said, the Windows client was connected over VPN and UrBackup server thinks that its IP is - this is the actual/real IP of the Linux client.

Any ideas?