- What is the exact error message?
- Can a friend reach the same address through another internet connection?
- What happens on your device with a fresh connection tab or another network?
These answers are clues, not proof of a cause. Make one attempt, record its result and time, then move to the next check.
1. Separate connection errors from password or audio problems
| What do you see? | Where should you start? |
|---|---|
| Failed to connect to server | Check the address and network reachability of that server. This generic message does not specify a cause. |
| Failed to resolve hostname | Check the spelling of the domain and whether its name resolves to a connection destination. |
| An explicit password, ban or permission message | Follow that specific message. Random network changes or a new identity are not an appropriate workaround. |
| You can see channels but have no audio | The connection exists. Start with the voice-settings guide. |
For password errors, read about server passwords, channel passwords and Privilege Keys. This article focuses on not reaching a server, not bypassing its access restrictions.
2. Confirm the address with a trusted source
In Connections → Connect, compare the destination with the current address supplied by the administrator or the server's official website. Check extra spaces, spelling and an old port saved in a bookmark. If the owner supplied a specific port, use that value rather than guessing.
TeamSpeak's connection-error checklist lists wrong addresses, name-resolution problems, filtered traffic and an offline destination as possible causes. That document concerns error 0x705; not every desktop connection failure displays that code.
AmoHa's public address is amoha.ir. Enter the domain, not a website-page address such as https://amoha.ir/blog. The Windows installation and connection guide covers the complete first-connection process.
3. If you were connected earlier, try a fresh server tab
Sometimes an old disconnected tab keeps failing while a new tab connects. A TeamSpeak staff explanation describes how each server tab uses its own socket; a blocked or closed socket can leave the original tab unable to reconnect. This is one possible situation, not a universal explanation.
If that matches your experience, try the address once in a fresh tab. Record the result if the problem returns: a successful new tab does not establish why the original connection broke. Do not delete bookmarks or identities. Before reinstalling, make a safe identity backup.
4. Narrow the problem with two comparisons
- Can a friend connect through a different internet connection? If so, the server is reachable from at least that route. Your route, device or connection-specific restrictions still need investigation. This alone does not establish that you were banned.
- Can the same device connect through another network? If available, try your own hotspot once, considering mobile-data costs and network rules. A different result is a clue about the network path, not proof of a broken router or fault by one provider.
- Do several people on different routes fail at the same time? Send the time and address to the administrator. The destination or a network near it may be affected; everyone need not change their own configuration.
An accessible website does not guarantee that its voice service is reachable. TeamSpeak's protocol documentation identifies UDP for voice. Loading a web page does not test that same service and traffic path.
5. Treat hostname errors as a separate clue
If the domain cannot be resolved to a usable destination, first check its spelling against the server's own instructions. TeamSpeak's address-resolution documentation explains the role of domain records. The domain owner needs to investigate server-side configuration.
If necessary, ask the trusted administrator to confirm a direct destination for a limited comparison. A working direct destination alongside a failing hostname suggests a name-resolution problem. It is not a reason to permanently replace the published address or try an unknown IP. Ordinary members do not need to change the server's DNS records.
6. Check security rules without switching protection off
If your device's security report shows that the official client is blocked, have a knowledgeable person review the rule for that application. Microsoft explains that allowing a recognized application is generally less risky than leaving a port open, but neither action is risk-free.
Avoid an unnecessary router factory reset, putting the device in a DMZ, or installing an unknown connection-repair tool. On a work or university network, ask its administrator for help. Use the official TeamSpeak 3 download guide for the client.
What should you send to support?
A short, comparable report is more useful than repeatedly pressing Connect:
- The complete error text and the time it happened, including the time zone;
- The public destination, client version and operating system;
- Whether friends are affected too;
- The result of a fresh-tab or alternative-network attempt, if you made one.
In TeamSpeak 3 for Windows, Tools → Client Log or Ctrl + L opens the current client log, as described in the official TeamSpeak community. Share only the relevant section through private support after removing personal details. Never post your identity file, passwords, access keys or an entire device log in public chat.
Common questions
Does this error mean the server is offline?
Not necessarily. The generic connection message alone cannot establish that. A confirmed address and comparison from another route help narrow it down.
Should I create a new identity?
Not as a first troubleshooting step. Previous ranks and permissions may be associated with your existing identity. Identify the actual error and keep a backup.
It works only through a VPN. Have I found the cause?
You have established that a different route changes the result. That observation alone does not identify the responsible network, route or setting. Report it with the exact time.
Next steps
Find the public address and joining information on the Iranian TeamSpeak server page. If AmoHa still will not connect, send the short report above to AmoHa support. More guides are available on the AmoHa blog.
Sources checked October 6, 2026. This is a low-risk diagnostic workflow, not a promise to fix every error or a report of tests on your connection.