PDA

View Full Version : D-Link router, client unable to connect via Internet


WiglyWorm
11-08-2006, 07:40
Alright, I've read the FAQ's, the stickies, and quite a few threads that popped up in search (besides that I'm A+ and Network+ certified). If I were using a Lynksis router, I might have even found something to help me out, but I'm using D-Link (DI-524).

I can connect just fine over the LAN, but when I try to have some friends connect via the WAN, they get the standard "maybe teamspeak is not running" message for when the server can't be found.

I have tried absolutely everything my router allows: Virtual Server, Special Apps, making exceptions in the hardware firewall. Making exceptions in my software firewall (just the windows firewall), turning off my software firewall, putting my server in the DMZ, adding stuff to my server.ini file.

I'm using RC2 2.0.20.1, and yes, I promise I'm giving out my public I.P., not my internal I.P.

Neither my friends, nor that script in the FAQ can connect.

So... If I can get any sort of pointers, I'd be most appreciative.

Patchank
11-08-2006, 20:08
ports forwarded too ?

WiglyWorm
11-08-2006, 23:51
Indeed.

I've spent some time on the phone with D-Link, and they haven't provided anything helpful... so just a couple minutes ago, I connected my server PC directly to the DSL modem. It worked perfectly.

so, there's something with the router.

On that note, I don't really see this being relevant, but just in case: my server is connected to my router wirelessly, would that be an issue?

Ryan Macintosh
12-08-2006, 00:28
Indeed.

I've spent some time on the phone with D-Link, and they haven't provided anything helpful... so just a couple minutes ago, I connected my server PC directly to the DSL modem. It worked perfectly.

so, there's something with the router.

On that note, I don't really see this being relevant, but just in case: my server is connected to my router wirelessly, would that be an issue?

wow i have the same problem same router, im still playing with it to see if i can get it working if i can i'll post back

WiglyWorm
12-08-2006, 05:44
Oi vey.

I've been escelated beyond tier 2 tech support to a "product specialist" with D-Link. I guess they're going to call me monday or tuesday. T_T

Any input would still be greatly appreciated, because I don't feel too confident.

Is there anything at all on the TeamSpeak Server application side that I could be missing?

Ryan Macintosh
12-08-2006, 17:08
Oi vey.

I've been escelated beyond tier 2 tech support to a "product specialist" with D-Link. I guess they're going to call me monday or tuesday. T_T

Any input would still be greatly appreciated, because I don't feel too confident.

Is there anything at all on the TeamSpeak Server application side that I could be missing?

i didn't cya anything last time i checked but i could have missed something, i'll look again

Ryan Macintosh
12-08-2006, 20:38
i didn't cya anything last time i checked but i could have missed something, i'll look again



you try the Application? under Adavence Tab? i just tryed it now and my friend say it not working but not sure

WiglyWorm
13-08-2006, 04:23
Yes, I've set it up under virtual server, special apps, firewall, and even put it in the DMZ. Nothing has worked.

Ryan Macintosh
13-08-2006, 05:42
Yes, I've set it up under virtual server, special apps, firewall, and even put it in the DMZ. Nothing has worked.


:confused: :confused: :confused: , let me know monday or tuesday what the guy says would ya? thanks

Ryan Macintosh
13-08-2006, 06:05
FOUND IT!!!!! well i found it in the foums

works for me:):) have fun

quto from hTIG
post http://forum.goteamspeak.com/showthread.php?t=15092

Now you want to look for Forwarding, or Port Forwarding it may even be Virtual Server, UPnP Port Forwarding or Port Range Forwarding. Any of these Should work....You may have to click on advanced setup to find this.
Once you have the port number entered and made sure that it is set to UDP and or TCP. You have to froward the port to the right LAN ip. That means setting it to the LAN ip of the machine running the server program. If your LAN ip is (example) 192.168.1.101 then you would enter 192.168.1.101 into the ip box provided.

Once you find this you can enter the required ports that it takes to operate TS server behind a router. These ports are: 8767 UDP, 14534 TCP, 51234 TCP.

All you should have to open is UDP port 8767, the others should only be pen when REALLY necessary (possible security risk).

The page may have a bunch of boxes lined up in a rows and or colums, or have a single box. You may have to even name it. If so there will be a box provided to do so. You cant use the same name more than once either. So that means you will have to name each port something different from each other.

Sometimes you may even have to provide a port trigger. Normally this is the port that you are trying to open. So if you need a port trigger for port 8767 UDP. The trigger should be 8767. And such for any other port that you want to open.

Now for the WAN part of this. Your router will have a WAN address. Such as example: 12.178.135.153. This is the ip address(WAN address) that you want to give out to other people!! You can find this ip by going to the status page on router. If you cant find it. Call your customer service number in the manual for your router. Or call your Internet Service Provider.

You can use your LAN ip to join your server that you are hosting on your PC. But to get other people on it you need to give them your WAN address.

This guide is for TS server. Not the Client!!
Think of it this way.. the server is the meeting point of all the people that you want to talk to. The client is what you use to talk with...


EDITED by Guldi: Removed port 8768 TCP as 1) TS per default uses only 8767 UDP and 2) there is def. no need for a 8768 TCP port 3) added a security warning for opening the TCPQuery & webinterface port.

WiglyWorm
13-08-2006, 06:14
Hm, this works for you?

*sigh*

Like I said in my first post, this didn't work for me at all.

Ryan Macintosh
13-08-2006, 08:39
Hm, this works for you?

*sigh*

Like I said in my first post, this didn't work for me at all.


WTF? Same router, same config? cable?, i don't get it:confused:

Ryan Macintosh
13-08-2006, 08:41
WTF? Same router, same config? cable?, i don't get it:confused:

Could you put Remote Access on, and maybe i could take a look? just a though, my email is ryan.macintosh*********** if ya want it, its my msn to

WiglyWorm
13-08-2006, 19:06
I don't have MSN... I see you have a gmail adress, do you have googletalk installed?

Ryan Macintosh
15-08-2006, 06:47
I don't have MSN... I see you have a gmail adress, do you have googletalk installed?


yes and no, i can install it, sorry i havn't posted a quick repuly been busy. school starts next week.:mad:

Ryan Macintosh
15-08-2006, 16:12
its installed

Bisa_Mithek
22-08-2006, 11:25
Guys, I'm running a DI-624 and I have the same problem :( ... well, not exactly the same, you see, some people never have problems conecting, others can connect one day but not the other day :confused:

To solve this, all I have to do is (strange enough?!) reboot my router ...

I'm not sure this might help but try it :)

(btw, if any1 could come up with a better more stable solution Im ready to worship you ^_^)

GIBS77
16-10-2006, 17:04
I don't know if you fixed it yet. :confused:
I have a DI-624+ and had the same problem.
Maybe you have set the portforwarding right but you can check here (http://www.portforward.com/english/routers/port_forwarding/Dlink/DI-524/TeamSpeak.htm)how it should be.
I only forwarded port 8767 in the beginning, but when I did the rest to and it worked for me.

Good luck :)

(On portforward.com (http://www.portforward.com/routers.htm) you can find guides how to "portforward" many routers and progs)

Reedy Boy
16-10-2006, 21:23
I don't know if you fixed it yet. :confused:
I have a DI-624+ and had the same problem.
Maybe you have set the portforwarding right but you can check here (http://www.portforward.com/english/routers/port_forwarding/Dlink/DI-524/TeamSpeak.htm)how it should be.
I only forwarded port 8767 in the beginning, but when I did the rest to and it worked for me.

Good luck :)

That link should be very useful for people

Thanks for posting it!!

:)