I am also unable to connect

[LovingMother]

I have read the manual, FAQ, and a number of threads here. My husband set up his server on the PC last night and asked me to get it going while he is at work today.

I opened all three ports on the router.
I set my firewall (Norton Internet Security) to permit all activity from TeamSpeak

I can log in to admin, and can log into the server internally (127.0.0.1:8767), but I am still unable to log into the server through my IP. When I try, the response is: "No reply from server
Maybe the server is offline
or maybe teamspeak is not running on it"

What have I missed?

I would appreciate any advice.

[guldi]

- "no reply" FAQ Thread => don not use the WAN IP within the LAN

- If LAN IP doesn't work, you most surley have a firewall problem (shut it down for testing)

- only for LAN connections to your server, no router ports needs to be forwarded (be sure: FORWARDED, NOT opened !). Forwarding is only req. if you wan to have people connected from the WAN.

- do not forward the TCPQuery & webinterface port if it is not a must to have access from WAN to it (Security reason !)

[CheshireCat]

Hi LM
Opening ports are not enough, you need to forward them to the internal LAN ip address of your server machine. Why 3 ports? You should only need to forward port 8767 (although doing more than this won't cause problems)
Try turning off the local/pc firewall while you try to diagnose the problem. It's only of real use for outgoing traffic or guarding yourself against other LAN pcs anyway
You can't guarantee that attempting to log in via your WAN ip address will work, that depends on the model/brand of router.

[LovingMother]

I thought forwarding and opening the ports were the same thing. I have them forwarded. What is the difference between the LAN IP and the WAN IP? I use the IP of my router. I don't have a LAN specifically set up, but I do have multiple computers on a wireless network (the pc I have the server on is hardwired to the router), so does that mean I automatically have a LAN? How do I find out which IP address I need to use, then?

Thanks bunches. :)

[LovingMother]

Ok, it appears that I can connect to my server via the router ISP now as long as I use QuickConnect but not if I use Connect. Does that matter? I'm not sure why one will work but not the other. I am using the same name and password for both.

[LovingMother]

How do I get others connected? When they use my IP#, they get the "cannot connect" and when they tried IP#:8767, they get "error". Am I still using the wrong address? I am using the only IP available according to my admin settings. Does it determine the IP's automatically or did my husband have to set this?

I have no clue what I am doing.

[guldi]

I thought forwarding and opening the ports were the same thing. I have them forwarded. What is the difference between the LAN IP and the WAN IP? I use the IP of my router. I don't have a LAN specifically set up, but I do have multiple computers on a wireless network (the pc I have the server on is hardwired to the router), so does that mean I automatically have a LAN? How do I find out which IP address I need to use, then?

Thanks bunches. :)
- OPEN a port means to open it in a firewall => traffic on this port can go through to it's destination. In case you have firewalls somewhere in your network, you need to make sure the TS ports (statetd in the FAQ) are open.

- FORWARD a port means to tell a device to send all traffic sent to a specific port (or port range) to a specific IP address (which you can define). Routers with NAT do not allow incoming traffic unless it belongs to a already established connection started from within your LAN. A server running in your LAN does not start connections, he waits for them. As your router does not allow new incomming connections, conenction requests from the WAN will never reach your server => this is where PORT FORWARDING comes into the game. You tell your router to allow traffic on a specific port (in this case the TS server port) to be allowed through the NAT and FORWARD it directly to the IP address of the PC the TS server is running on. This way you can "bypass" the NAT of your router.



LAN / WAN IP:
read this thread (lower section): http://forum.goteamspeak.com/showthread.php?t=10158


Detection of IP addresses:
We have a FAQ thread dealing with this (problem) as well. I hate to write down whats already posted, so pls read the available docu, thx

[guldi]

This (http://forum.goteamspeak.com/showthread.php?t=15092) might be worth reading as well

[LovingMother]

We have the server up and people can log into it, but they can barely hear each other and when my husband tries to talk it crashes. They all hear each other very well on existing servers. Is this the Windows XP SP1 issue?

[guldi]

boah, that sounds like huge (sound, directX) driver problems ?

- tested wave #direct sound in TS
- played around with recording level settings (in TS and in the sound mixer) ?