Printable View
After I moved 6 of 17 boxes from sbp.pns.net to sb.pns.net 17 boxes can not communicate with the server.
Has some admin blocked my account for some reason?
It is not the case I see.
If I ping sb.pns.net I get address 216.168.224.53 instead of 69.9.160.186 and
for sbp.pns.net I get IP 216.168.224.53 instead of 69.9.160.188.
Seems to be a DNS problem.
Wow I can't ping any of those by IP's or DNS either...
Not sure e-mail alien88
I have somewhat the same problem.Quote:
Originally Posted by Joh14vers6
I need to use sbp.psn.net and port 80 due to firewall reasons and when I was setting up som boxes this morning (european time) all of a sudden I could not connect to the server anymore.
The log on a running machine show throughout the day
...
[Wed Jan 18 16:42:07 2006] resolving hostname
[Wed Jan 18 16:42:07 2006] opening connection
[Wed Jan 18 16:42:18 2006] server busy -- block added to submit queue
...
But half an hour ago it began to show:
...
[Wed Jan 18 16:55:36 2006] resolving hostname
[Wed Jan 18 16:55:54 2006] could not resolve hostname -- block added to submit queue
...
Right now it seems like a DNS problem but if anyone has further info it would be great.
Regards
According to Network Solutions, the domain pns.net (presumably sb.pns.net & sbp.pns.net are subsets) expired on Jan 12/06 and is pending renewal or deletion. :eek: :eek:
Just try entering either URL in your favorite browser.
_need creditcard_ :|Quote:
Domain Pricing †
1 Year @ $34.99 per year
2 Years @ $29.99 per year (Save 14%)
3 Years @ $24.99 per year (Save 28%)
5 Years @ $19.99 per year (Save 42%)
9 Years @ $14.99 per year (Save 57%)
100 Years @ $9.99 per year (Save 70%)
All years billed at time of purchase
stupid internet :swear:
but, for 75 bucks, it'll be online for 3 years, or so Network Solutions claims...
Been doing it since last night. :(
Someone dropped the ball and did not renew the address.
Its wierd it hasnt worked since 4AM of 1/18 ... if they forgot to register their address .. they should have posted some kind of warnin or something of that sort.... do you guys think that there might have been a change of hearts as to the point of this test.... well i will keep on trying... by the way i know a company, if any one is interested, that charges 12 bucks per year and i think 10 if you go for 2+ years... and without bandwidth restrictions xD
What's the solution? I notice on the TPR stats that some users are managing to send in intermediate blocks. How are they achieving this?
All of my machines are blocked from getting through also. It started about 5 pm est.
unionpacific59
I'm surprised nobody has mentioned that the easy temporary fix is to just modify the config to use the IP address directly rather than rely on the DNS/hostname.
I switched my config to use 69.9.160.186 and it's working fine for me now.
Other options are to add a hosts entry or if you're hosting your own DNS to just manually add it to your local DNS server until the SoB admins get it straightened out.
I just switched to seventeenorbust.com and everything works fine again...Quote:
Originally Posted by umccullough
i tried both and still have no connection
unionpacific59
Indeed, the IP address works, but I can only access one SoB PC directly, the other ones will be at least two weeks, which is going to cost me dearly in output :(
And I'm not the only one with PC's out of reach I'm afraid...
Guys don't forget about the sieve and factor sections as back ups
IP doesn't work for client's that need port 80! Unless there's another IP for port 80 clients? :umm:
Since I don't use the proxy, I don't even know what hostname, or IP that was... i'll assume by the original poster's message that it was sbp.pns.net @ 69.9.160.188 ?Quote:
Originally Posted by Glenn119
This is of course true -- and that is why I still have a couple machines that are out of touch as well.Quote:
Originally Posted by EER
I find it insanely weird that the admins haven't commented this yet! :scratch:
Anyway, you can change the serv_addr key under HKEY_LOCAL_MACHINE\SOFTWARE\LhDn\sob\config from sb.pns.net to seventeenorbust.com to make things work (at least for now).
Just remember to restart your client(s) to apply this setting.
Sceptic
... The 69.9.160.188 IP works fairly well ... XD
just add it to your config tab XD
You would think we would have learned last time but we forgot again.. It's been renewed for two years this time and should start working again as soon as it's expired from your name servers.
I'm able to resolve everything here w/o any problems. Many apologies for this happening again..
Alien88
From post #11 - seventeenorbust.com won't fit in the host section in config.Quote:
Originally Posted by othello
Looks like now the sb.pns.net points to a networksolutions.com "under construction" page..
So using either 69.9.160.186 for normal clients, or 69.9.160.188 for proxy clients is still required I guess...
UPDATE: Nevermind, looks like my DNS cache just needed to be flushed from yesterday's fiasco:
ipconfig /flushdns
UDPATE2: It appears to have switched back to the "under construction" page... is NSI screwing up the nameservers?
Linux :-)Quote:
Originally Posted by vaughan
Or probably just editing the registry directly...Quote:
Originally Posted by othello
Why such a ridiculous text length limit in the first place?
C:\Documents and Settings\Administrator>ping sb.pns.net
Pinging sob.pns.net [69.9.160.186] with 32 bytes of data:
Reply from 69.9.160.186: bytes=32 time=260ms TTL=37
Reply from 69.9.160.186: bytes=32 time=260ms TTL=37
Reply from 69.9.160.186: bytes=32 time=259ms TTL=37
Reply from 69.9.160.186: bytes=32 time=263ms TTL=37
Ping statistics for 69.9.160.186:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 259ms, Maximum = 263ms, Average = 260ms
Looks like it happened again :cry:Quote:
Originally Posted by Alien88
****ing DNS servers eh who'd have them....
please wait.....
login to ROOT server A - access code level 5 required and all access is logged.
userid: ##################
password: ##############################
login successful.
Hello Sir,
#dup -a *.pns.net -i 69.9.160.186
1 record loaded
#rec -a sbp.pns.net -i 69.9.160.188
1 record loaded
#update
2 records will be updated, passed to other root servers on next update.
next update in 1h35m14s
#quit
goodbye Sir...
Logged in for 12 seconds.
(IF freaking only!)
It did. It's been fixed now: Record expires on 12-Jan-2017.Quote:
Originally Posted by IronBits
So this is a non issue for quite a while now. Sorry, again.
someone send him a reminder around new year 2016-2017 ;)
Hope to be done by then.:thumbs:Quote:
Originally Posted by KriZp
Or create a sticky thread "Domain expires on 12-Jan-2017!!!", maybe it will also encourage people to get the job done before (next) domain expiration... :clap:Quote:
Originally Posted by KriZp
LOL:rotfl::rotfl:Quote:
Originally Posted by Theadalus