View Full Version : AOL Problems accessing the control panel
Today we received 2 complaints of AOL users not being able to access the control panel on Direct Admin servers.
Thanks to Dean (a loyal supporter) he found that the built in AOL browser will NOT work on port 2222 connections - he used an external copy of Mozilla, and everything worked fine.
muttdog
10-31-2003, 10:14 AM
Today we received 2 complaints of AOL users not being able to access the control panel on Direct Admin servers.
Thanks to Dean (a loyal supporter) he found that the built in AOL browser will NOT work on port 2222 connections - he used an external copy of Mozilla, and everything worked fine.
On another note, i seem to have this 'non'-issue issue... (not hostpc, but big ole msft)
In IE 6.0.2800.1106 if i type www.domainname.com:2222 in location i get page can't be displayed. BUT if i type http://www.domainname.com:2222 it works...
strange...
hello muttdog
yep...for some reason it won't work without the http://
stangz
11-03-2003, 10:50 PM
Originally posted by muttdog@Oct 31 2003, 09:14 AM
On another note, i seem to have this 'non'-issue issue... (not hostpc, but big ole msft)
In IE 6.0.2800.1106 if i type www.domainname.com:2222 in location i get page can't be displayed. BUT if i type http://www.domainname.com:2222 it works...
strange...
Sweet, I thought I was the only one having that problem. Just to fulfill my curiousity, does anyone know why it does this?
thevillageinn
11-04-2003, 12:10 AM
I tried searching at the MS Knowledge Base, but got tired of sifting through bad results.
muttdog
11-04-2003, 10:09 AM
Originally posted by stangz@Nov 3 2003, 09:50 PM
Sweet, I thought I was the only one having that problem. Just to fulfill my curiousity, does anyone know why it does this?
it has to do with the construction of a URL....
blah://IPADDRESS/directory
Remember www.fakednsentry.com resolves to an IPaddress, regardless if it starts with www or ftp or subdomain (if you have DNS record) Resolution occurs in reverse, traversing backward through the DNS entry.
As with my site on hostpc, and I am assuming *most* others, unless you are special, have www.domain.com resolve to the same address as ftp.domain.com. SO what does this mean?
If you type in 63.247.79.138 into the address bar in IE, IE only is told to go to that IP. But using what protocol?? ping? finger? gopher? TCP? UDP? FTP? HTTP? telnet? (ok, so some of these protocols are not on the same OSI layer, but just pretend since I dont feel like thinking of others)
That the were the blah:// comes in (notice :// is just a separator used in parsing the address)
Since the majority of people are using the http protocol (most access webpages) IE and Netscape "default" under their own conditions to which protocol to use...
Typically the protocol defines a default port to go to.
Ok, so you think I am crazy... Do a DNS resolve on your domain. Do it for www.domain.com and ftp.domain.com. They are the same right? (again, unless you are big huge user or reseller and have mutiple boxes... Such as www.microsoft.com and ftp.microsoft.com dont resolve to same thing, but work in same fashion.) So try this: use your favorite FTP program to go to www.domain.com. Basically you are doing a FTP protocol on IPADDRESS:21 the www has nothing to do with the use of ftp or http. You can even ftp to just domain.com
Now, you are gonna try to do http://ftp.domain.com This actually works, but it wont show your homepage. The reason is because of the way DA and other control panel has been configured to "forward" and share a hosting computer... That Apache page you see is the default page at http://IPADDRESS control panels use the DNS resolve process to figure out which page to show. If you dont use DNS, you wont see your webpage.
SO! the reason you might need http:// for some and not for others is because of the way that the browser "guesses" the type of protocol you want to use... It is a convience they added so you can type www.microsoft.com to access http:// without typing it. When you specify a port, i dont know what protocol IE defaults to, but obviously it is the wrong one...
thevillageinn
11-04-2003, 12:45 PM
thanks for explaining it.
I had figured that it was due to the fact that you were specifying a port, and as a result had to specify a protocol because IE wouldn't just assume.
I was also hoping that MS would just say it in so many words so I wouldn't have to try to explain what little I know about this.
stangz
11-04-2003, 04:55 PM
Originally posted by muttdog@Nov 4 2003, 09:09 AM
Ok, so you think I am crazy...
Yep. I do think you are crazy! :P :lol: :P
Guest
01-22-2004, 02:10 PM
Why in the world would anyone who needs to access a web control panel be using AOL in the first place?
Get a real ISP, and stop supporting a company that blocks lots of legitimate email, and gives their users a crippled version of the net, among other things.
Using AOL as your ISP when you're running a website is like someone using a crayon to write their resume for an executive job.
QuickGold
01-22-2004, 03:00 PM
Originally posted by Guest@Jan 22 2004, 01:10 PM
Why in the world would anyone who needs to access a web control panel be using AOL in the first place?
Get a real ISP, and stop supporting a company that blocks lots of legitimate email, and gives their users a crippled version of the net, among other things.
Using AOL as your ISP when you're running a website is like someone using a crayon to write their resume for an executive job.
Not everyone is a gifted Internet whiz....different strokes for different folks :D
At least AOL users aren't supporting that company with the butterfly. ;)
thevillageinn
01-24-2004, 10:10 PM
now that this topic is back on the top...I noticed a while ago that in Firebird you don't have to type "http://" in front of the www.mydomain.com:2222
also, there's no reason to jump all over people for using AOL. There are many reasons, in addition to the one QuickGold noted. Sometimes, as a reseller, you have a client...and they use AOL...
QuickGold
01-24-2004, 11:45 PM
Originally posted by thevillageinn@Jan 24 2004, 09:10 PM
I noticed a while ago that in Firebird you don't have to type "http://" in front of the www.mydomain.com:2222
You can get away without typing the http:// portion in any browser, I believe
thevillageinn
01-25-2004, 11:50 PM
I've never been able to get MSIE to accept just "www.mydomain.com:2222" it always errors out unless I add the "http://". I don't know about NN or Opera, but Firebird will go to the admin panel with out "http://"
QuickGold
01-26-2004, 02:44 PM
Originally posted by thevillageinn@Jan 25 2004, 10:50 PM
I've never been able to get MSIE to accept just "www.mydomain.com:2222" it always errors out unless I add the "http://". I don't know about NN or Opera, but Firebird will go to the admin panel with out "http://"
I'm a Mozilla/Firebird user...and you are right about IE not taking it sans http://. Oh well, thats a good reason to change browsers :D
Originally posted by QuickGold+Jan 26 2004, 12:44 PM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (QuickGold @ Jan 26 2004, 12:44 PM)</td></tr><tr><td id='QUOTE'> <!--QuoteBegin-thevillageinn@Jan 25 2004, 10:50 PM
I've never been able to get MSIE to accept just "www.mydomain.com:2222" it always errors out unless I add the "http://". I don't know about NN or Opera, but Firebird will go to the admin panel with out "http://"
I'm a Mozilla/Firebird user...and you are right about IE not taking it sans http://. Oh well, thats a good reason to change browsers :D [/b][/quote]
Just one reason among many, many others...
Most importantly is all of the holes that all of these viruses and hijacks take advantage of in IE. Those things aren't a problem with Firebird. The same arguments apply to Thunderbird over Outlook/Outlook Express.
QuickGold
01-26-2004, 04:58 PM
Originally posted by ozee@Jan 26 2004, 01:52 PM
Most importantly is all of the holes that all of these viruses and hijacks take advantage of in IE. Those things aren't a problem with Firebird. The same arguments apply to Thunderbird over Outlook/Outlook Express.
I'll echoe those recommendations as well as the one for Thunderbird...it's great.
thevillageinn
01-26-2004, 10:17 PM
I like thunderbird, but I find it's slow to respond after it's been in the background for a while. Say during the day it's on, and then I come to check my e-mail at night, it can take a while for it to get it's act together and change views or check mail.
I'm curious if anyone else has this issue, I've always figured it to be a result of large mail files, and I just put up with it.
QuickGold
01-26-2004, 11:52 PM
Originally posted by thevillageinn@Jan 26 2004, 09:17 PM
I like thunderbird, but I find it's slow to respond after it's been in the background for a while. Say during the day it's on, and then I come to check my e-mail at night, it can take a while for it to get it's act together and change views or check mail.
I'm curious if anyone else has this issue, I've always figured it to be a result of large mail files, and I just put up with it.
Can't say I've had this issue, albeit I don't leave it running all the time. Do you have the most current version? They come out with new versions fairly often. I ran a search and found nothing off the bat. Alot of software tends to be slow coming back when it's been on for a while and(I assume) minimized.
eugene
01-27-2004, 12:05 AM
Originally posted by thevillageinn@Jan 26 2004, 08:17 PM
I like thunderbird, but I find it's slow to respond after it's been in the background for a while. Say during the day it's on, and then I come to check my e-mail at night, it can take a while for it to get it's act together and change views or check mail.
I'm curious if anyone else has this issue, I've always figured it to be a result of large mail files, and I just put up with it.
My guess is that it is an OS-related issue. It could be the result of the OS placing the idle proc's memory onto disk cache. On the other hand, it could just be the result of power management options; your HDD could have spun down to preserve life/power.
thevillageinn
01-27-2004, 04:58 AM
Originally posted by eugene@Jan 26 2004, 08:05 PM
My guess is that it is an OS-related issue. It could be the result of the OS placing the idle proc's memory onto disk cache. On the other hand, it could just be the result of power management options; your HDD could have spun down to preserve life/power.
I haven't upgraded it in a while, so I will see if that does anything for it.
as far as the HDD spin up or similar, that's not an issue as I've usually been using the computer for other things just prior (games, etc.) or my wife was just using it.
In looking at the memory usage for the process, it was pretty small (2.5 mb or so) so I brought it to foreground (hadn't used it in about 6 or 7 hours) it was slow to respond, and there was a good amount of disk access as it loaded my accounts back into memory, I then checked the memory usage and it had jumped up to nearly 17mb. That is likely where my slow response is. Once the disk had quieted down (just a few seconds later) I moved around between accounts and such, and found that things were much quicker.
So there ya go...my 'mystery' is solved.
TBird does the same thing for me if it's been "asleep" for awhile, but I always just figured it was a caching issue...
Right now, it's a small price to pay to be freed from that buggy MS email program...
Originally posted by Guest@Jan 22 2004, 01:10 PM
Why in the world would anyone who needs to access a web control panel be using AOL in the first place?
Get a real ISP, and stop supporting a company that blocks lots of legitimate email, and gives their users a crippled version of the net, among other things.
Using AOL as your ISP when you're running a website is like someone using a crayon to write their resume for an executive job.
I despise AOL. But as a reseller (and as a web developer in general) I have to acknowledge AOL's customer base and act accordingly. Some of my hosting clients use AOL -- they may never have the "need" to access the control panel because they'll have someone else actually maintaining the site, but they may want to do little things from time to time such as adding an email forwarder. What are we supposed to do? Tell potential clients we won't take their money because they're on AOL? That's elitist, arrogant, and not a very smart business decision. Yes, AOL sucks, but we can't just ignore them. IMHO.
Powered by vBulletin™ Version 4.0.3 Copyright © 2012 vBulletin Solutions, Inc. All rights reserved.