PDA

View Full Version : server worked, i went to a lan and now i can no longer connect? help?!

ShoelessOne
19-01-2003, 21:52
well, l ike the title says, i have been running teamspeak for a couple of days now... but, last night i went to a lan, and now i can no longer connect to the server.
it says

[15:55:22] No reply from server
Maybe the server is offline
or maybe teamspeak is not running on it


when i was at the lan i used teamspeak, but all i did was connect to the server using my self assigned IP address (192.168.1.2) instead of my WAN IP address.

what is going on?

anybody have any help they can offer?
ShoelessOne
20-01-2003, 21:42
oh yes, and i have now uninstalled and reinstalled teamspeak (both client and server) and i still cant connect. some friends have also tried connecting, they get the same error i do.


?
Cstar_maxim
20-01-2003, 22:15
If you have moved your server to a LAN you will need to open your UDP port 8767 in the firewall in order to connect to it.
ShoelessOne
20-01-2003, 22:28
no no, u see, i had my computer on a router, and it worked perfectly fine. i brought my computer to a lan at a friends house, hooked it up. the only settings i changed was the IP address which i set to 192.168.1.2.

then i brought it home the next day, and plugged it back into my router. i didnt change any settings, or anything. all i did was make my computer obtain the IP address automatically again.

i cant connect to the server, nor can friends connect to my server.
Cstar_maxim
21-01-2003, 16:33
Okay, one step at a time.

you are running a TS server on a Mobile computer?

Your Server was behind a router, then you took the computer that runs the server and client to a LAN, which assigned a new IP to your machine.

You have brought your computer back "home" and now you can not connect to TS even after re-assigning IP.

Try having your client connect to 127.0.0.1 if your client and server are on same machine.
ShoelessOne
21-01-2003, 21:00
i have a 1.33 ghz AMD athlon Tbird, (w/ 266 fsb). I have cable internet through ATT bi. I have the coax (rb45) cable plugged into my cable modem, and from my cable modem it goes to a wireless router. The wireless computer then goes to my computer in my room, as well as a computer upstairs.

I did not change anything on my router or my computer. The only thing i did was change (in network settings) my IP address from "Obtain IP address automatically" to "192.168.1.2". After that i ran teamspeak at the lan party. It ran fine, i just had people connect to 192.168.1.2 instead of my regular IP address that i have (12.241......). the 12.241...... ip address is the IP address that i get when i right click on teamspeak server 2 in the taskbar.

When i brought the computer back from the lan, i changed the IP from "192.168.1.2" to "obtain ip address automatically" (as it was set before). that is all i did. I would think it should have zero effect on anything, but i am no longer able to 1. connect to my own server with the 12.241... ip address (which by the way i am still told is correct by right clicking on icon in taskbar) 2. have friends connect to my server.

i get the message from above /\. thanks alot for help.

really.

ShoelessOne
Cstar_maxim
21-01-2003, 22:23
You can always connect to a server that is runs both server and client on the same computer using IP 127.0.0.1 instead of the IP specified by Teamspeak.

Try this first to help figure out the problem. This will show that TS is up and running and it is a firewall/networking problem.

Then we can take it from there.
ShoelessOne
22-01-2003, 22:36
ok, well, i could at least connect using 127.0.0.1... For some reason while i am connected to the server however i cant access the server admin page though (right click on taskbar icon, click on administration).

so, what does this all mean?

p.s. Thanks again
Cstar_maxim
23-01-2003, 08:34
what I think may have happend is a re-initalising of your wireless LAN has automaticly set up a new firewall and is blocking your 8676 UDP port again.

Its just a guess.....I am not sure how wireless systems work at re-establishing connections but I would think that if your internal IP is automatically obtained and you end up with a differant IP than what you had when you disconnected it could setup default firewall settings for the new IP.
ShoelessOne
23-01-2003, 20:00
ok, ah, i failed to mention that while i have a wireless router, it is also a 4 port gateway (ie, wireless and wired all in one). Now i just need to figure out how to deal with that...
ShoelessOne
23-01-2003, 20:02
oh, also i used mirc to /dns myself, and my ip address is still the same... firewall could be a problem.