Results 1 to 11 of 11
Thread: Router :'(
-
17-01-2004, 03:00 #1
-= TeamSpeak User =-
- Join Date
- Jan 2004
- Location
- DK
- Posts
- 5
Router :'(
Hi
Here is my problem:
I've got this router from Linksys called BEFW11S4 and that is just fine
but the real problem is that I (My self) can't connect to my own server.
My IP is 192.168.1.100
Router IP is 80.165.128.182
And i am no magician with computeres (okay now i said that ...) But i need some help with configurating the server and my router because as i said me and computers... erh.. where is the power button?? j/k
-
17-01-2004, 07:34 #2
-= TeamSpeak User =-
- Join Date
- Dec 2003
- Location
- IL USA
- Posts
- 3
if you have the server and client on the same computer, you can connect to your loopback address of 127.0.0.1 or your local ip address 192.168.1.100.
Odd, I've tried using the same router you are and can't get it to forward packets at all. Can connect from within the lan just fine, but nobody from the outside can connect even tho ive forwarded 8767 udp and it has the latest firmware.
-
17-01-2004, 11:44 #3
-= TeamSpeak User =-
- Join Date
- Jan 2004
- Location
- DK
- Posts
- 5
I have also tried and tried to make it forward packets buth my pals cant connect to it. But i don't know what to do i am kinda lost you know... But there is only one think to do
keep trying..
Well i also tried with 127.0.0.1 but that didn't even work... So now i am really confused.. maybe i got what you said wrong... or maybe i am just not doing it right... Well thanks anyway
-
17-01-2004, 11:48 #4
-= TeamSpeak Fanatic =-
- Join Date
- Dec 2002
- Location
- Germany
- Posts
- 1,763
You cannot connect to the Server from the LAN using the LAN IP?
As long as that is not working forwarding a prot will make no difference.
Is there some error in the server log?
Please give a bit more info (server version, etc.. Just check the Forum Rules)
-
17-01-2004, 12:24 #5
-= TeamSpeak Addict =-
- Join Date
- Dec 2003
- Location
- holland
- Posts
- 703
From within the LAN, are you trying to connect to a TS server running on the same computer as the client. Or are we talking different boxes here. What operating system, any firwalls (XP) running by any chance?
-
17-01-2004, 12:25 #6
-= TeamSpeak User =-
- Join Date
- Jan 2004
- Location
- DK
- Posts
- 5
Ok now some of it is working
127.0.0.1 is working
And it is the same computer
Sever ver. 2.0.19.40
OS : Win Xp Pro
Server log ::
---------------------------------------------------------------
-------------- log started at 11-01-04 21:28 -------------
---------------------------------------------------------------
11-01-04 21:28:56,ALL,Info,server, Server init initialized
11-01-04 21:28:56,ALL,Info,server, Server version: 2.0.19.40 Win32
11-01-04 21:28:56,WARNING,Info,SQL, created table ts2_servers
11-01-04 21:28:56,WARNING,Info,SQL, created table ts2_channels
11-01-04 21:28:56,WARNING,Info,SQL, created table ts2_clients
11-01-04 21:28:56,WARNING,Info,SQL, created table ts2_channel_privileges
11-01-04 21:28:56,WARNING,Info,SQL, created table ts2_server_privileges
11-01-04 21:28:56,WARNING,Info,SQL, created table ts2_bans
11-01-04 21:28:56,ALL,Info,server, Starting server with port: 8767
11-01-04 21:28:56,WARNING,Info,SERVER, Default Server created
11-01-04 21:28:56,WARNING,Info,SERVER, admin account info: username: admin password: yqnya5
11-01-04 21:28:56,WARNING,Info,SERVER, superadmin account info: username: superadmin password: swzy3u
11-01-04 21:28:57,ALL,Info,server, Server init finished
11-01-04 21:29:54,ERROR,All,frmMain, unable to detect external ip
11-01-04 21:34:40,ERROR,All,frmMain, unable to detect external ip
12-01-04 00:18:24,ALL,Info,server, Server shutdown initialized
12-01-04 00:18:26,ALL,Info,server, Server shutdown finished
---------------------------------------------------------------
--------------- log ended at 12-01-04 00:18 --------------
---------------------------------------------------------------
---------------------------------------------------------------
-------------- log started at 17-01-04 02:00 -------------
---------------------------------------------------------------
17-01-04 02:00:20,ALL,Info,server, Server init initialized
17-01-04 02:00:20,ALL,Info,server, Server version: 2.0.19.40 Win32
17-01-04 02:00:21,ALL,Info,server, Starting server with port: 8767
17-01-04 02:00:21,ALL,Info,server, Server init finished
17-01-04 02:00:25,ERROR,All,frmMain, unable to detect external ip
17-01-04 02:15:25,ALL,Info,server, Starting server with port: 6112
17-01-04 02:15:53,ALL,Info,server, Starting server with port: 6112
17-01-04 04:01:24,ALL,Info,server, Server shutdown initialized
17-01-04 04:01:26,ALL,Info,server, Server shutdown finished
---------------------------------------------------------------
--------------- log ended at 17-01-04 04:01 --------------
---------------------------------------------------------------
---------------------------------------------------------------
-------------- log started at 17-01-04 04:24 -------------
---------------------------------------------------------------
17-01-04 04:24:23,ALL,Info,server, Server init initialized
17-01-04 04:24:23,ALL,Info,server, Server version: 2.0.19.40 Win32
17-01-04 04:24:23,ALL,Info,server, Starting server with port: 8767
17-01-04 04:24:23,ERROR,All,SERVER, Server startup failed with port 8767, Exception: EIdSocketError.Socket Error # 10049
Cannot assign requested address.
17-01-04 04:24:23,ALL,Info,server, Starting server with port: 6112
17-01-04 04:24:23,ERROR,All,SERVER, Server startup failed with port 6112, Exception: EIdSocketError.Socket Error # 10049
Cannot assign requested address.
17-01-04 04:24:23,ERROR,All,WEBINTERFACE, WebInterface startup failed with port 14534, Exception:Socket Error # 10049
Cannot assign requested address.
17-01-04 04:24:23,ERROR,All,TCPQUERY, TCPQuery startup failed with port 51234, Exception: Socket Error # 10049
Cannot assign requested address.
17-01-04 04:24:23,ALL,Info,server, Server init finished
17-01-04 04:24:26,ERROR,All,frmMain, unable to detect external ip
---------------------------------------------------------------
-------------- log started at 17-01-04 12:40 -------------
---------------------------------------------------------------
17-01-04 12:40:45,ALL,Info,server, Server init initialized
17-01-04 12:40:45,ALL,Info,server, Server version: 2.0.19.40 Win32
17-01-04 12:40:45,ALL,Info,server, Starting server with port: 8767
17-01-04 12:40:46,ALL,Info,server, Starting server with port: 6112
17-01-04 12:40:46,ALL,Info,server, Server init finished
17-01-04 12:40:49,ERROR,All,frmMain, unable to detect external ip
17-01-04 12:42:00,ERROR,All,frmMain, unable to detect external ip
17-01-04 12:45:02,ALL,Info,server, Server shutdown initialized
17-01-04 12:45:04,ALL,Info,server, Server shutdown finished
---------------------------------------------------------------
--------------- log ended at 17-01-04 12:45 --------------
---------------------------------------------------------------
17-01-04 12:45:04,ALL,Info,server, Starting server with port: 8767
17-01-04 12:45:04,ALL,Info,server, Starting server with port: 6112
17-01-04 12:45:04,ALL,Info,server, Server init finished
17-01-04 12:45:07,ERROR,All,frmMain, unable to detect external ip
17-01-04 12:47:51,ALL,Info,server, Server shutdown initialized
17-01-04 12:47:54,ALL,Info,server, Server shutdown finished
---------------------------------------------------------------
--------------- log ended at 17-01-04 12:47 --------------
---------------------------------------------------------------
---------------------------------------------------------------
-------------- log started at 17-01-04 12:48 -------------
---------------------------------------------------------------
17-01-04 12:48:33,ALL,Info,server, Server init initialized
17-01-04 12:48:33,ALL,Info,server, Server version: 2.0.19.40 Win32
17-01-04 12:48:33,ALL,Info,server, Starting server with port: 8767
17-01-04 12:48:33,ALL,Info,server, Starting server with port: 6112
17-01-04 12:48:33,ALL,Info,server, Server init finished
17-01-04 12:48:37,ERROR,All,frmMain, unable to detect external ip
TSClient.log
---------------------------------------------------------------
-------------- log started at 17-01-04 12:40 -------------
---------------------------------------------------------------
17-01-04 12:41:20,3504,WARNING,All,procedure TClientReadThread.Execute,Socket Error # 10054
Connection reset by peer.
17-01-04 12:41:23,3388,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
17-01-04 12:41:38,3504,WARNING,All,procedure TClientReadThread.Execute,Socket Error # 10054
Connection reset by peer.
17-01-04 12:41:41,3388,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
17-01-04 12:41:41,3588,WARNING,All,procedure TDICallBack.execute,"The operation had no effect." or "The device buffer overflowed and some input was lost." or "The device exists but is not currently attached." or "The change in device properties had no effect."
17-01-04 13:04:19,3388,ERROR,ProcedureInfo,Client Open,Exception: Bad login
17-01-04 13:04:24,3388,ERROR,ProcedureInfo,Client Open,Exception: Bad login
17-01-04 13:05:35,3388,ERROR,ProcedureInfo,Client Open,Exception: Bad loginLast edited by Stammer; 17-01-2004 at 12:30.
-
17-01-2004, 12:55 #7
-= TeamSpeak Fanatic =-
- Join Date
- Dec 2002
- Location
- Germany
- Posts
- 1,763
From the Socket error 10049 I suspect that you tried to fiddle around with the BoundToIP in the server.ini.
And you did get the error propabley because you tried to enter your external IP there. Am I correct?
If so, it seems that you don't know what you are doing there. If you don't know what you are doing leave it open.
I assume that you currently have entered 127.0.0.1 there. That would explain why only 127.0.0.1 works. Since you cannot forward to 127.0.0.1 no forwarding rule that you enter at your router will work.
Leave the BoundToIP open (which basically means that the server will answer on any IP that is assigned to your computer) and make a forwarding rule with a destination IP of the LAN IP of the TS server.
(It seems that you have two server instances up, one on 8767 and one on 6112. So you will need two forwarding rules, one with port 8767 UDP and one with port 6112 UDP)
If it still does not work, change the log level in the TS client to debug (Settings -> Options -> Other -> Log Options), restart the cilent to make the setting active, and post the client log here.
EDIT: You can ignore 11-01-04 21:29:54,ERROR,All,frmMain, unable to detect external ip. If you want to get rid of that message you can set ExternalIPDetecion=0 in the server.ini.
EDIT2: Change your passwords. You accidently posted them with your server.log.Last edited by Dummer Sack; 17-01-2004 at 12:57.
-
17-01-2004, 13:06 #8
-= TeamSpeak User =-
- Join Date
- Jan 2004
- Location
- DK
- Posts
- 5
Ok now BoundToIP=(nothing)
and 127.0.0.1 still works
and only on server is running now at 8767
password changed
and routing is done to...
-
17-01-2004, 13:08 #9
-= TeamSpeak User =-
- Join Date
- Jan 2004
- Location
- DK
- Posts
- 5
Doesn't work

Server log :
17-01-04 14:04:02,ALL,Info,server, Server init initialized
17-01-04 14:04:02,ALL,Info,server, Server version: 2.0.19.40 Win32
17-01-04 14:04:02,ALL,Info,server, Starting server with port: 8767
17-01-04 14:04:03,ALL,Info,server, Server init finished
17-01-04 14:04:06,ERROR,All,frmMain, unable to detect external ip
TSClient.log :
17-01-04 14:01:06,2496,DEBUG,All,Startup,Client version 2.0.32.60
17-01-04 14:01:06,2496,DEBUG,ProcedureInfo,Client Open,Creating and starting threads
17-01-04 14:01:06,2496,DEBUG,All,TDSoundIn.Open,opend direct Capture 8bit=0 , 11khz=1
17-01-04 14:01:17,2496,DEBUG,ProcedureInfo,Client Open,host 80.165.128.182 resolved to 80.165.128.182
17-01-04 14:01:17,2496,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
17-01-04 14:01:17,2496,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
17-01-04 14:01:17,444,WARNING,All,procedure TClientReadThread.Execute,Socket Error # 10054
Connection reset by peer.
17-01-04 14:01:20,2496,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
17-01-04 14:06:33,2496,DEBUG,ProcedureInfo,Client Open,host 80.165.128.182 resolved to 80.165.128.182
17-01-04 14:06:33,2496,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
17-01-04 14:06:33,2496,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
17-01-04 14:06:33,444,WARNING,All,procedure TClientReadThread.Execute,Socket Error # 10054
Connection reset by peer.
17-01-04 14:06:36,2496,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
17-01-04 14:06:36,3996,WARNING,All,procedure TDICallBack.execute,"The operation had no effect." or "The device buffer overflowed and some input was lost." or "The device exists but is not currently attached." or "The change in device properties had no effect."
-
17-01-2004, 13:58 #10
-= TeamSpeak Fanatic =-
- Join Date
- Dec 2002
- Location
- Germany
- Posts
- 1,763
So the only thing that works is 127.0.0.1?
The forwarding is of no use as long as you cannot connect to the LAN IP (192.168.x.x).
Have you got a firewall running (remeber that XP has a built in one). If yes, try to disable it and check if then you can connect then to the LAN IP.
-
01-06-2005, 07:49 #11
-= TeamSpeak User =-
- Join Date
- Jun 2005
- Location
- United States
- Posts
- 7
I thought I would direct you to my post here:
http://forum.goteamspeak.com/showthr...8278#post98278
It might help.
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Similar Threads
-
A router friendly TeamSpeak!
By MrStolpe in forum [TeamSpeak Classic] General QuestionsReplies: 22Last Post: 26-07-2005, 12:23 -
WIN2k Server / Linksys Router Problem
By XForce007 in forum [TeamSpeak 2] Server SupportReplies: 1Last Post: 14-09-2002, 10:48 -
Another Router Question. . .
By ReaverXR in forum [TeamSpeak Classic] General QuestionsReplies: 2Last Post: 22-07-2002, 08:18 -
Router
By SHADOWOLF in forum [TeamSpeak Classic] General QuestionsReplies: 1Last Post: 13-07-2002, 16:34


Reply With Quote