I can not connect to boru server

Status
Not open for further replies.

artur79

New Member
Messages
10
Reaction score
0
Points
0
I don't know why I can not connect to boru server. I know it work, and I can see my site via proxy server but directly I see "Firefox can not connect to the server". It is not DNS problem, it's ping test from windows cmd.exe
""
Microsoft Windows XP [Wersja 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>ping buntownik.x10.bz

Badanie buntownik.x10.bz [69.175.121.66] z u¿yciem 32 bajtów danych:

Up³yn±³ limit czasu ¿±dania.(time out)
Up³yn±³ limit czasu ¿±dania.
Up³yn±³ limit czasu ¿±dania.
Up³yn±³ limit czasu ¿±dania.

Statystyka badania ping dla 69.175.121.66:
Pakiety: Wys³ane = 4, Odebrane = 0, Utracone = 4 (100% straty/lost),
""

I don't know what can be a reason. Using proxy is some way, but not the best for me (site is not big problem but I don't like webmail).
What can I do? Can You help me some way?
 

Anna

I am just me
Staff member
Messages
11,783
Reaction score
595
Points
113
We're aware of this, it is affecting some people, including me. All seem to be form various ISPs and countries, so it does look like it would be a node somewhere along the way that fails.

I have contacted our DC to have them assist on checking network connectivity.
 

Anna

I am just me
Staff member
Messages
11,783
Reaction score
595
Points
113
Could you please do a tracert and paste the full response? And please let me know what IP you are located at.

you can send me an email to anna[at]x10hosting.com
 

artur79

New Member
Messages
10
Reaction score
0
Points
0
OK I send mail but probably it not help. There is more then 255 hops (it cant work)
PS here I can write and I don't need to use proxy. You see my IP I think ;)
 

Anna

I am just me
Staff member
Messages
11,783
Reaction score
595
Points
113
Yes, I see your IP. However I would not do that if you had replied through the account panel as that would only show the IP of the location of the account panel, hence why I asked for it.

We have a few users with the same problem and are working on getting it sorted. It does however appear to be failing at a point outside of our control sadly.
 

artur79

New Member
Messages
10
Reaction score
0
Points
0
If it's problem with some on way node who can do something with this? I don't know how it work, where are the trace set. if it is makes sense to ask for help my ISP, can they do something?
 

Anna

I am just me
Staff member
Messages
11,783
Reaction score
595
Points
113
It may help contacting your ISP, but it is highly possible that they'll say, not our end, we can't do anything. I am currently stuck with that answer from my ISP :/
 

artur79

New Member
Messages
10
Reaction score
0
Points
0
The problem disappeared. So now looks like the result of tracert:

Trasa śledzenia do buntownik.x10.bz [69.175.121.66]
przewyższa maksymalną liczbę przeskoków 30

1 <1 ms <1 ms <1 ms 192.168.2.1
2 9 ms 8 ms 7 ms Poznan-bras2.inetia.pl [195.114.190.152]
3 6 ms 6 ms 6 ms 81.210.127.234
4 * 33 ms 32 ms hbg-b1-link.telia.net [195.12.255.169]
5 44 ms 44 ms 44 ms 208.178.58.33
6 135 ms 135 ms 135 ms xe-2-0-5.ar2.ord1.us.nlayer.net [69.31.111.222]
7 132 ms 133 ms 133 ms ae4-52.cr1.ord1.us.nlayer.net [69.31.111.145]
8 * 151 ms 150 ms ae1-20g.ar1.ord6.us.nlayer.net [69.31.110.250]
9 134 ms 134 ms 134 ms as32475.xe-2-0-4.ar1.ord6.us.nlayer.net [69.31.110.202]
10 * * * Upłynął limit czasu żądania.
11 * 143 ms * boru.x10hosting.com [69.175.121.66]
12 144 ms * * boru.x10hosting.com [69.175.121.66]
13 143 ms * * boru.x10hosting.com [69.175.121.66]
14 143 ms 144 ms * boru.x10hosting.com [69.175.121.66]
15 * 143 ms * boru.x10hosting.com [69.175.121.66]
16 * * * Upłynął limit czasu żądania.
17 * 143 ms * boru.x10hosting.com [69.175.121.66]
18 * * 143 ms boru.x10hosting.com [69.175.121.66]

Śledzenie zakończone.

I didnt contact my ISP. It start working yesterday
 

Anna

I am just me
Staff member
Messages
11,783
Reaction score
595
Points
113
Yeah, it started working for me as well yesterday.

So guess whatever caused it has been solved.
 
Last edited:
Status
Not open for further replies.
Top