Thanks for the information guys, I really appreciate it!

I just got off the phone to orange and an extremely unhelpful helper basically said it wasn't possible to portforward with orange, never will I use this company again (but unfortunately I'm not in control of our ISP choice here ).

Edit: To answer your previous question I have a DGN1000. And now you've provided those DNS codes (which is all I wanted from orange but that was too much apparently) I'll give it another shot just incase.

Edit2: Tried this again using the provided information (thanks for that), but it didn't work. Seems like pretty much nothing I do is opening ports, would be nice to hear from anyone else using Orange who's had success.

Edited by deleted (Thu 07-Jun-12 19:23:22)

It's not an Orange issue. It is solely down to configuring the router correctly, with any ISP..

Well, i've put in those DNS codes following the guide (under network connections along with the subnet mask/IP/default gateway) and it's not working

Thanks for the advice anyway

Edit: Just to give a bit more detail, oddly the internet did continue to work for half an hour or so but then stopped completely on this unit, the validation tool within the network connections menu said the DNS servers weren't responding.

Edited by deleted (Thu 07-Jun-12 19:51:01)

I told you before, do everything on the router and put the PCs back to Auto.

Your way's not working probably cuz you've caused a clash with the router.

F.A.O Johnybenson

Hello, you need to stop what your doing. and read what the others have said in their reply's.

The person at Orange is completely right, they have nothing to do with portforwarding. Portforwarding is what you do inside your own house.

DNS = Domain Name System.
What it is used for is translating a website address like www.thinkbroadband.com into an IP address/number. Computer games dont use DNS to connect to game servers, they use either the IP address, or some kind of matchmaker service which niether ways use the DNS. Changing the DNS settings has nothing to do with your problem, your just adding a new problem.

Portforwarding is used, when you have a webserver or you are directly hosting a game inside your house, and you want everybody else in the world to be able to connect to it.

My recommendation is you should put everything back on automatic, then run a ping/tracert test to the IP address your trying to connect to through a dos command prompt. At the momment, no one can advise you properly, because you've changed all the wrong settings.

I can only apologise if it seems I'm ignoring people, I've just found myself quite confused by the whole thing. Anyway, I've gone back and made sure everything's reset as it was, both on the laptop and the router.

Here's a trace route for connecting to the D3 log on server (which was the application I mentioned trying to run but being unable to connect):

C:\Users\xx>tracert eu.logon.battle.net

Tracing route to eu.logon.battle.net [213.248.127.130]
over a maximum of 30 hops:

1 * 2699 ms * 192.168.0.1
2 22 ms 21 ms 21 ms 213.1.112.216
3 * 2360 ms * 213.1.117.126
4 * 820 ms * 213.1.67.238
5 * 2340 ms * 213.1.78.252
6 * 2360 ms * 213.1.79.34
7 * 2124 ms * 87.237.20.240
8 * 1125 ms * bundle-ether1.lontr1.London.opentransit.net [193
.251.255.101]
9 1154 ms * 1307 ms telia.GW.opentransit.net [193.251.251.22]
10 * 1536 ms * ldn-bb1-link.telia.net [80.91.247.91]
11 721 ms * 1293 ms prs-bb1-link.telia.net [213.155.134.40]
12 * 1520 ms * ffm-bb1-link.telia.net [80.91.245.104]
13 862 ms * 1197 ms ffm-b10-link.telia.net [80.91.247.185]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out..
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Again I'd like to just say thanks for the help, I'll make sure to read everything thoroughly and not go jumping into making changes from now on!

Edit: Apologies for the layout of the tracert, can't seem to line it up properly - hope it's alright

Edited by deleted (Thu 07-Jun-12 22:23:46)

Ok, now we are getting some where, the tracert is showing there is a huge lag/latency problem between your laptop and the router.

Turn the wifi off on your laptop and plug it in directly to the router using the ethernet cable, as the ping time (*2699 ms) is unbelieveably high and maybe caused if your using wifi. Normal ping to your own router should be about 1ms.

Some gameservers wont let you join if your pings are to high, which yours is.
(mainly in online shoot em ups) basically if you have high lag/latency, the person you are shooting at will of gone/moved long before your bullet gets to the location where you think he was standing.

Edited by deleted (Thu 07-Jun-12 23:00:04)

In reply to a post by johnybenson:

using a DNS I've got for orange online -
(Primary DNS: 195.92.195.94
Secondary DNS: 195.92.195.95)

Where you get these? They don't even belong to Orange; they belong to Energis UK, altho' they could well be DNSs.

Ger rid of these at once everywhere.

Change in the router to the ones given by E7er, or better still let it "Obtain from ISP", and set all PCs to Auto Obtain both DNS and IP addy.

The setting of these DNS have no bearing on your gaming issue, as was pointed out, but will affect and slow all your other Internet look ups.

OMG! Well spotted!

This is how it should look:

C:\>tracert eu.logon.battle.net

Tracing route to eu.logon.battle.net [213.248.127.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms OrangeRouter [192.168.1.1]
2 28 ms 28 ms 27 ms 213.1.112.200
3 29 ms 28 ms 28 ms 213.1.117.61
4 30 ms 29 ms 28 ms 213.1.67.230
5 30 ms 30 ms 30 ms 213.1.78.252
6 30 ms 29 ms 30 ms 213.1.79.22
7 30 ms 31 ms 29 ms 87.237.20.240
8 33 ms 31 ms 31 ms bundle-ether1.lontr1.London.opentransit.net [193.251.255.101]
9 30 ms 30 ms 30 ms telia-2.GW.opentransit.net [193.251.252.78]
10 31 ms 30 ms 30 ms ldn-bb2-link.telia.net [80.91.247.93]
11 37 ms 38 ms 37 ms prs-bb2-link.telia.net [80.91.247.240]
12 46 ms 46 ms 45 ms ffm-bb2-link.telia.net [80.91.246.182]
13 57 ms 76 ms 44 ms ffm-b10-link.telia.net [80.91.251.250]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Don't worry about it timing out later. These nodes probably won't respond to pings.