Problems Accessing Site

**mmandjsmom** · 11-12-2007, 01:04 PM

I'm not sure where to post this, so sorry if this is wrong. I am just wondering if anyone else is having any problems accessing the FV website. I have a tough time accessing the site or forums each evening from about 5pm - 10:30pm CST and most of the weekends.

Am I the only one? Does anyone hve an idea why this is? Thanks for the info!

mmandjsmom

**jamie79** · 11-12-2007, 02:04 PM

No I have problems too. I am wondering since your the next state over if we have the same ISP. Mine is Centurytel

**FrugalMomof3** · 11-12-2007, 02:23 PM

I have problems like that once in a while too, I think it has something to do with our ISP cache process.

Nothing we can do since it's not in our hands (so to speak).

**nodmicks** · 11-12-2007, 02:27 PM

I do also. Frequently. I also have centurytel.

**baxjul** · 11-12-2007, 02:32 PM

I'm not having any problems.

**mmandjsmom** · 11-12-2007, 05:05 PM

I have Qwest, so we are not on the same...unless I'm mistaken. I'm glad to hear that it's not just me. Like someone said though, not much I can do. Thanks for the replies!

**coltsmama** · 11-12-2007, 07:16 PM

I have the same peoblem. And it really stinks because it boots me off the internet when I try.

**nodmicks** · 11-13-2007, 08:46 PM

I couldn't get in all morning! I had withdrawl. LOL

**Gabe** · 11-13-2007, 09:22 PM

To trouble shoot this I would recommend that you do a trace route in a DOS session from your connection. It is fairly simple and it would show where the problem lies.

Here is an example of the output of a tracert command in DOS prompt.
Traceroute is also good for speed test, but it also traces the route between the computer and the server
[ame="http://en.wikipedia.org/wiki/Traceroute"]http://en.wikipedia.org/wiki/Traceroute[/ame]

C:\WINDOWS>tracert www.somesite.com

Tracing route to www.somesite.com [64.68.191.111]
over a maximum of 30 hops:

1 119 ms 121 ms 120 ms sym0103723m01.bctel.net [207.102.1.251]
2 107 ms 114 ms 98 ms 207.102.34.249
3 113 ms 117 ms 123 ms 192.197.174.118
4 135 ms 122 ms 116 ms 166.48.13.245
5 134 ms 145 ms 159 ms core7.SanFrancisco.cw.net [204.70.4.93]
6 144 ms 142 ms 136 ms Hssi2-1-0.BR1.SCL1.Alter.Net [206.157.77.74]
7 145 ms 152 ms 147 ms 105.ATM3-0.XR1.SCL1.ALTER.NET [146.188.145.158]
8 138 ms 149 ms 146 ms 195.ATM2-0.TR1.SCL1.ALTER.NET [146.188.146.2]
9 189 ms 170 ms 209 ms 107.ATM6-0.TR1.NYC1.ALTER.NET [146.188.137.165]
10 187 ms 180 ms 180 ms 199.ATM7-0.XR1.BOS1.ALTER.NET [146.188.179.85]
11 194 ms 177 ms 185 ms 191.ATM8-0-0.GW1.BOS1.ALTER.NET [146.188.176.225]
12 196 ms 208 ms 179 ms NVC.customer.UU.NET [64.68.0.242]
13 197 ms 206 ms 207 ms www.somesite.com [64.68.191.111]

The numbers on the left are the so-called "hops". The number of hops that it takes to transmit a packet of data from computer A to computer B is the number of routers. In our example there are 13 hops.

Each response line gives you the HOP #, the round trip times for the 3 packets that were sent and host information (IP address and/or host name).

The roundtrip times for each hop are representative of the time it takes to go from the source to the host for that particular hop and back to the source.

Short times are a good sign. Also, a small number of hops is usually a good sign.

so if you where having problems with connection you would do a traceroute and it will show you where your problem is.