Client unable to connect to server using hostname on local network

TeamSpeak 3 Client
1

I have configured Teamspeak server on windows server. I have a client on another desktop running Windows 11. I can use IP address to connect to server okay. But cannot use the hostname of the server to connect.

I am getting the following error message: “Failed to resolve hostname ”

On the server I have all required ports configured through windows firewall.
On my DC I have DNS entries configured for the Teamspeak Server, both forward and reverse lookups as well as a SRV record.

What am I doing wrong? Why can’t I connect using a hostname instead of an IP address?

Any assistance will be greatly appreciated.

2

Can you try to make a nslookup up to your hostname?

2 Likes
3

Yes, nslookup works fine. I am able to resolve the name to an IP address.

4

It might be possible that a myTS nickname is running under the same name.

If that is the case the nickname would be prioritised.
You can create a myTS nickname on the myTS website and set the IP as the target.

If you need a hostname however please provide your client logs.

2 Likes
5

The name on the myTS website is different from the hostname on the server.

Where do I find the log file?

I do not see the following path in my client installation. %localappdata%\TeamSpeak\Logs\Default

6

In TS3 you can press CTRL + L to open the logs

2 Likes
8
Logs
2025-03-03 17:53:18 Info TeamSpeak Client 3.6.2 (2023-09-20 09:48:13)
2025-03-03 17:53:18 Info SystemInformation: Windows 11 (26100) x64 (AMD or Intel) Binary: 64bit
2025-03-03 17:53:18 Windows Audio Session Devel Hardware agc not available - Desktop Microphone (7- Microsoft® LifeCam HD-3000)
2025-03-03 17:53:18 Windows Audio Session Devel Hardware agc not available - Microphone Array (Intel® Smart Sound Technology for Digital Microphones)
2025-03-03 17:53:18 Windows Audio Session Devel Hardware agc not available - Headset Microphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:18 SoundDevManager Debug Loading dynamic soundbackend from C:/Users/jahven/AppData/Local/Programs/TeamSpeak 3 Client/soundbackends/directsound_win64.dll
2025-03-03 17:53:18 Direct Sound Debug setting timer resolution to 1ms -
2025-03-03 17:53:18 SoundDevManager Debug Soundbackend loaded.
2025-03-03 17:53:18 Info *** Time [SPAWN_EVENTCONVERTER]: 119
2025-03-03 17:53:18 ClientUI Info OpenGL Info: LibGLES, Vendor: Google Inc., Renderer: ANGLE (Intel(R) Iris(R) Xe Graphics Direct3D11 vs_5_0 ps_5_0), Version: OpenGL ES 2.0 (ANGLE 2.1.0.57ea533f79a7)
2025-03-03 17:53:19 Info *** Time [ICONMANGER]: 132
2025-03-03 17:53:19 Addons Info Checking for addon updates…
2025-03-03 17:53:19 Plugins Info Loading plugin: teamspeak_control_plugin_win64.dll
2025-03-03 17:53:19 ControlPlugin Info Control Plugin started, accepting connections
2025-03-03 17:53:19 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - enter - DeviceDeleteList
2025-03-03 17:53:19 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - leave - DeviceDeleteList
2025-03-03 17:53:19 Addon Info Addon up to date.
2025-03-03 17:53:19 Info *** Time [BUILD_GUI]: 501
2025-03-03 17:53:19 Info *** Time [SERVERVIEW]: 548
2025-03-03 17:53:19 Info *** Time [SERVERVIEWMANAGER]: 571
2025-03-03 17:53:19 Info *** Time [MAINWINDOW]: 1243
2025-03-03 17:53:19 Info *** Time [INIT]: 1243
2025-03-03 17:53:20 ClientUI Info Qt version: 5.15.2
2025-03-03 17:53:20 ClientUI Info Using configuration location: C:\Users\joel.galloway\AppData\Roaming\TS3Client\settings.db
2025-03-03 17:53:20 ClientUI Info Last update check was: Mon Mar 3 08:58:58 2025
2025-03-03 17:53:20 Info Statistics report: User previously denied participation
2025-03-03 17:53:20 Bookmarks Info Collecting autoconnect bookmarks
2025-03-03 17:53:20 Newsticker Info Newsticker next check: Tue Mar 4 08:58:59 2025
2025-03-03 17:53:24 ClientUI Info Connect to server: *********TMSPK
2025-03-03 17:53:24 ClientUI Info Trying to resolve *********TMSPK
2025-03-03 17:53:24 TSDNS Info Trying to resolve server name: *********TMSPK
2025-03-03 17:53:25 TSDNS Info Failed to resolve server nickname: *********TMSPK
2025-03-03 17:53:25 TSDNS Info A/AAAA DNS resolve unsuccessful, *********tmspk Domain name not found
2025-03-03 17:53:25 TSDNS Info SRV DNS resolve unsuccessful, _ts3._udp.*********tmspk Domain name not found
2025-03-03 17:53:25 ClientUI Info Lookup finished: query= error=2
2025-03-03 17:53:25 ClientUI Info Failed to resolve *********TMSPK
2025-03-03 17:53:35 ClientUI Info Connect to server: 1##...*
2025-03-03 17:53:35 ClientUI Info Initiating connection: 1##...*:9987
2025-03-03 17:53:35 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - enter - DeviceDeleteList
2025-03-03 17:53:35 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - leave - DeviceDeleteList
2025-03-03 17:53:35 Windows Audio Session Debug WAS::openDevice-enter - {0.0.0.00000000}.{ddaf4a09-b27f-4f5f-84f0-6127480d2df3}
2025-03-03 17:53:35 Windows Audio Session Devel Mix Format: SRate:48000 Bitrate: 32 Channels: 2 - Headset Earphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Devel Initializing with mix format. - Headset Earphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Info Initialized with 2 channels in 32bit, 48kHz. - Headset Earphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Devel WAS Buffer size: 1056 - Headset Earphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Debug WAS::openDevice-leave - {0.0.0.00000000}.{ddaf4a09-b27f-4f5f-84f0-6127480d2df3}
2025-03-03 17:53:35 Windows Audio Session Debug WAS::startDevice-enter - {0.0.0.00000000}.{ddaf4a09-b27f-4f5f-84f0-6127480d2df3}
2025-03-03 17:53:35 Windows Audio Session Debug WAS::startDevice-leave - {0.0.0.00000000}.{ddaf4a09-b27f-4f5f-84f0-6127480d2df3}
2025-03-03 17:53:35 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - enter - DeviceDeleteList
2025-03-03 17:53:35 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - leave - DeviceDeleteList
2025-03-03 17:53:35 Windows Audio Session Debug WAS::openDevice-enter - {0.0.1.00000000}.{8edc6d11-e16d-4e5f-b1f3-75a29a8e0ff3}
2025-03-03 17:53:35 Windows Audio Session Devel Mix Format: SRate:48000 Bitrate: 32 Channels: 2 - Headset Microphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Devel Initializing with mix format. - Headset Microphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Info Initialized with 2 channels in 32bit, 48kHz. - Headset Microphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Devel WAS Buffer size: 1056 - Headset Microphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Debug WAS::openDevice-leave - {0.0.1.00000000}.{8edc6d11-e16d-4e5f-b1f3-75a29a8e0ff3}
2025-03-03 17:53:35 Windows Audio Session Debug WAS::startDevice-enter - {0.0.1.00000000}.{8edc6d11-e16d-4e5f-b1f3-75a29a8e0ff3}
2025-03-03 17:53:35 Windows Audio Session Debug WAS::startDevice-leave - {0.0.1.00000000}.{8edc6d11-e16d-4e5f-b1f3-75a29a8e0ff3}
2025-03-03 17:53:35 PktHandler Info server sent ciphers:1
2025-03-03 17:53:35 PktHandler Info Selected cipher:0
2025-03-03 17:53:35 PktHandler Devel Puzzle solve time: 3
2025-03-03 17:53:35 ClientUI Info Connect status: Connecting
2025-03-03 17:53:35 ClientUI Info Connect status: Connected
2025-03-03 17:53:35 ClientUI Info Connect status: Establishing connection
2025-03-03 17:53:35 ClientUI Info Connect status: Connection established

I am seeing a line here that refers to TSDNS.
I will configure this and see what happens.

9

Are you sure the hostname is correct? When there is a valid hostname it will try to open a connection like when you try it with the IP.

2 Likes
10

Yes, I am sure.

And confirm, this is the hostname for the Windows Server, correct?
And NOT the Teamspeak Server.

11

Yeah I’ve tried the hostname of the device/computer that was shown in my router dashboard.

3 Likes
12

Okay, I got it working!!!

1 Like
13

In the logs, there is a line that speaks to not seeing the domain name.

So, I used the severname.domain.local and it works.

Mind you, I did not see prior logs before configuring the following below.

  • pointer record
  • srv record
1 Like