Reviewers Recommend
Naughty Office 102Naughty Office 102 - review by Captain Jack
Starring: Reagan Foxx, Jewelz Blu, April Olsen, Kay Lovely, Charli Phoenix. Read review
All Forums > Shopping Info > Shopping Info Forum Page 24 > Can't get no Suga!!!!
AuthorPost
GonzoAnalFan
Member

700 Posts
6/04
Posted - Aug 4 2005 : 4:00AM
Anyone else having trouble accessing ANY parts of Sugardvd.com??

I've been unable to connect for a couple of days now ;(

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

GonzoAnalFan
Member

700 Posts
6/04
Posted - Aug 5 2005 : 5:08AM
Bump! (for the ENTIRE forum....no posts AT ALL in over 25hrs!!)
infimum
Member

189 Posts
3/04
Posted - Aug 5 2005 : 8:57AM
It works fine for me. I'm afraid you are alone in this thread
GonzoAnalFan
Member

700 Posts
6/04
Posted - Aug 6 2005 : 2:52AM
This doesn't make any sense & I'm getting extremely frustrated!

Any ideas? (I'm able to connect flawlessly to EVERY webpage imaginable)

Hardware All-Star Supporter
All-Star Member

Your other left
14594 Posts
3/02
Posted - Aug 6 2005 : 3:43AM
Maybe you've got a DNS problem. Try going to http:\\66.240.152.5
 
GonzoAnalFan
Member

700 Posts
6/04
Posted - Aug 7 2005 : 1:30AM
No success....what does this mean?

(I can access EVERY single site perfectly fine, just abruptly can't access this particular address)

TIA ;)

Edited by - GonzoAnalFan on 8/7/2005 1:30:37 AM

Hardware All-Star Supporter
All-Star Member

Your other left
14594 Posts
3/02
Posted - Aug 7 2005 : 4:09AM
Well, it could mean that your ISP is blocking that address, or the block of addresses it comes from. If you're running Windows you can try doing a traceroute and see whether or not that succeeds. You need to open a 'Command prompt' window though. The command is:

tracert 66.240.152.5

Here's an example of what you should get back, though the path from your PC won't be the same (hmm, interesting that RARP resolved the address to the name mail.oddesse.net):

C:\Documents and Settings\Administrator>tracert 66.240.152.5

Tracing route to mail.oddesse.net [66.240.152.5]
over a maximum of 30 hops:

1 25 ms 25 ms 25 ms L100.DSL-04.DLLSTX.verizon-gni.net [71.97.0.1]
2 25 ms 25 ms 24 ms P1-3.LCR-01.DLLSTX.verizon-gni.net [130.81.34.56]
3 27 ms 27 ms 26 ms so-6-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [130.81.17.173]
4 27 ms 26 ms 26 ms dal-edge-11.inet.qwest.net [65.115.192.89]
5 26 ms 27 ms 25 ms dal-core-02.inet.qwest.net [205.171.25.149]
6 26 ms 25 ms 26 ms dap-brdr-01.inet.qwest.net [205.171.225.53]
7 27 ms 26 ms 26 ms qwest-gw.dlstx.ip.att.net [192.205.32.145]
8 61 ms 60 ms 60 ms tbr1-p012101.dlstx.ip.att.net [12.123.17.82]
9 59 ms 60 ms 61 ms tbr1-cl2.la2ca.ip.att.net [12.122.10.50]
10 57 ms 58 ms 57 ms gar2-p310.lsrca.ip.att.net [12.123.199.117]
11 58 ms 58 ms 58 ms 12.118.130.78
12 * * * Request timed out.
13 63 ms 59 ms 59 ms mail.oddesse.net [66.240.152.5]

Trace complete.

C:\Documents and Settings\Administrator>

If you look at that trace, you can see that my provider is Verizon. The trace goes through several of their routers before being handed off to QWest, which passes the trace through its network and on to AT&T, which passes it to a core router at 12.118.130.78 (which is programmed to not give out its name), which delivers the packet to the address I'm trying to trace.

If your ISP is blocking the address, then you'll probably only get one or two lines before you get a string of '* * * Request timed out' messages and a notice the trace failed.

GonzoAnalFan
Member

700 Posts
6/04
Posted - Aug 7 2005 : 5:58PM
Tracing route to mail.oddesse.net [66.240.152.5]
over a maximum of 30 hops:

1 9 ms 8 ms 11 ms 10.239.10.1
2 11 ms 13 ms 24 ms 68.86.109.141
3 9 ms 23 ms 10 ms 68.86.106.165
4 11 ms 9 ms 9 ms 68.86.106.161
5 10 ms 9 ms 13 ms 68.86.106.142
6 29 ms 10 ms 9 ms 68.86.106.146
7 12 ms 9 ms 14 ms 68.86.106.150
8 11 ms 11 ms 11 ms 68.86.106.154
9 10 ms 20 ms 23 ms 68.86.106.158
10 12 ms 10 ms 10 ms 12.124.64.21
11 * 53 ms 54 ms tbr2-p013801.attga.ip.att.net [12.123.21.101]
12 61 ms 58 ms 57 ms tbr1-cl1.dlstx.ip.att.net [12.122.2.89]
13 54 ms 55 ms 52 ms tbr1-cl2.la2ca.ip.att.net [12.122.10.50]
14 52 ms 65 ms 53 ms gar2-p300.lsrca.ip.att.net [12.123.199.105]
15 70 ms 60 ms 63 ms 12.118.130.78
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Edited by - GonzoAnalFan on 8/7/2005 6:03:51 PM

Hardware All-Star Supporter
All-Star Member

Your other left
14594 Posts
3/02
Posted - Aug 7 2005 : 10:43PM
Yeah, that looks like your ISP may be blocking it. You should contact them and ask.
GonzoAnalFan
Member

700 Posts
6/04
Posted - Aug 7 2005 : 11:14PM
Wow!....that sure sucks ass.

Strange how they've allowed it until now (They=Comcast Cable)

Thanks a lot Hardware.

GonzoAnalFan
Member

700 Posts
6/04
Posted - Aug 8 2005 : 12:17AM
I just spoke with Comcast, they said they're gonna (hopefully) fix it.
Hardware All-Star Supporter
All-Star Member

Your other left
14594 Posts
3/02
Posted - Aug 8 2005 : 2:26AM
Since the address resolves to mail.oddesse.net it would appear that somebody's using, or has previously used, that address for a mail server, in which case it could have been tagged as a spammer at some point.
GonzoAnalFan
Member

700 Posts
6/04
Posted - Aug 30 2005 : 2:11AM
Suddenly got fixed (by Comcast, I guess) a week ago ;)
Hardware All-Star Supporter
All-Star Member

Your other left
14594 Posts
3/02
Posted - Aug 30 2005 : 4:14AM
Well, they won't win any prize for speedy service, but at least they did fix it.



Jump To: