larryB
24-02-2006, 18:41
As a suggestion, please consider using defaults that assist users with configuration. A significant portion of forum traffic, and frustraion on the part of users, has to do with configuration issues. These may be reduced by:
- including teamspeak public test servers with logins and all configuration details set, as part of the default that exists after a clean install
- including 1-2-3-4 how to connect discussion
- including diagnostics that detect if the program, as installed and configured, can connect to a teamspeak public server.
- including diagnostics that detect where the program fails to connect to a teamspeak public server, such failure points might include (a) local machine firewall, (b) local area network firewall, (c) gateway / router configuration, etc
Simple pings help with some of this. Simple test packet transmissions internal to a standard configuration that connects to one of your public servers, could resolve the rest. A plain english response could indicate what corrective measures are required including (1) server lan router port forwarding, (2) client lan router configurations and (3) teamspeak configurations.
If a test shows a teamspeak configuration error, the test could offer to attempt to correct the teamspeak configuration and then re-run the test.
Bottom line, Ventrillo works fine for me, but TS has never worked for me and I can't find the problem.
Hours of reading hundreds of forum posts, and trial and error tweaking to the router configuration has not resolved the problem.
As a result, I am at the point of just not liking TeamSpeak because it just doesnt work with standard out of the box configurations on my router and windows XP machine.
Adios.
Larry
- including teamspeak public test servers with logins and all configuration details set, as part of the default that exists after a clean install
- including 1-2-3-4 how to connect discussion
- including diagnostics that detect if the program, as installed and configured, can connect to a teamspeak public server.
- including diagnostics that detect where the program fails to connect to a teamspeak public server, such failure points might include (a) local machine firewall, (b) local area network firewall, (c) gateway / router configuration, etc
Simple pings help with some of this. Simple test packet transmissions internal to a standard configuration that connects to one of your public servers, could resolve the rest. A plain english response could indicate what corrective measures are required including (1) server lan router port forwarding, (2) client lan router configurations and (3) teamspeak configurations.
If a test shows a teamspeak configuration error, the test could offer to attempt to correct the teamspeak configuration and then re-run the test.
Bottom line, Ventrillo works fine for me, but TS has never worked for me and I can't find the problem.
Hours of reading hundreds of forum posts, and trial and error tweaking to the router configuration has not resolved the problem.
As a result, I am at the point of just not liking TeamSpeak because it just doesnt work with standard out of the box configurations on my router and windows XP machine.
Adios.
Larry