NTL blocking DNS2GO port 1227?

[smileblack]

I've been running DNS2GO for some time to give myself a fixed IP address. Yesterday morning, the DNS2GO client which runs on my PC started to fail to connect to DNS2GO. I believe it connects on port 1227 to tell DNS2GO's servers my current IP address. Technical support at DNS2GO are at a loss to explain this failure. I have tried installing the software on a second computer, lowering my firewalls etc. but have not succeeded in fixing the problem.

Is anyone else running DNS2GO and having problems? I half wonder if NTL has started blocking port 1227...

Nigel.

[Paul]

ntl do not block any ports other than the following (all inbound only).

137 (UDP), 138 (UDP), 139 (TCP), 445 (UDP & TCP), 593 (TCP), 1433 (TCP), 1434 (UDP), 27374 (TCP)

[smileblack]

That's a shame. Blaming NTL was such an easy solution ;)

[Bill C]

That's a shame. Blaming NTL was such an easy solution ;)

So who are you going to blame next ;)

[daxx]

NTL, cause mines not working either on NTL connection, works fine on all BT connections

[Bill C]

NTL, cause mines not working either on NTL connection, works fine on all BT connections

How can it be NTL if they do not block that port. And they DO NOT BLOCK THAT PORT can i make that any clearer

[dilli-theclaw]

How can it be NTL if they do not block that port. And they DO NOT BLOCK THAT PORT can i make that any clearer

Perhaps if you use bold and bigger font ;):)

[Bill C]

How can it be NTL if they do not block that port. And they DO NOT BLOCK THAT PORT can i make that any clearer


Done :LOL:

[smileblack]

I understand what you are saying about NTL not blocking port 1227 but I'm still reluctant to take NTL off my list of suspects. It could be NTL or DNS2GO or my set-up although now I have evidence of two people for who DNS2GO works with BT but has stopped working with NTL, I'm heading back in the NTL direction!

What would be useful if someone with NTL can report that DNS2GO is still working... (although that would confuse issues further).

Nigel.

[poolking]

Have you opened up the correct port in your firewall?

[Paul]

What ip are you trying to connect to ?

[Chrysalis]

can anyone confirm if port 1025 is NOT blocked please as I cannoot recieve any traffic on port 1025 since yesterday, I was logged into a ssh session on a server which has port 1025 set for ssh then suddenly the connection died and attempts kept timing out. I did a tcpdump and it seems the syn-acks were not getting back to me and this is still the case so my client kept sending syns, as soon as we changed the port all was well again, and I did reboot my pc and disable firewall.

[damoritz]

Hi


I am having exactly the same problem. Ever since Wednesday morning my DNS2go client will not connect. No machines on my network will connect yet deerfield say eveything is fine - please help someone!!

Thanx
David

[Paul]

See post #2, there can be a number of causes of network connectivity problems, but those ports are not blocked.

[Chrysalis]

can confirm both 1227 and 1025 open, 1025 I wonder was a temporary problem maybe ntl had to block.

[smileblack]

This is looking like an NTL problem. Ok, so perhaps port 1227 is not blocked but maybe there are other NTL issues. Not knowing the full details of how DNS2GO works, I cannot guess what these may be.

If one person on NTL could put their hand up and say, "DNS2GO works" then perhaps I would believe it is a local problem but as my firewall is down and the failure occurred on a PC I don't normally touch (and I have tried running the software on a second PC), I'm suspicious. It's been running for over a year and suddenly it dies without me touching the PC concerned.

The server that DNS2GO tried to contact is discovery.dns2go.com. It maps to a number of different IP addresses.

All very strange.

Nigel.

[Eusa]

Just testing 1 of the 4 IPs.

From NTL.

Tracing the path to 207.89.233.94 on TCP port 1227, 30 hops max

<deleted>

7 tele-ic-1-so-010-0.inet.ntl.com (62.253.185.82) 14.999 ms 15.686 ms 14.283 ms
8 212.250.14.62 (212.250.14.62) 15.424 ms 13.938 ms 13.743 ms
9 p10-0.core01.bos01.atlas.cogentco.com (130.117.0.46) 112.228 ms 88.477 ms 94.683 ms
10 p5-0.core01.ord01.atlas.cogentco.com (66.28.4.110) 109.183 ms 109.024 ms 111.010 ms
11 g0-1.na01.b002281-1.ord01.atlas.cogentco.com (66.28.66.206) 111.382 ms 109.259 ms 109.660 ms
12 FREE (66.250.7.38) 109.550 ms 109.282 ms 109.146 ms
13 4-16.atm6-0.rtr1.lnng.mi.core.com (169.207.224.34) 161.837 ms 206.427 ms 245.006 ms
14 se0.wb4132.gylr.mi.core.com (207.89.129.54) 126.529 ms 126.591 ms 126.742 ms
15 * * *
16 * *

From not NTL

Tracing the path to 207.89.233.94 on TCP port 1227, 30 hops max

<deleted>

7 ae-1-0.bbr2.London1.Level3.net (212.187.128.57) 23.737 ms 23.237 ms 24.732 ms
8 as-0-0.bbr1.NewYork1.Level3.net (4.68.128.106) 89.004 ms 89.005 ms 88.008 ms
9 as-1-0.bbr1.Chicago1.Level3.net (64.159.0.237) 110.194 ms 110.760 ms
ae-0-0.bbr2.Chicago1.Level3.net (64.159.1.34) 110.191 ms
10 ge-9-0.ipcolo1.Chicago1.Level3.net (4.68.101.10) 113.639 ms
ge-7-2.ipcolo1.Chicago1.Level3.net (4.68.101.170) 111.064 ms
ge-9-0.ipcolo1.Chicago1.Level3.net (4.68.101.10) 107.636 ms
11 unknown.Level3.net (63.208.138.174) 112.088 ms 108.770 ms 109.506 ms
12 4-16.atm6-0.rtr1.lnng.mi.core.com (169.207.224.34) 114.529 ms 117.439 ms 116.517 ms
13 se0.wb4132.gylr.mi.core.com (207.89.129.54) 125.204 ms 129.635 ms 125.913 ms
14 207.89.233.94 (207.89.233.94) [open] 125.179 ms 123.841 ms 133.172 ms

Looks more like NTL (or chunks of the NTL user ip space) are being blocked by DNS2GO, or their immediate upstream than the other way round.
Since only 1 of the 4 even pings, but all connect on TCP/1227 from another ISP, they are much with the firewalling, and the packets and the floor, and the tidyup. No issues here. Return to your home.

[criptopus]

Hello fellow sufferers I too am suffering from the same malady. I am unable to connect to port 1227 of discovery.dns2go.com but I can connect (after a long pause) to port 57 of discovery.dns2go.com. This dns2go told me to do and to contact my ISP if I could and ask them why they where blocking the port.

[Keytops]

Since only 1 of the 4 even pings, but all connect on TCP/1227 from another ISP, they are much with the firewalling, and the packets and the floor, and the tidyup. No issues here. Return to your home.

huh? :erm: :idea:

[Paul]

I have tested connecting to port 1227 on a server of mine, from my ntl connection, and it's fine.

[keety]

Hello chaps..


I too have the same problem. I've been onto Deerfield and they have said that its (1227) being blocked by NTL and that they are in dicussion with NTL about the matter at the moment.

Keety

[murfitUK]

Same problem here. Can't connect to port 1227 and Deerfield support team insist it is because NTL are blocking.

[sleepless]

Hello fellow sufferers I too am suffering from the same malady. I am unable to connect to port 1227 of discovery.dns2go.com but I can connect (after a long pause) to port 57 of discovery.dns2go.com. This dns2go told me to do and to contact my ISP if I could and ask them why they where blocking the port.

I would also like to know why they are being blocked :confused:

[Toto]

I would also like to know why they are being blocked :confused:

Hmm,

Why not use their facility to get round port blocking, got this from their front page.

DNS2Go is a Dynamic DNS service that enables any Internet user to host
their own domain name, even if they have a dynamic IP address (one that changes periodically). The installation of a small piece of software on the host computer allows the DNS2Go service to track the computer's IP address - no matter how often it changes. The DNS2Go service then ensures that the user's domain name always points to the host PC. DNS2Go even works behind firewalls and routers, and offers facilities for getting around ISP port blocking.

[smileblack]

It's this software that we are all complaining doesn't work.

The lastest response I've had from DNS2GO is:

The trace route will time-out for discovery.dns2go.com at our firewall because we are blocking ICMP packets.

The fact that you are able to connect from one ISP but not another is an indication the particular ISP is experiencing or enforcing some sort of routing / block.

For a trace route, you would need to trace the DNS2Go router IP addresses:
207.89.233.1
198.31.34.1
63.149.6.1

Thank you for the various forum posts. Even though NTL may not be actively "blocking" any ports, they could be experiencing a route issue when routing the connection to the DNS2Go servers.

I have come across about a dozen or so users from the UK and the Netherlands that are experiencing the exact same issue, and by viewing their current IP addresses, it would appear they are linked to NTL.

[Toto]

It's this software that we are all complaining doesn't work.

The lastest response I've had from DNS2GO is:

The trace route will time-out for discovery.dns2go.com at our firewall because we are blocking ICMP packets.

The fact that you are able to connect from one ISP but not another is an indication the particular ISP is experiencing or enforcing some sort of routing / block.

For a trace route, you would need to trace the DNS2Go router IP addresses:
207.89.233.1
198.31.34.1
63.149.6.1

Thank you for the various forum posts. Even though NTL may not be actively "blocking" any ports, they could be experiencing a route issue when routing the connection to the DNS2Go servers.

I have come across about a dozen or so users from the UK and the Netherlands that are experiencing the exact same issue, and by viewing their current IP addresses, it would appear they are linked to NTL.


Well. lets hope you can get it sorted, although I'm at a loss to explain why a user in the Netherlands is having a problem, he shouldn't be on the NTL network unless of course he is tunelling through an ntl IP address.

[Eusa]

The lastest response I've had from DNS2GO is:

The trace route will time-out for discovery.dns2go.com at our firewall because we are blocking ICMP packets.


If that was refering to my tcptraceroute output, then all I can say is

*sigh*

"Tracing the path to 207.89.233.94 on TCP port 1227, 30 hops max"

vs

"will time-out ... because we are blocking ICMP packets"

I give up.

[damoritz]

I have emailed NTL yesterday and told them that many of us are experiencing problems but to this moment in time, no reply. I will try calling them today and post the outcome

[ProfPete]

I have come across about a dozen or so users from the UK and the Netherlands that are experiencing the exact same issue, and by viewing their current IP addresses, it would appear they are linked to NTL.

What do you mean linked by linked to ntl? Just because the IP ranges are similar doesn't mean they are linked, as they all cope from the RIPE allocation.

If you have a better reason, please share it, as it would be interesting to investigate any patterns.

[criptopus]

Me: I understand you are blocking port 1227, can you explain why?

NTL: O sir, we don't block ports here at NTL, oh no sir, definatly not sir.

Me: Well I have telneted from my NTL account and from my BT account and I am afraid it speaks for its self.

NTL: O sir, we don't block ports here at NTL, oh no sir, definatly not sir. (repeat)

Me: Well then we are not agreeing, where do we go from here.

NTL: (you guessed it, repeat)

Me (ears beginning to close up): Check this site out http://www.ntlworld.com/tunnel.php?task=portBlocking maybe you do block some ports.

NTL (short silence): Only to protect from viruses, sir.

Me: But you said you didn't block ports?

NTL (short silence): Only to protect from viruses, sir. (repeat)

Me: So if you said you didn't block ports and now you do you may even block port 1227, is that not a possibility.

NTL (obviously had it!): If you would like to ring back later when the system is up and running and we can access your account data I would be be able to esculate this to a higher level for you sir.

Me: I think that maybe appropiate, bye for now........

[Paul]

Which part of "NTL DO NOT BLOCK PORT 1227" do you find hard to understand ?

I have tested connections to THREE of my servers, both uk and us based, on port 1227, and they are all working fine.

If there is a problem then it is NOT due to port blocking. :)

[criptopus]

Well it does look like the EQ (Encephalization Quotient) of NTL is significantly lower than first thought. It was said that a dinosaur could not feel a bit in the bum for a good few seconds after it was struck. I wonder if this is a similar case with NTL as they didn't realise they blocked ports, they may be even slower to block them through out the company. More may follow, lol.

[Chrysalis]

the port doesnt seem to be blocked, but there looks like there is a routing issue from ntl be it accidental or deliberate, the problem is too advanced for normal tech support to deal with I wonder if ignition or monkeybreath could shed some light on this.

[criptopus]

Supervisor at NTL has instructed me to download ssh !#? what ever that is to solve this problem. Something about tunneling I think. Anybody used this software on Windows XP?

[Toto]

Well it does look like the EQ (Encephalization Quotient) of NTL is significantly lower than first thought. It was said that a dinosaur could not feel a bit in the bum for a good few seconds after it was struck. I wonder if this is a similar case with NTL as they didn't realise they blocked ports, they may be even slower to block them through out the company. More may follow, lol.


Tisk tisk, insulting ntl is not a good idea, especially as some good employees contribute to this forum.

You have been told that ntl does not bock port 1227, that has been confirmed here, and you have also been told that the matter is a technical problem, likely a routing issue. If you want help using an ssh client such as PuTTY, then by all means ask, but quit with the generalised insults. :(

[levy]

I too am a Deerfield DNS2GO user. I have been using DNS2GO for many years. This is the first problem I have had. Deerfield say....




We have had a number of reports from users who's ISP is NTLWorld.com that are unable to connect with their DNS2Go clients. This is related to port 1227 being blocked.

Our DNS2Go Project Manager is going to be in touch with the ISP to see if there is anything that can be done for them to allow the connection.

If NTLWorld is not your local ISP, open a DOS prompt and attempt to telnet to discovery.dns2go.com on port 1227.

Example:
telnet discovery.dns2go.com 1227

If you are unable to connect, verify the exact error message your client is returning. If the client is returning the error message: "Error - Unable to Connect to Server" Please let me know who your local ISP is.


Thank you

I'd say the problems not Deerfield or anyones configuration it seems quite localised to NTL users :rolleyes:

[criptopus]

Tisk tisk, insulting ntl is not a good idea, especially as some good employees contribute to this forum.

You have been told that ntl does not bock port 1227, that has been confirmed here, and you have also been told that the matter is a technical problem, likely a routing issue. If you want help using an ssh client such as PuTTY, then by all means ask, but quit with the generalised insults. :(

I will try to be good in the future, and try and restrain my observations to helping solve the problem. All this downtime is beginning to reflect badly on me as potential employers are emailing me as to why my site is down - stress -.

It was good of there supervisor to tell me about ssh, I downloaded win32-ssh and seem completly lost with it. I think I understand what it is supposed to do but still seem a little lost with its settings.

Should we look into this -ssh- program here or is there somewhere else in this forum that would be better?

[Toto]

I will try to be good in the future, and try and restrain my observations to helping solve the problem. All this downtime is beginning to reflect badly on me as potential employers are emailing me as to why my site is down - stress -.

It was good of there supervisor to tell me about ssh, I downloaded win32-ssh and seem completly lost with it. I think I understand what it is supposed to do but still seem a little lost with its settings.

Should we look into this -ssh- program here or is there somewhere else in this forum that would be better?

A good ssh client can be found here:

http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

And a good starting point for using it can be found here:

http://www.tartarus.org/~simon/puttydoc/

It's a pretty powerfull tool when you get the hang of it, and can help in situations such as this where there is an obvious problem with ntl and other networks.

I only normally use it to ssh into a remote linux box I use, but it has plenty of other excellent uses. :tu:

[MikeCourterier]

Hello,

Mike Courterier from Deerfield.com (DNS2Go) here.

I would like to know if this DNS2Go client connection issue still exists for NTL subscribers.

If so, it would be helpful to know if manually setting the DNS2Go server helps.

1. Open the DNS2Go client by double-clicking the tray icon.
2. Select the 'Options' tab.
3. Select the 'Advanced' button.
4. Select the 'Server Connection' tab.
5. Select the 'Connect to the server specified below' radio button.
6. Enter each of the following IP addresses in the 'Hostname or IP address' dialog (test one at a time).
7. Leave the port at 1227.
8. Select 'OK'.
9. Tell me if any of the servers work.


DNS2Go Server IPs:

198.31.34.113
207.89.233.158
63.149.6.189
207.89.233.94

Thank you,

Mike Courterier
Deerfield.com

[daxx]

Machine temp setup:
Firewall OFF
Machine set as DMZ in router
Fixed IP assigned to LAN machine

DNS2Go Server IPs:

198.31.34.113 = NO CONNECTION Error: Unable to connect to Server
207.89.233.158 = NO CONNECTION Error: Unable to connect to Server
63.149.6.189 = NO CONNECTION Error: Unable to connect to Server
207.89.233.94 = NO CONNECTION Error: Unable to connect to Server
Default Settings = NO CONNECTION Error: Unable to connect to Server


HTH

daxx

[MikeCourterier]

Machine temp setup:
Firewall OFF
Machine set as DMZ in router
Fixed IP assigned to LAN machine

DNS2Go Server IPs:

198.31.34.113 = NO CONNECTION Error: Unable to connect to Server
207.89.233.158 = NO CONNECTION Error: Unable to connect to Server
63.149.6.189 = NO CONNECTION Error: Unable to connect to Server
207.89.233.94 = NO CONNECTION Error: Unable to connect to Server
Default Settings = NO CONNECTION Error: Unable to connect to Server


HTH

daxx

Thank you Daxx,

If you wouldn't mind, would you please try this server?

67.15.62.14

Thank you,

Mike Courterier
Deerfield.com

[Paul]

I have tested this further today with some more servers and there is a problem with some (apparently US) based servers. Specifically there is a return route problem. The packets are reaching the US server (via sprint) but are getting lost on their return to me - I cannot see what route the dns2go servers are using back to ntl, but my tests seem to be getting lost either in the Level3 network, or possibly on the very edge of the ntl network (I suspect level3, otherwise the uk servers would probably fail as well, since they are outside the ntl network). :)

[MikeCourterier]

I have tested this further today with some more servers and there is a problem with some (apparently US) based servers. Specifically there is a return route problem. The packets are reaching the US server (via sprint) but are getting lost on their return to me - I cannot see what route the dns2go servers are using back to ntl, but my tests seem to be getting lost either in the Level3 network, or possibly on the very edge of the ntl network (I suspect level3, otherwise the uk servers would probably fail as well, since they are outside the ntl network). :)

Thank you Paul,

Can you give me something to test from my end?

The five server IPs I have provided are on four distinct circuits serviced by different providers.

We presently have over 20k clients connected to the service from all over the world and it seems as though the only ones experiencing connectivity problems originate from the NTL network.

Thanks again for your assistance.

Mike Courterier
Deerfield.com

[Paul]

Can you give me something to test from my end?Sorry, I'm not clear what you are asking for ?

[levy]

Thank you Daxx,
If you wouldn't mind, would you please try this server?
67.15.62.14
Thank you,
Mike Courterier
Deerfield.com

The IP address 67.15.62.14 did not work either, but reading the last few posts, it didnt look like it was going to :( . Thanks for taking the time to post here Mike.C/Deerfield.

[MikeCourterier]

Sorry, I'm not clear what you are asking for ?

Sorry, I should have been more clear... you mentioned that the return packets were being lost when the request originated from you to us... I was wondering if you had a server I could test from my end to see if the reverse were true.

Also, there does seem to be a routing issue to the NTL network from some locations here in the U.S., as an example a trace route to www.ntlworld.com (http://www.ntlworld.com) from http://www.dnsstuff.com fails in New York City.

http://www.dnsstuff.com/tools/tracert.ch?ip=www.ntlworld.com

That same trace from any of our circuits succeeds.

Thank you,

Mike Courterier
Deerfield.com

[levy]

Not sure if anyone is interested, but I donââ‚Âà ‚¬ÃƒÂ¢Ã¢â‚¬Å¾Ã‚¢t know who long this downtime is going to continue.

If you have a NetGear router and the OFFLINE auto redirection set up on your dns2go client, I have written some software which securely logs onto my Netgear router, gets the current NTL leased IP address, then creates an auto redirect HTML page and FTP/uploads it to my NTL website which is the target for my DNS2GO offline page. So when someone attempts to access my dns2go web site, Deerfield detects I am offline, forwards them HTML request to my NTL offline page then subsequently forwarded to my websites using the IP address currently leased. It all works great.

So if you have:

· A NETGEAR router,
· Your DNS2GO offline redirection already setup
· Have Visual Studio 2003 / C# or just want the setup package

Drop me a line , i'll email the code, its fully configurable and freeware ;)

Levy.

[Paul]

Sorry, I should have been more clear... you mentioned that the return packets were being lost when the request originated from you to us... I was wondering if you had a server I could test from my end to see if the reverse were true.You could try zmnt.co.uk - this is an ntl connected machine that is currently listening on port 1227 - it will allow a connection and then drop it.

Basically I have machine "A" which is on ntl, and machine "B" which is on a network in the USA, both are listening on port 1227. If I initiate a connection from A > B then the syn request gets from A > B, B sends the ack back, but this gets lost on route back from B to A. Hence the connection fails to establish.

However ... If I initiate a connection from B > A then the syn gets from B > A ok, and the ack gets back from A to B ok - hence the connection is established.

The replies from the remote US end are getting lost only when the local ntl end initiates the connection.

I have seen this in the past on ntl - as I recall - I think it was due to the the ntl core routers bouncing the return packets between themselves - but ignition would be better able to comment on this.

[MikeCourterier]

You could try zmnt.co.uk - this is an ntl connected machine that is currently listening on port 1227 - it will allow a connection and then drop it.

Basically I have machine "A" which is on ntl, and machine "B" which is on a network in the USA, both are listening on port 1227. If I initiate a connection from A > B then the syn request gets from A > B, B sends the ack back, but this gets lost on route back from B to A. Hence the connection fails to establish.

However ... If I initiate a connection from B > A then the syn gets from B > A ok, and the ack gets back from A to B ok - hence the connection is established.

The replies from the remote US end are getting lost only when the local ntl end initiates the connection.

I have seen this in the past on ntl - as I recall - I think it was due to the the ntl core routers bouncing the return packets between themselves - but ignition would be better able to comment on this.

Hi,

Looks like you were way ahead of me... it was your B>A test that I was wanting to confirm and it appears as though it works fine.

I don't think there is anything more I can do on my end, hopefully someone from NTL will look at this again.

Thank you for all of your help.

Mike Courterier
Deerfield.com

[levy]

Not sure if anyone is interested, but I donââ‚Âà ‚¬ÃƒÂ¢Ã¢â‚¬Å¾Ã‚¢t know who long this downtime is going to continue.

If you have a NetGear router and the OFFLINE auto redirection set up on your dns2go client, I have written some software which securely logs onto my Netgear router, gets the current NTL leased IP address, then creates an auto redirect HTML page and FTP/uploads it to my NTL website which is the target for my DNS2GO offline page. So when someone attempts to access my dns2go web site, Deerfield detects I am offline, forwards them HTML request to my NTL offline page then subsequently forwarded to my websites using the IP address currently leased. It all works great.

So if you have:

· A NETGEAR router,
· Your DNS2GO offline redirection already setup
· Have Visual Studio 2003 / C# or just want the setup package

Drop me a line , i'll email the code, its fully configurable and freeware ;)

Levy.

Got me thinking, i dont need dns2go anymore, just use my NTL domain with the redirection software

[keety]

So, any idea how we go about getting this fixed??????

[MikeCourterier]

Hi,

We are testing alternative ports and have made some progress... if you would like to give it a try... do the following:

1. Open the DNS2Go client by double-clicking the tray icon.
2. Select the 'Options' tab.
3. Select the 'Advanced' button.
4. Select the 'Server Connection' tab.
5. Select the 'Connect to the server specified below' radio button.
6. Enter IP addresses 66.98.216.42 in the 'Hostname or IP address' dialog.
7. Set the port to 6000.
8. Select 'OK'.
9. Tell me if it works.

Thank you,

Mike Courterier
Deerfield.com

[Paul]

FYI - I can connect to that fine via Telnet. :)

[MikeCourterier]

FYI - I can connect to that fine via Telnet. :)

Hi Paul,

Yes, it looks like port 6000 is going to work...

I see a couple of users from NTL online using that port.

Mike Courterier
Deerfield.com

[daxx]

Ahhhhhh < big sigh of satisfaction>

all fine from me as well

Thanks Mike and all at Deerfield for the quick workaround

daxx

[MikeCourterier]

Ahhhhhh < big sigh of satisfaction>

all fine from me as well

Thanks Mike and all at Deerfield for the quick workaround

daxx

Hi Daxx,

Glad to hear it...!

Thanks for your assistance in troubleshooting the issue over the weekend.

Mike Courterier
Deerfield.com

[keety]

I'll give it a bash when I get home, many thanks for your help!

[MikeCourterier]

I'll give it a bash when I get home, many thanks for your help!

Hi Keety,

NP... please check back here before you give it a go... we are moving the server that is listening on port 6000 to a different location. Once it is moved, I will post the new IP/Name to this thread. I hope to get that done in the next hour or so.

It is presently running at one of our backup locations and I'd like to get it in-house to minimize DNS propogation times.

Thank you,

Mike Courterier
Deerfield.com

[MikeCourterier]

Hi,

Ok, we have a DNS2Go server setup and listening on port 6000. We have tested with a number of NTL subscribers with positive results. This server will stay in place until the routing issue with port 1227 is addressed.

To use the server, do the following:

1. Open the DNS2Go client by double-clicking the tray icon.
2. Select the 'Options' tab.
3. Select the 'Advanced' button.
4. Select the 'Server Connection' tab.
5. Select the 'Connect to the server specified below' radio button.
6. Enter d2gpip4.deerfield.com in the 'Hostname or IP address' dialog.
7. Set the port to 6000.
8. Select 'OK'.

Alternatively, you can set the 'Hostname or IP address' to IP Address 63.149.6.95.

I will leave the test server at 66.98.216.42 up an running until tomorrow to give those using it time to switch over.

Thank you,

Mike Courterier
Deerfield.com

[levy]

Great Job MikeC/Deerfield all working here too ...:D

[daxx]

switched to 'new' server

thanks again Mike

usual top class service from your crew

[fmusgrave]

OK I am having a connection problem too, but do not know what NTL is but wouls love to know what I need to do to get it fixed. DNS2GO give one ip, but what is my Ip give another, so DNS2go is not getting ping. It just will not connect. HELP

[Peter_]

Nice thread bump 4 years and 2 months old.