Need some help

maybe

Member
I have the following problem: my browsers can't display Solo anymore. Neither IE nor Mozilla nor Opera. The AOL browser which I rarely use works fine, but I hate it. The funny thing is, I don't have this problem with any other sites I frequent, it's just Solo. First I thought the site was down but others didn't have any problems. I did what Karin told me and deleted Cookies and temporary internet files and such stuff, I restarted the computer - nothing. It occurred all of a sudden last night, a few hours before everything was fine and I didn't mess around with the software or anything. I just switched on the computer and wanted to do my nightly Solo check amongst other things and it didn't work. I'm rather helpless with computers and tend to panic when something doesn't work :o
Unfortunately I don't know any computer geeks in real life so I hope someone here can help me. Thanks in advance :)

PS - feel free to move this to the site feedback forum if this is the wrong place
 
its probably your service provider. its probably a backbone issue.
call your broadband provider and tell them whats happening. its likely that solo routes through one of those backbone providers and thats why your having trouble.
 
its probably your service provider. its probably a backbone issue.
call your broadband provider and tell them whats happening. its likely that solo routes through one of those backbone providers and thats why your having trouble.

I already contacted them and they told me to reset the internet options, clear the cookies etc., which didn't help of course. I've written them a detailed email and I'm waiting for their response. The thing is, my provider is AOL but the AOL browser is the only one that displays Solo. :confused:
Thank you anyway :)
 
i seriously think its a backbone issue. the people on the phone never know what they are talking about you gotta ask for LEVEL 3 TECH SUPPORT at least thats what they call it at time warner.

im certain solo routes through an MCI backbone. or maybe its 3 com. sometimes they gotta assign you a new ip address to get the issue fixed dont ask me why i know this stuff ! but good luck!
 
Did you download anything from the forum? Might be worth turning your firewall off and then try the forum again as it may have blocked the forum.

Might also be worth resetting your advance settings for your internet explorer?

shbf

I already did reset the advance settings, but I'll try the firewall thing later tonight. Didn't download anything from here recently though. Oh, and it's not just the forum, it's the main page as well. Thanks shbf :)
 
i seriously think its a backbone issue. the people on the phone never know what they are talking about you gotta ask for LEVEL 3 TECH SUPPORT at least thats what they call it at time warner.

im certain solo routes through an MCI backbone. or maybe its 3 com. sometimes they gotta assign you a new ip address to get the issue fixed dont ask me why i know this stuff ! but good luck!

if you can get to a site with one browser and not another there is no network issue.

the best test is to open a command window and type:

telnet www.morrissey-solo.com 80

if it connects, the network is fine.
if it gives an error saying could not connect, there is a network problem.

another possibility is that the aol browser is using a proxy and the other ones are not and you can't connect directly but could if you configured the browser to use the proxy.

backbone issues are way beyond the scope of this issue. with bgp routing in place, most backbone problems are never seen by the end user because the failed route is ignored and an alternative route is used.
 
if you can get to a site with one browser and not another there is no network issue.

the best test is to open a command window and type:

telnet www.morrissey-solo.com 80

if it connects, the network is fine.
if it gives an error saying could not connect, there is a network problem.

another possibility is that the aol browser is using a proxy and the other ones are not and you can't connect directly but could if you configured the browser to use the proxy.

backbone issues are way beyond the scope of this issue. with bgp routing in place, most backbone problems are never seen by the end user because the failed route is ignored and an alternative route is used.

This is going to sound incredibly stupid, but what do you mean with command window, bored? I only use the computer to write emails and to surf the web :o And what can I do to make the other browsers use a proxy?

It's obvious. Morrissey has cursed me for visiting "Solow" :p
 
This is going to sound incredibly stupid, but what do you mean with command window, bored? I only use the computer to write emails and to surf the web :o And what can I do to make the other browsers use a proxy?

It's obvious. Morrissey has cursed me for visiting "Solow" :p

command window is a place where you can type commands rather than point and click

click start -> run

a box will pop up

type the letters cmd and press enter

that will open a command window

then you can try the telnet command
 
open the dos window as described above by bored

type ping forums.morrissey-solo.com

It should look like this (Ish)

C:\Documents and Settings\yourname>ping forums.morrissey-solo.com

Pinging forums.morrissey-solo.com [64.182.120.8] with 32 bytes of

Reply from 64.182.120.8: bytes=32 time=163ms TTL=44
Reply from 64.182.120.8: bytes=32 time=159ms TTL=44
Reply from 64.182.120.8: bytes=32 time=165ms TTL=44
Reply from 64.182.120.8: bytes=32 time=162ms TTL=44

Ping statistics for 64.182.120.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 159ms, Maximum = 165ms, Average = 162ms


The bit in red is the bit you type in.

Do you connect through a home network (For example wireless on a laptop), or directly to the internet? (Cable direct from internet to your laptop)

I reccomend the ping utility because if FTP does connect you may just get a blank screen which is rather confusing.

If you get no responce it could be 2 things - your network provider, or your home network, if you are using one. Test this by typing tracert 64.182.120.8

it should look like this:

C:\Documents and Settings\yourname>tracert 64.182.120.8
Tracing route to 8-120-182-64.cust.propagation.net [64.182.120.8]
over a maximum of 30 hops:

1 6 ms 16 ms 6 ms 10.29.104.1
2 6 ms 5 ms 5 ms brom-t2cam1-b-ge95.inet.ntl.com [0.1.226.157]
3 7 ms 6 ms 6 ms bmly-t3core-1b-ge-010-0.inet.ntl.com [195.182.174.97]
4 6 ms 8 ms 12 ms 212.43.162.61
5 16 ms 8 ms 34 ms 195.50.91.129
6 9 ms 9 ms 8 ms ae-0-54.bbr2.London2.Level3.net [4.68.117.98]
7 8 ms 7 ms 37 ms ae-1-0.bbr2.London1.Level3.net [212.187.128.57]
8 8 ms 7 ms 8 ms ae-22-56.car2.London1.Level3.net [4.68.116.176]
9 8 ms 7 ms 7 ms bcr1-ge-6-1-0.londonlnx.savvis.net [206.24.169.29]
10 10 ms 10 ms 11 ms bcs2-so-1-1-0.Londonlnx.savvis.net [204.70.193.122]
11 156 ms 11 ms 153 ms cr1-pos-0-8-0-0.NewYork.savvis.net [204.70.192.121]
12 101 ms 148 ms 99 ms dcr2-so-3-0-0.Chicago.savvis.net [204.70.192.101]
13 149 ms 149 ms 122 ms dcr2-so-0-0-0.dallas.savvis.net [204.70.192.98]
14 149 ms 154 ms 154 ms dcr1-ge-1-0-0.losangeles.savvis.net [204.70.193.105]
15 149 ms 168 ms 149 ms cr1-bundle-pos1.losangeles.savvis.net [204.70.197.26]
16 151 ms 162 ms 149 ms dcr2-ge-3-0-0.losangeles.savvis.net [204.70.193.49]
17 164 ms 164 ms 160 ms dpr1-so-4-0-0.losangelesequinix.savvis.net [204.70.196.42]
18 162 ms 158 ms 158 ms bpr3-so-0-0-0.losangelesequinix.savvis.net [204.70.194.173]
19 162 ms 157 ms 162 ms 8-120-182-64.cust.propagation.net [64.182.120.8]


Trace complete.


The bit in red, as before...... :)

Your route will look very different to mine as you are on a different network, but copy and paste it into a message and I'll let you know where the problem lies :)

To copy it, you have to click on the little c:\ symbol on a black background on the very top left of the DOS window to the left of where it says command prompt, select edit and then mark from the drop down menue - then you can swipe it and copy and paste in the normal way.

Good luck

:)
 
Thanks bored and Bassist :) I'll try it tomorrow, I'm too tired now. I'll let you know what happens.
 
Thanks bored and Bassist :) I'll try it tomorrow, I'm too tired now. I'll let you know what happens.

No problem.

It could be a DNS problem, but it's unlikely...

try typing 64.182.120.8 into the address bar in IE instead of www.forums.morrissey-solo.com if it connects then it's your DNS, let us know.

:)
 
Ok, if I type in 64.182.120.8 a Google site pops up and says there are no results matching my query :confused:

If I type in the telnet thing the black window opens, saying it's connecting to morrissey-solo, and then all of a sudden the window closes again. I can't read what it says, it's too fast.

The pinging returns nothing, it only says something about a timeout (4 times), then there is some text and a split second later the window is closed.


tracert:

...
5 167 ms 167 ms 167 ms sl-st21-mia-14-1-1.sprintlink.net [144.223.64.217]
6 173 ms 173 ms 173 ms sl-bb20-mia-5-0-0.sprintlink.net [144.232.9.198]
7 174 ms 175 ms 175 ms sl-bb20-orl-12-0.sprintlink.net [144.232.8.53]
8 171 ms 171 ms 171 ms sl-bb21-orl-15-0.sprintlink.net [144.232.2.146]
9 188 ms 188 ms 188 ms sl-bb20-atl-2-0.sprintlink.net [144.232.20.86]
10 188 ms 188 ms 186 ms 144.232.18.14
11 211 ms 211 ms 211 ms dcr2-so-2-0-0.dallas.savvis.net [204.70.192.70]
12 245 ms 245 ms 245 ms dcr1-so-4-2-0.LosAngeles.savvis.net [208.172.44.105]
13 241 ms 241 ms 244 ms dpr1-so-0-0-0.losangelesequinix.savvis.net [208.172.44.106]
14 244 ms 269 ms 246 ms bpr3-so-0-0-0.losangelesequinix.savvis.net [204.70.194.173]
15 * * * Zeitüberschreitung der Anforderung (= timeout)
and so on

Bassist, I'm directly connected to the internet.
Internet Explorer does say there could be a DNS problem.
 
Last edited:
Sorry, I have to bump this. It's still not working. What does the above mean?

Sorry - been realy bussy.....

OK.

The fact that IE can't connect using the IP address means that it isn't a DNS issue. The fact that the ping is timing out means you'r computer can't see morrissey solo on the network.

fritz.box [192.168.178.1] - this is an internal network address. Part of a home network, you must have an ADSL router or something, not just the modem type connection....


Your hop 18 = 162 ms 158 ms 158 ms bpr3-so-0-0-0.losangelesequinix.savvis.net [204.70.194.173]

My hop 14 = 244 ms 269 ms 246 ms bpr3-so-0-0-0.losangelesequinix.savvis.net [204.70.194.173]

These are the same - this means your connection is going all the way to the states and failing at the last hop. - it should be :

8-120-182-64.cust.propagation.net [64.182.120.8]

SO.....

Option 1 - Someone who runs your home network has blocked this IP address, probably via some sort of firewall software, or on the ADSL router.

Option 2 - Someone at Morrissey-solo.com has blocked your IP Address from accessing the site. (Sorry mods, just listing options! ;))

Option 3 - REALY unlikely, but the network which Morrissey-solo is on could be blocking you, or your ISP, or your ISP is blocking it.

It works over AOL because that connection will go via their proxy server, which effectively hides your IP Address as you read from it.

My bet is Option 1, to be honest. It might be worth asking a mod to check their end though, although I can't see how something like that could happen by accident.....? So that's unlikely. I suppose it is possible someone could have used Windows Firewall on your computer (What operating sys is it? Windows xp, 98, etc?) is it possible someone is messing with you?

Let me know what you can, I'll check in again later.

Cheers

:)

EDIT: drop down to DOS again (The cmd thing) and type 'ipconfig' without the quotes! paste in what comes up - this will tell me about your home network setup.
 
Yes, the modem is used as a router... or something.

My operating system is Windows XP. As far as option 1 goes, I'm the only person who has access to the computer, and I haven't changed any settings. It practically happened from one minute to the next. I PM'd a mod to check, just in case they've blocked me by accident.

When I do the DOS thing the window closes immediately, it's impossible to read anything :mad:

EDIT: Solo doesn't do IP bans, so option 2 is out
 
Last edited:
Yes, the modem is used as a router... or something.

My operating system is Windows XP. As far as option 1 goes, I'm the only person who has access to the computer, and I haven't changed any settings. It practically happened from one minute to the next. I PM'd a mod to check, just in case they've blocked me by accident.

When I do the DOS thing the window closes immediately, it's impossible to read anything :mad:

EDIT: Solo doesn't do IP bans, so option 2 is out

I thought it would be.

Go to start>Run and type cmd into the box to get the DOS window back up.

type 'ipconfig' in at the C:> prompt.

Who else has access to the ADSL router? I think someone has been playing with that. I can't think of any other way to cause this.

Your computer can connect to every other computer between you and solo, but not 64.182.120.8 which is the IP Address for solo. It's like you being able to go all the way to London, and then being blocked from entering the street I live on.

When you do the ipconfig, one of the things to come up will be the Default Gateway. My guess, looking at your subnet, is that it will be either 192.168.178.1 or 192.168.178.254 - once you know what it is type that number into your web browser and you will get connected to your ADSL router. Probably username admin and password admin, no one ever bothers to change them. That's if it even askes. See if you can spot a firewall setting, or something similar. Or ask whever set it up if they are playing a trick on you!?
 
I can't imagine anyone messing with me. I live in a house with my parents and my grandma but nobody ever uses my computer. My mum has her own, but it isn't connected to the ADSL router, and the other two don't even know how to switch it on. It's password protected anyway. I switched it off at noon and in the evening I couldn't connect to Solo. I would have noticed if anyone had messed around with it, I was at home that day. Do you think the AOL people are that nasty? :p

Anyway, as you said, the Default Gateway is 192.168.178.1 and it takes me to the ADSL router, but I can't find anything about firewall settings there. I found something about ports, but I don't know what to do with it.

Thanks again for your help. I posted a few queries in forums about computer problems but I haven't received a single reply :(
 
Last edited:
I'm terribly sorry, but I have to bump this again. It's driving me nuts.
Any help would be really appreciated.
 
Back
Top Bottom