Server not found....(Problem Resolved)
 

ADMINS, please help! for some reason, i can no longer get connected
to this wonderful site from my laptop. yesterday, there were some
random issues, but i still could connect and browse the threads. today,
when i try and connect, i get the above message. i'm creating and posting
this thread using my work PC/Network. my laptop uses a Sprint Wireless
Network card. my default browser is Firefox (1.5.0.4), but i've also tried
IE (6.0 sp2); neither will connect. i've disconnected, rebooted, cleared
my cookies/temp. files/cache and just about everything else i can think
of. any suggestions?:dunno:

-brian

Same thing happened to me last night from home. Couldn't get in until almost midnight. Juan told me to try this: go to xoutpost.com, and do a Ctrl + F5... That should clear out your history and load up the latest version of the site.
I never had to though.

I was flipping out that I couldn't get in. Sucks huh, and of course, one of my favs here, sent me an email - OMFG - did you see that last post...oh, sorry...:rofl:

thanks Laura. i tried that and still no luck.:mad:
maybe i'll try and reboot all over again.:tsk:

try clearing your DNS cache too...

- close all browsers
- Start/Run type CMD, (enter)
- at the prompt type ipconfig/flushdns (enter)
(type exit to close)

probably won't have to restart. good luck!

Can you "ping 207.210.230.186" from your laptop?

:dunno: i also had some problems getting on. a page came up saying i need to upgrade some stuff with a a link. I never did, and was able to get on the site a couple hours later...

Your ISP probably hasn't received the DNS update for the site now that it has moved.

The ip addresss for the site is now 207.210.230.186.

do a tracert www.xoutpost.com from your laptop and see if it resolves to that address.

If not, do a ipconfig /flushdns
then tracert again

still no luck after flushing the DNS.

pinging the above IP Adress resulted in replies.
4 replies from that same IP Address.
4 packets sent, 4 packets received.

what address is www.xoutpost.com resolving to? the site will respond to the addresss above, try putting the ip address into the browswer address bar and see what happens.

if i try the tracert to www.xoutpost.com - i get :
unable to resolve target system name www.xoutpost.com

if i try a tracert to 207.210.230.186 - i get 24 different entries.
entries 2, 5 and 6 timed out.
all other entries contained ip addresses or web sites.

Thats a DNS problem with your ISP, it's not a problem with the site, they haven't received the new DNS change yet. Sometimes DNS changes take up to 72 hours to propagate.

just type the new ip address into your browser and it should come up.

i'm not sure how i can check what address x5world is resolving to.
when i try and open www.xoutpost.com and it fails, the address bar
is reading www.xoutpost.com; as it's trying to open, the status bar
reads "opening page www.xoutpost.com/..."

when i attmept the tracert to the ip address, the 1st line reads,
"tracing route to galactica.cedgecons.com [207.210.230.186]"

ok, i must be an idiot.:dunno:
when i try to type 207.210.230.186 into the address bar and press enter,
it changes to http://207.210.230.186/. a website appears, but it's not
X5world. it's a teal screen that says "There is no website configured at
this address......." it appears that this site is a generic page for www.cpanel.net

oh, just so u know, when i do the above on the pc that i am sending this
from, i get the same result.

I don't know if that's the old address or new, but that's the address that i get when i tracert to xoutpost.com as well. Maybe ucrewx5 can tell you if that is the new or old. and if it's the old, they're doing a redirect to the new and your machine isn't likeing the redirect. Regardless, I'm pretty confident that the problem is on your end or with your ISP and not with the site itself.

If I remember correctly, that 207.x.x.x address is the new address for the site.

Guess who's back?

ok, well, i guess my ISP has resolved their issues.

thanks everyone for helping me to try and troubleshoot
this issue.:2thumbs:

LOL Welcome "Back!"