[AccessD] DBA web site search Archives

Andy Lacey andy at minstersystems.co.uk
Wed May 4 01:41:40 CDT 2005


Thanks Greg. Mine gets as far as your line 13 (inaddr.G4.NET) then
repeatedly gives request timed out. I've no idea why. Have asked my isp to
look at it.

-- Andy Lacey
http://www.minstersystems.co.uk 

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Greg Smith
> Sent: 04 May 2005 04:22
> To: 'Access Developers discussion and problem solving'
> Subject: RE: [AccessD] DBA web site search Archives
> 
> 
>  
> Here's a copy of my tracert from home...via Starband.Net 
> which can be from either Virginia or Georgia, depending on 
> the weather ('weather' or not it'll work right...;): Ignore 
> my ping times...it's a satellite waaaay out there. )I 
> obviously do not play Halo online and live very long to talk 
> about it...)
> 
> Tracing route to www.databaseadvisors.com [66.211.140.127]
> over a maximum of 30 hops:
> 
>   1     1 ms     1 ms     1 ms  192.168.0.1
>   2     *        *        *     Request timed out.
>   3   787 ms   641 ms     *     misc-148-78-243-2.pool.starband.net
> [148.78.243.2]
>   4  1248 ms   672 ms   768 ms  e00.atl.ge4-0-35.wvfiber.net 
> [63.223.3.117]
>   5  2619 ms   704 ms   704 ms  atl-ix.gnaps.net [198.32.132.16]
>   6   696 ms   704 ms     *     ge-0-1-0.br1.atl1.gnaps.net 
> [199.232.225.6]
>   7   721 ms   672 ms  1377 ms  at-1-1-0.br1.res1.va.gnaps.net
> [199.232.44.49]
>   8   703 ms     *     1976 ms  ge-1-0-0.br1.nyc1.ny.gnaps.net
> [199.232.131.16]
>   9  2082 ms   736 ms   768 ms  ge-0-2-0.br1.qcy1.ma.gnaps.net
> [199.232.44.1]
>  10  3422 ms   640 ms   672 ms  fe-2-3.manchester0-2.nh.G4.net
> [216.177.5.161]
>  11   696 ms   672 ms  1313 ms  gige-7-1.manchester0-4.nh.G4.net
> [216.177.5.25]
>  12  1441 ms  1313 ms   704 ms  ge-15-1-4009.manchester0-5.nh.G4.net
> [216.177.5.14]
>  13   694 ms   801 ms   672 ms  38.136.211.66.inaddr.G4.NET 
> [66.211.136.38]
>  14   664 ms  1282 ms  1313 ms  www2.korksoft.com [66.211.140.127]
> 
> Trace complete.
> 
> I also ran a trace using Sam Spade and got this:
> 
>  1 192.168.0.1       1ms    1ms    1ms  TTL:  0  (No rDNS)
>  2   No Response      *      *      *                 
>  3 148.78.243.2   1860ms 1878ms 1661ms  TTL:  0
> (misc-148-78-243-2.pool.starband.net ok)
>  4 63.223.3.117   1710ms 1769ms 1550ms  TTL:  0
> (e00.atl.ge4-0-35.wvfiber.net ok)
>  5 198.32.132.16  2808ms 1563ms 3172ms  TTL:  0  
> (atl-ix.gnaps.net probable bogus rDNS: No DNS)  6 
> 199.232.225.6  2652ms 1508ms 3190ms  TTL:  0 
> (ge-0-1-0.br1.atl1.gnaps.net probable bogus rDNS: No DNS)  7 
> 199.232.44.49  2516ms 1399ms 3080ms  TTL:  0 
> (at-1-1-0.br1.res1.va.gnaps.net probable bogus rDNS: No DNS)  
> 8 199.232.131.16 2346ms 1290ms 2971ms  TTL:  0 
> (ge-1-0-0.br1.nyc1.ny.gnaps.net probable bogus rDNS: No DNS)
>  9 199.232.44.1   2218ms 1182ms 2863ms  TTL:  0
> (ge-0-2-0.br1.qcy1.ma.gnaps.net probable bogus rDNS: No DNS)
> 10 216.177.5.161  3502ms 1520ms 2625ms  TTL:  0 
> (fe-2-3.manchester0-2.nh.G4.net probable bogus rDNS: No DNS)
> 11 216.177.5.25   3360ms 1411ms 2515ms  TTL:  0
> (gige-7-1.manchester0-4.nh.G4.net probable bogus rDNS: No DNS)
> 12 216.177.5.14   3208ms 1301ms 2408ms  TTL:  0
> (ge-15-1-4009.manchester0-5.nh.G4.net probable bogus rDNS: No 
> DNS) 13 66.211.136.38  3063ms 1192ms 2284ms  TTL:  0 
> (38.136.211.66.inaddr.G4.NET ok) 14 66.211.140.127 3072ms 
> 1370ms 2174ms  TTL:114  (www2.korksoft.com ok)
> 15 66.211.140.127 2757ms                TTL:114  
> (www2.korksoft.com ok)
> 
> I'm obviously getting through ok and I'm not seeing anything 
> like what you are talking about.
> 
> Greg Smith
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Andy Lacey
> Sent: Tuesday, May 03, 2005 5:02 PM
> To: 'Access Developers discussion and problem solving'
> Subject: RE: [AccessD] DBA web site search Archives
> 
> Not just me getting odd behaviour then. And Lembit had the 
> same problem yesterday but then his cleared. So something odd 
> going on somewhere.
> 
> -- Andy Lacey
> http://www.minstersystems.co.uk 
> 
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of 
> Jim Hewson
> > Sent: 03 May 2005 21:53
> > 
> .
> .
> .
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com 
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> 




More information about the AccessD mailing list