Users can't get on using AOL

Since the upload, we can get on the site using explorer and everything seems to work ok, but we're having problems when trying to log on using AOL. A user tells me this:

I'm getting the "forbidden" page or "cannot be found" when logging in via aol which I always did in the past, but can get in fine through internet explorer. Any suggestions?

Also, I notice it has gotten worse as time has gone on.

[Ntfu2]

thats caused by either a incorrect .htaccess file, try backing up your current one, and then deleting the .htaccess file and try again.

File ownership is wrong, though everyone would get the error then.

If your old server didnt have mod_security enable/installed, and your new one does try either turning it off, or turning the mod_security rules down alot. I personally dont use mod_security and have 0 security problems.

[motochick]

I can move the .htaccess file from my old server to the new one and overwrite it. Wouldn't that get the same result? If so, where the heck to I find the file?

Also, where could I find that mod_security setting so I can check it?

Thanks alot for the leads! BTW, it seems to be working better on AOL but still not right (ex: clicking our logo on top page is supposed to take you to home page but instead there is an error)

And it did work fine before the move. Thanks again, I really appreciate the help!

[Ntfu2]

mod_security is server level, you wont find it in vBulletin settings, ask whoever setup your server (hosting company)

.htaccess will either be in the web root, or in the forums root.

[motochick]

Thank you ntfu2 for the suggestions. I passed them on to my server co and it must have done the trick because the server co has the forum working on aol now. However, it it is running WAY SLOW. The pages load at what seems like dialup speed. But then again, my internet company is having problems, AGAIN. So I'm not sure if it is my connection or the site. IF it is the site, any suggestions on whats up?

[Ntfu2]

attempt a traceroute to the server, it could be a number of things from your ISP's route to the server, to the actual hosting company itself. Usually a traceroute will be able to tell you where the connection is slowing down, if you copy and paste the results here, I'm sure we'll be able to help.


Or you could wait about 6 hours, if they are continuing to have problems, it maybe a early indication the hosting isn't for you

[motochick]

oh, what the hell I ran the traceroute from the windows command prompt but I can't copy it to paste it here. AHHHHHH!

oh, whatever, I;ll type it out for gods sake!

tracing route to supermotojunkie.com [72.52.152.114] over a maximum of 30 hops
1 19ms 9ms 6ms 10.33.0.1
2 7ms 8ms 7ms ip68-8-2-1-213.ph.ph.cox.net [68.2.1.213]
3 10m 9ms 11MS 68.2.12.181
4 9ms 7MS 8MS 68.2.12.66
5 7MS 8MS 9MS CHNDDSRJ01-ae1.rd.ph.cox.net [68.2.14.1]
6 18ms 20ms 17ms 68.1.0.232
7 32ms 19ms 21ms dpr1-ge-2-0-0-298.losangelesquinix.savvis.net [208.173.157.37]
8 18ms 20ms 19ms dcr1-so-3-0-0.losangeles.savvis.net[207.70.194.1]
9 51ms 27ms 52ms dcr2-so-6-0-0.dallas.savvis.net [204.70.192.85]
10 33ms 32ms 51ms dcr2-so-6-0-0.dallas.savvis.net [204.70.192.50]
11 106ms 197ms 73ms dcr1-as1.atlanta.savvis.net [204.70.194.177]
12 87ms 85ms 88ms bcs1-so-2-0-0.washington.savvis.net [204.70.192.54]
13 86ms 89ms 99ms bcs1-so-1-3-0.washington.savvis.net [204.70.192.21]
14 103ms 98ms 99ms lw-core2-ge4.rtr.liquidweb.com [209.59.157.26]
15 121ms 98ms 111ms acr2-so-1-1-0.washington.savvis.net [204.70.194]
16 114ms 121ms 98ms lw-dc2-dist2.rtr.liquidweb.com [209.59.157.110]
17 97ms 97ms 114ms lw-core2-ge4.rtr.liquidweb.com [209.59.157.110
18 97ms 101ms 120ms lw-dc-dist2-ge2.rtr.liquidweb.com [209.59.157.110]
19 99ms 114ms 100ms host.supermotojunkie.com [72.52.152.114]

Trace complete