Works for me here in Phoenix.

hard coding the IP seems the only way to get around this temporarily until all the DNS records get updated.
Put your cable modem on a UPS so it never goes down ;)

tracert 70.94.216.222

Tracing route to mta-70-94-216-222.new.res.rr.com [70.94.216.222]
over a maximum of 30 hops:
[code]
5 93 ms 57 ms 19 ms langbbr01-ae0.r2.la.cox.net [68.1.0.232]
6 22 ms 23 ms 24 ms ae-2-0.cr0.lax00.tbone.rr.com [66.109.6.132]
7 29 ms 29 ms 31 ms 66.109.6.6
8 31 ms 30 ms 30 ms ae-0-0.cr0.sjc10.tbone.rr.com [66.109.6.8]
9 69 ms 70 ms 69 ms ae-2-0.cr0.chi10.tbone.rr.com [66.109.6.15]
10 65 ms 65 ms 65 ms ae-15.chcgileq-rtr1.kc.rr.com [66.109.6.101]
11 79 ms 79 ms 80 ms CPE-69-76-62-254.kc.res.rr.com [69.76.62.254]
12 76 ms 77 ms 77 ms gig2-0-0.kscyks119-10k1.kc.rr.com [24.94.161.42]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * *
[/code]

On a side note. Can I use Orly the osterich as my avatar?

@all regarding G4000: Hmm, what a mess. Gary, I had completely forgotten to ask about the No-IP needing to be installed when you reformatted your hard drive a while back...I guess I just assumed for whatever reason that your IP address had changed numerous times since then and that thus you had to have had the client updating it automatically. I stand corrected. :smile:

Now I'm able to connect fine to the server; it looks like we should be good from now on, with the No-IP client now updating the DNS automatically. Clients should be able to begin migrating back to G4000 if they wish. :smile:

Gary, I'm thinking that the reason why people still weren't able to connect to the server even after you thought you'd fixed the problem, is what David said: it just took a while for the updated IP address to propagate through the No-IP system. Hopefully we shouldn't have any such problems again due to such changes being automatically updated in the future.

Max :smile:

[quote=MyDogBuster;155404]On a side note. Can I use Orly the osterich as my avatar?[/quote]
I don't see why not. But, one quick question: who is Orly the ostrich? :smile:

[quote=mdettweiler;155453]I don't see why not. But, one quick question: who is Orly the ostrich? :smile:[/quote]
:orly emu:(Tho' he's actually Orly Emu.)
Not to be confused with my avatar.

[quote=Flatlander;155454]:orly emu:(Tho' he's actually Orly Emu.)
Not to be confused with my avatar.[/quote]
Oh, I get it now! I didn't realize at first that "Orly" was meant to be the same as "O RLY", hence I didn't make the connection. :smile:

<<<<<<<<<<<<< More my style BUT

I still can't connect to G4000.

[B]NPLB LLRnet server #4 (updated 2008-12-28 17:00 GMT):[/B]
maintained by em99010pepe
Short identification: C6000
server = "nplb.dynip.telepac.pt"
port = 6000
k-range: k = 341 / 315
n-range: 600K-1M / 700K-1M
currently processing [COLOR=#0000ff]k=341 at n=~802.09K[/COLOR]

Okay, I got it working but not before I had to re-boot MY laptop.
Why would the server having an identity crisis cause me to have to re-boot to sync up again? Cookies?

I'll probably have to re-boot all my machines that I want on G4000. Not a good thing.

If it's windows, open a cmd prompt and typy nbstat -RR and ipconfig /flushdns

[quote=IronBits;155483]If it's windows, open a cmd prompt and typy nbstat -RR and ipconfig /flushdns[/quote]

I was thinking about that but I couldn't remember the command line...lol