Can't connect to server from the outside

[XA04]

Not usually like me to post a question related to something like this, but I'm very stumped..

Basically I'm running a teamspeak server at home (also BitTorrent and other services), but can't seem to connect from the outside. Within the LAN it's fine, but outside it's not.

Yes, I've forwarded the ports on my router...(UDP and TCP where applicible.. UDP for teamspeak) I've also tried disabling the software firewall, and I've also contacted my ISP to see if they were blocking anything (they weren't).

Any ideas?

[sadbuttrue]

I ran into the same problem when I first made the switch to Windows 7. It turned out that disabling the Windows Firewall service causes all incoming connections to get blocked. I've had to re-enable the service and turn the firewall off "the right way". Whoever coded the Windows firewall needs a firm kick up the backside.

[XA04]

Well so far I've tested it with Windows 7 but mainly I've been testing it on Server 2003.. I've added the relevant exceptions in the whitelist.. but to no avail

[chrestomanci]

Has your external IP address changed recently? You could be connecting to some one else's router.

Remember that on most routers you need to forward TCP/IP and UDP ports separately, Are you forwarding the correct protocol?

If all else fails, you might try installing another server, such as a basic web server, and seeing if that works OK, and then diagnosing from there.

Who is your ISP? Do their support personnel sound clueful? Is it possible that they are blocking ports, but their support people are lying or just don't understand the question.

[XA04]

Nope. It's static, and I have a domain name provided by the ISP too.

Yup, it's just one UDP port for teamspeak. But having the same problems with other services too, whether it's TCP or UDP.

I'll try an FTP server later, but I can't see it making any difference considering I can't use remote desktop/bit torrent or teamspeak from the outside..

ISP is plusnet, and although they have gone downhill over the years the customer service was excellent and the guy definitely knew what he was talking about... to the extent he probably knew more than me (which, not been big headed but stereo typing tech support) which is a surprise. He definitely told me that they're not blocking any ports on there side though.

He did suggest one thing, said it might be worth using wireshark to test if certain packets are at a lower priority or something. Can't remember exactly what he said, was gonna have a play about with it later..

[mightymouse]

what about creating a vpn using something like hamachi? would it work? personally i havent tried before but i would have thought it might help

[XA04]

what about creating a vpn using something like hamachi? would it work? personally i havent tried before but i would have thought it might help

Nothing from the outside can get in. I don't see how creating a VPN would work either..

[MaddAussie]

What router?

Have you tried a trace route/ping from external?

[Splash]

As MaddAussie says, what router are you using? The fact that you can connect fine from within your LAN suggests that it's not a software firewall (unless it's configured to trust LAN traffic...) interfering.

That said, I thought Teamspeak required both TCP and UDP ports? The UDP is the voice connection but you need a TCP port to connect to the server in the first place. Are you using TS or TS2?

[XA04]

What router?

Have you tried a trace route/ping from external?

Belkin F5D7632-4, V1. Quite an old one but has worked fine for years..

Not tried a trace route, will ask a friend to do it now.

As MaddAussie says, what router are you using? The fact that you can connect fine from within your LAN suggests that it's not a software firewall (unless it's configured to trust LAN traffic...) interfering.

That said, I thought Teamspeak required both TCP and UDP ports? The UDP is the voice connection but you need a TCP port to connect to the server in the first place. Are you using TS or TS2?

I'm using teamspeak version 3 I believe? Even still though, I can't connect via remote desktop on the outside, where as I used to be able to..

[Splash]

TS3 uses

Default voice port (UDP): 9987
Default filetransfer port (TCP): 30033
Default serverquery port (TCP): 10011

You need all of these forwarded to have it work - can you check these?

[Splash]

Even still though, I can't connect via remote desktop on the outside, where as I used to be able to..

Suggests something else might be up then. That said I don't think I'd risk opening RDP over the internet...

[XA04]

Trace route came back looking ok..

TS3 uses

Default voice port (UDP): 9987
Default filetransfer port (TCP): 30033
Default serverquery port (TCP): 10011

You need all of these forwarded to have it work - can you check these?

Forwarded filetransfer and server query.. still not working.

Suggests something else might be up then. That said I don't think I'd risk opening RDP over the internet...

Yeah. I'm pretty sure it's either to do with plusnet or my router. I've changed the default RDP port as I was a little paranoid about that too

[MSIC]

I cant remember with TS if you need to allocate a fixed IP within your LAN to the machine running the TS server, and then of course port forward to that IP.
I did this once (not with TS but something I cant remember) and then got stumped - found out that my desktop had decided to "jump ship" and leave the IP I had assigned, and get another (similar) one

[Splash]

Can you try something like ShieldsUp to check that the port forwarding is working correctly? Your LAN ip hasn't changed or anything silly like that has it?

[XA04]

I cant remember with TS if you need to allocate a fixed IP within your LAN to the machine running the TS server, and then of course port forward to that IP.
I did this once (not with TS but something I cant remember) and then got stumped - found out that my desktop had decided to "jump ship" and leave the IP I had assigned, and get another (similar) one

Can you try something like ShieldsUp to check that the port forwarding is working correctly? Your LAN ip hasn't changed or anything silly like that has it?

The machine I'm running the server on has a fixed IP. 100% sure it's not changed as I connect to it via RDP using the IP address.. checked via command prompt too.

Not sure what shieldsup is but I'll google it and get back to you.

Edit: Oh I've seen this before. Well it's saying port 9987 is stealth?