Problems with the website

eightysix wrote:Maybe you have cookies disabled on your browser by default?

I checked and I do have my jdorama.com cookie.

I also sometimes have problems with the "View posts since last visit" link, sometimes I get the first page of results, but when I click on the "Next" link it says nothing matched the query, which can't be right because the first page says there's 2 more pages of results to go.

crack

SnowBlower wrote:crack

what kind?

plumbers crack?

Is it just me then that has a problem with the view new posts function? rats.

(Edit: it is just me ... I did something stupid on my machine and forgot about it, d'oh!)

I thought maybe I could do a search for all new posts 1 day old, but Even though the search function allows "*" wildcards, performing a search for "*" and specifying only a date restriction doesn't seem to work. Should it? I think it would be nice.

Here's a tip for people having DNS lookup problems.

If you think you are having a DNS problem, and you suspect the problem is at your ISP (say, you've cleared your computers DNS cache by restarting and you still have the problem), then one way to fix this is by using a different set of DNS name servers other than your ISPs.

One way to try a different set of name servers is to go to www.opendns.com, click on the "Get Started" link and follow the instructions for your OS. Don't forget to write down the changes you make to your configuration, as you may want to change back. but it's really a pretty simple process.

If you switch to the opendns name servers and then see your problem has been fixed, then you know that your ISP is likely the cause of the problem.

Just as a disclaimer, I believe that opendns currently only has servers running in the US. If your connectiviy to the US is slow, this could slow down your browsing across the board (but probably only by a little bit). On the other hand, they say their servers are very fast, so maybe it'll speed things up for you. It's pretty easy to try out, so you can see yourself. Also, I am not connected to this site in any way, but I did try it out on my system, and it looks to me like they do what they say they do.

Anonymous wrote:

Do you run Windows XP? I'm strictly a Linux person myself, so I can try to help, but I hope I don't make a mistake.

I googled for instructions for XP, and it looks like the command to show your nameservers is "ipconfig /all".
(Click Start...Run....cmd....then type ipconfig /all at the command prompt).

Give that a try and let me know what your nameservers are. Or post the output if you don't understand it. And if you don't run XP, then tell us what OS you are running, and we can look up the instructions for it.

Hopefully, when we know your nameservers, I can query them with the dig command to see if they are using reasonable timeouts. If they are, then we know we have to continue looking elsewhere for the cause of your problem. If they aren't reasonable, then we have to contact your ISP to see what's up. It could take a little time and patience, but I'm sure we can get things sorted.

Or you could try your ISP help desk again. It really is their responsibility to make sure their users have good network connections.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\admin>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : C2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gateway.2wire.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethe
rnet NIC
Physical Address. . . . . . . . . : 00-0B-6A-D4-45-F9
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.67
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 165.21.83.88
165.21.100.88
Lease Obtained. . . . . . . . . . : 12 July 2006 20:09:58
Lease Expires . . . . . . . . . . : 13 July 2006 20:09:58

it's all juz something like that... dunno which one's the nameservers...
arh... i feel like such a noob.. lol. :bonk:
thanks again anyway!!

The nameservers are the DNS Servers. (Domain Name System) (165.21.83.88, 165.21.100.88 )

I tried the dig command with those, but I always dnd up with connection timeout errors. :puppydog: I must be doing something wrong. :banghead:

I was able to "dig" your nameservers from where I am, and it looks like they are using reasonable timeout values, nothing huge or strange. At this point I think that your ISP is ok.

Weird. Can routers cache DNS? :headscratch:

tabana wrote:Weird. Can routers cache DNS? :headscratch:

Routers that are part of the internet infrastructure? I don't think so.

Home routers? I don't know. I think that would be a misfeature ... but you never know what can happen these days.

I was thinking about home routers, but I guess you're right, that wouldn't be very useful. :sweat:

š wrote:

Routers that are part of the internet infrastructure? I don't think so.

Home routers? I don't know. I think that would be a misfeature ... but you never know what can happen these days.

I think it's pretty clear it's their issue, no one from their internet service can access this websites new server by domain name, yet no one else not a single person has an issue from another isp?

Please let me know how that makes sense to you?

Anonymous wrote:I think it's pretty clear it's their issue, no one from their internet service can access this websites new server by domain name, yet no one else not a single person has an issue from another isp?

Please let me know how that makes sense to you?

Ah, I didn't know that, I sort of jumped in on this conversation half way through. You say that you know other people on the same ISP also have the same problem? Then the problem is with the ISP, but it may not be a problem with DNS caching ... at least on those two nameservers you use.

Perhaps they use some weird web caching proxy system? Some ISPs do route all outgoing web traffic through a caching proxy in order to save bandwidth.

I think the best solution is to keep calling them and tell them that they haven't fixed the problem and that you still can't reach jdorama.com.

Also, as a test, you might also be able to get around a malfunctioning web proxy by telling your browser to use some other web proxy that uses a non-standard port. I'll go see if I can find one for you.

Ok, let's say we think your ISP may be running a transparent caching web proxy, one way to find out is to try some on-line test, like this one:

http://www.all-nettools.com/toolbox,net
(scroll down and click the CHECK! button under the "Proxy test" section).
Does it say "Proxy server detected"?

or try this one:
http://www.broadband-help.com/cm_diagnose.asp?init=1
Under "Proxy Information" at the bottom of the screen, does it say "Proxied HTTP? Yes"?

Can you give these tests a try and let us know if they detect a proxy?


(Edit Update...)

If you find you are using a proxy, that proxy will also be a suspect for the problems you are having. We can try a different proxy in an experiment to see if that supports that hypothesis :)

The thing about transparent proxies, is that they generally work by "grabbing" all your network traffic that goes to some other site's port 80. Port 80 is the standard www port used by web servers. They could also grab traffic on other ports, but knowing if they do that is a little more difficult.

Anyway, this is to say, if we try using a proxy that does not use port 80, maybe we'll see a difference in behavior, and that would indicate a problem in your ISPs transparent proxy.

To find another proxy to use, you can search on google for "(free|open) proxy servers", or something like that. Here's one site I found: proxyforest.com. It's in Japanese, but the list of proxies it has is in English.

Find a proxy on the list that does not use port 80 (warning, some will not work, so this could require some experimentation). For example, I just tried 201.242.177.232:8080 (that's given as IP : Port), and it worked for me. Now edit your browser's proxy information preferences to set the proxy IP to 201.242.177.232 and the port to 8080. If that doesn't work, just undo that information and try another one.

Once you've changed your browser to use another proxy, you can go to some site like ipchicken.com that will tell you your IP address and see
if it has changed. If it has, you were successful in correctly setting up your proxy settings. Now try visiting jdorama.com and see if you see a difference in behavior.

This isn't 100% guaranteed foolproof experiment, but if using a different proxy allows you to access the site, then it does put some heavy suspicion on your ISP's transparent proxy.

P.S. using one of these other proxies is almost always going to slow down your internet browsing, so don't forget to undo the changes you make after you are done.

I hope this information is a little useful to anyone who is having problems accessing the site. I know it may sound complicated, so I guess the best advice is to try your ISP help desk first, but if you feel frustrated by them or a little adventurous, give this method a try. Good luck.

I know several people that have the same isp as this user, and their isp does use caching proxies.

Anonymous wrote:I know several people that have the same isp as this user, and their isp does use caching proxies.

Good to know. Caching proxies can certainly screw up like this from time to time. And if everyone at that ISP has this same problem ... well, it's looking more and more like the proxy might be the cause.

Switching proxies may show this more conclusively.

OMG!!! IT WORKS!!! :dancing: YAY!!
THANK YOU THANK YOU THANK YOU THANK YOU SO MUCH!!! :bow:
I dunno how I can ever repay you all.. :hug:

bcgurl wrote:OMG!!! IT WORKS!!! :dancing: YAY!!
THANK YOU THANK YOU THANK YOU THANK YOU SO MUCH!!! :bow:
I dunno how I can ever repay you all.. :hug:

I'm glad your problem got fixed. Did it just fix itself? (Maybe the ISP rebooted their proxy and flushed its cache :) ) Or did you or the ISP figure it out?

bcgurl wrote:OMG!!! IT WORKS!!! :dancing: YAY!!
THANK YOU THANK YOU THANK YOU THANK YOU SO MUCH!!! :bow:
I dunno how I can ever repay you all.. :hug:

Welcome back. :victory:

š wrote:

I'm glad your problem got fixed. Did it just fix itself? (Maybe the ISP rebooted their proxy and flushed its cache :) ) Or did you or the ISP figure it out?

I dunno.. I just followed your way of switching the proxies and it just worked.. :mrgreen:

By the way, there's this problem I dunno how to fix. Sometimes I just go to any site or any page there will be an error message saying "The connection was refused when attempting to conatct the proxy server you have configured." Is there any way to solve this or do I just keep on reloading the page?