Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 246
  • Last Modified:

I can not reach a particular url from my lan but can reach it from a network outside my lan?

Microsoft network with 2k dc and xp pro/2k pro ws's.  All running behind a linksys router connected to an adtran which has a T1 connected to it.  Network seems to work fine and I can access the internet.  There are some urls that I can not access (i.e www.abss.nc.us).  I called a friend at another business and he has no problem getting to the site.  I tried firefox and ie with no luck.  They both seem to time out.  Any ideas?  Thanks Dale
0
DaleFrazier
Asked:
DaleFrazier
  • 5
  • 3
  • 3
  • +2
1 Solution
 
Pete LongConsultantCommented:
I cant get to that URL ?
0
 
rsivanandanCommented:
Well, I can't seem to open it.

Is it something that started today ? May be the site is down and the guy you called have looked at the browser cached version ?

Have him navigate onto different pages on the site and see if he can.

Cheers,
Rajesh
0
 
Pete LongConsultantCommented:
Heres mr trying from THREE different DNS servers to get it no joy


C:\Documents and Settings\pete>nslookup www.abss.nc.us
Server:  con2k-sql.coniston.co.uk
Address:  10.1.0.9

*** con2k-sql.coniston.co.uk can't find www.abss.nc.us: Non-existent domain

C:\Documents and Settings\pete>nslookup
Default Server:  con2k-sql.coniston.co.uk
Address:  10.1.0.9

> server 194.164.4.100
Default Server:  [194.164.4.100]
Address:  194.164.4.100

www.abss.nc.us
Server:  [194.164.4.100]
Address:  194.164.4.100

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to [194.164.4.100] timed-out
> server 194.42.224.130
DNS request timed out.
    timeout was 2 seconds.
Default Server:  [194.42.224.130]
Address:  194.42.224.130

www.abss.nc.us
Server:  [194.42.224.130]
Address:  194.42.224.130

DNS request timed out.
    timeout was 2 seconds.
*** [194.42.224.130] can't find www.abss.nc.us: Non-existent domain
>



0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 
prashsaxCommented:
Call your friend who can access it.

Ask him to do a nslookup for this domain and send you the IP address.

For doing nslookup, open command prompt.
Start->run->cmd

nslookup www.abss.nc.us

This should return some IP address.


0
 
DaleFrazierAuthor Commented:
So sorry experts.  I gave you the wrong address.  Try this one,

www.abss.k12.nc.us.  
0
 
prashsaxCommented:
This is the IP address: 216.166.215.68

Try and do a tracert to this address.

See, if you ISP is blocking access to this IP.
0
 
rsivanandanCommented:
That is better, I can reach it.

Try to do the nslookup for this particular domain along with what Prashsax mentioned.

Cheers,
Rajesh
0
 
DaleFrazierAuthor Commented:
I did a tracert, went 30 hops, then timed out.  Nslookup showed something.  Still can't reach the site!

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

C:\Documents and Settings\Dale>tracert 216.166.215.68

Tracing route to 216-166-215-68.clec.commercial.madisonriver.net [216.166.215.68
]
over a maximum of 30 hops:

  1     7 ms    14 ms     3 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 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.

C:\Documents and Settings\Dale>nslookup
*** Can't find server name for address 192.168.1.2: Non-existent domain
*** Default servers are not available
Default Server:  UnKnown
Address:  192.168.1.2

> exit

C:\Documents and Settings\Dale>nslookup 216.166.215.68
*** Can't find server name for address 192.168.1.2: Non-existent domain
*** Default servers are not available
Server:  UnKnown
Address:  192.168.1.2

Name:    216-166-215-68.clec.commercial.madisonriver.net
Address:  216.166.215.68


C:\Documents and Settings\Dale>
0
 
prashsaxCommented:
It could be possible that ICMP is disabled by your ISP thats why you don't see any hops at all.

Can you do a tracert for say google.com

If you can't then for sure ICMP is disabled.

In that case, use TRACETCP.
http://sourceforge.net/project/showfiles.php?group_id=88080&package_id=92014&release_id=329356
Its a software to do tracert using TCP instead of icmp.

Syntax is:
tracetcp 216.166.215.68:80 -m 30


0
 
DaleFrazierAuthor Commented:
google tracert works like a charm.  Any other ideas?
0
 
Pete LongConsultantCommented:
what about remote traces to this ip/domain

Trace Route's Externally


In case you need to perform some traceroutes
just pick one of the trace servers below, fire up
telnet and connect to the selected host
then just enter the command "trace host"
e.g. trace www.google.com or trace 64.233.179.104
and look at the trace results; those servers come
handy when it comes to diagnosing connectivity or
speed issues since they allow you to perform
some cross tests and point out which routing node
is causing issues or slowing down your traffic

here we go ...

route-server.ip.att.net         ATT Route Server
ner-routes.bbnplanet.net        BBN Planet NER Route Server
route-server.cerf.net           CerfNet Route Server
route-server.colt.net           Colt Internet Route Server
route-server-ap.exodus.net      Exodus Communications Asia Route Server
route-server-eu.exodus.net      Exodus Communications Europe Route Server
route-server.exodus.net         Exodus Communications USA Route Server
route-server.gblx.net           Global Crossing Route Server
216.18.63.214                   Group Telecom Route Server
route-server.he.net             Hurricane Electric Route Server
route-views.oregon-ix.net       Oregon Exchange Route Server
route-server.as5388.net         Planet Online Route Server
route-server.savvis.net         SAVVIS Communications Route Server
grh.sixxs.net                   SixXS GRH Route Server
route-views.on.bb.telus.com     TELUS Eastern Canada Route Server
route-views.ab.bb.telus.com     TELUS Western Canada Route Server
route-server.ip.tiscali.net     Tiscali Route Server

btw there are some more, but I think the above servers may
suffice for most "quick diagnostic" purposes you may have :)
0
 
DaleFrazierAuthor Commented:
Ok, hop 16 is my default gateway given to me by my isp, uslec.  But what does all this mean???

CCC
############## route-server.ip.att.net ###############
#########  AT&T IP Services Route Monitor  ###########

This router maintains peerings with customer-facing routers
throughout the AT&T IP Services Backbone:

 12.123.21.243   Atlanta, GA             12.123.133.124  Austin, TX
 12.123.41.250   Cambridge, MA           12.123.5.240    Chicago,IL
 12.123.17.244   Dallas, TX              12.123.139.124  Detroit, MI
 12.123.37.250   Denver, CO              12.123.134.124  Houston, TX
 12.123.29.249   Los Angeles, CA         12.123.1.236    New York, NY
 12.123.33.249   Orlando,FL              12.123.137.124  Philadelphia, PA
 12.123.142.124  Phoenix, AZ             12.123.145.124  San Diego, CA
 12.123.13.241   San Francisco, CA       12.123.25.245   St. Louis, MO
 12.123.45.252   Seattle, WA             12.123.9.241    Washington, DC

This router has the global routing table view from each of the above
routers, providing a glimpse to the Internet routing table from the
AT&T network's perspective.

*** Please Note:

Ping and traceroute delay figures measured with this box are unreliable,
due to the high CPU load this box experiences when complicated "show" commands
are being executed.

For questions about this route-server, send email to: jayb@att.com

#################### route-server.ip.att.net ####################

route-server>trace 216.48.47.170

Type escape sequence to abort.
Tracing the route to 216.48.47.170

  1 white_dwarf.cbbtier3.att.net (12.0.1.1) [AS 7018] 0 msec 0 msec 0 msec
  2 ar13.s10-0-0.n54ny.ip.att.net (12.124.182.17) [AS 7018] 400 msec 204 msec 20
0 msec
  3 tbr2-p012109.n54ny.ip.att.net (12.123.0.46) [AS 7018] [MPLS: Label 32252 Exp
 0] 200 msec 204 msec 200 msec
  4 ggr3-ge140.n54ny.ip.att.net (12.122.80.237) [AS 7018] 200 msec 200 msec 204
msec
  5 att-gw.dc.aol.com (192.205.32.2) [AS 7018] 204 msec 200 msec 200 msec
  6 0.ge-5-1-0.XL3.NYC4.ALTER.NET (152.63.3.125) [AS 701] 200 msec 208 msec 200
msec
  7 0.so-7-0-0.XL1.ATL4.ALTER.NET (152.63.86.106) [AS 701] 200 msec 200 msec 200
 msec
  8 POS6-0.GW1.ATL4.ALTER.NET (152.63.86.81) [AS 701] 160 msec 200 msec 204 msec
  9 uslec-atl-gw.customer.alter.net (157.130.68.10) [AS 701] 200 msec 200 msec 2
00 msec
 10 ge-0-1-0-0.core2.atlagamv.uslec.net (207.59.119.17) [AS 1785] 200 msec 200 m
sec 200 msec
 11 so-0-2-0.core1.chrxncrx.uslec.net (169.130.81.69) [AS 1785] 200 msec 200 mse
c 200 msec
 12 ge-0-0-0-0.core2.chrxncrx.uslec.net (207.59.119.90) [AS 1785] 200 msec 200 m
sec 200 msec
 13 so-0-1-2.core2.gnboncph.uslec.net (169.130.80.253) [AS 1785] 200 msec 208 ms
ec 200 msec
 14 ge-0-0-0.core1.gnboncph.uslec.net (169.130.80.97) [AS 1785] 200 msec 200 mse
c 200 msec
 15 ge-8-0-300.edge1.gnboncph.uslec.net (169.130.102.3) [AS 1785] 200 msec 204 m
sec 200 msec
 16 216.48.xx.xxx  [AS 1785] 200 msec 200 msec 200 msec
 17  *  *  *
 18  *  *  *
 19  *  *  *
 20  *  *  *
 21  *  *  *
 22  *  *  *
 23  *  *  *
 24  *  *  *
 25  *  *  *
 26  *  *  *
 27  *  *  *
 28  *  *  *
 29  *  *  *
 30  *  *  *
route-server>CCC
############## route-server.ip.att.net ###############
#########  AT&T IP Services Route Monitor  ###########

This router maintains peerings with customer-facing routers
throughout the AT&T IP Services Backbone:

 12.123.21.243   Atlanta, GA             12.123.133.124  Austin, TX
 12.123.41.250   Cambridge, MA           12.123.5.240    Chicago,IL
 12.123.17.244   Dallas, TX              12.123.139.124  Detroit, MI
 12.123.37.250   Denver, CO              12.123.134.124  Houston, TX
 12.123.29.249   Los Angeles, CA         12.123.1.236    New York, NY
 12.123.33.249   Orlando,FL              12.123.137.124  Philadelphia, PA
 12.123.142.124  Phoenix, AZ             12.123.145.124  San Diego, CA
 12.123.13.241   San Francisco, CA       12.123.25.245   St. Louis, MO
 12.123.45.252   Seattle, WA             12.123.9.241    Washington, DC

This router has the global routing table view from each of the above
routers, providing a glimpse to the Internet routing table from the
AT&T network's perspective.

*** Please Note:

Ping and traceroute delay figures measured with this box are unreliable,
due to the high CPU load this box experiences when complicated "show" commands
are being executed.

For questions about this route-server, send email to: jayb@att.com

#################### route-server.ip.att.net ####################

route-server>trace 216.48.47.170

Type escape sequence to abort.
Tracing the route to 216.48.47.170

  1 white_dwarf.cbbtier3.att.net (12.0.1.1) [AS 7018] 0 msec 0 msec 0 msec
  2 ar13.s10-0-0.n54ny.ip.att.net (12.124.182.17) [AS 7018] 400 msec 204 msec 20
0 msec
  3 tbr2-p012109.n54ny.ip.att.net (12.123.0.46) [AS 7018] [MPLS: Label 32252 Exp
 0] 200 msec 204 msec 200 msec
  4 ggr3-ge140.n54ny.ip.att.net (12.122.80.237) [AS 7018] 200 msec 200 msec 204
msec
  5 att-gw.dc.aol.com (192.205.32.2) [AS 7018] 204 msec 200 msec 200 msec
  6 0.ge-5-1-0.XL3.NYC4.ALTER.NET (152.63.3.125) [AS 701] 200 msec 208 msec 200
msec
  7 0.so-7-0-0.XL1.ATL4.ALTER.NET (152.63.86.106) [AS 701] 200 msec 200 msec 200
 msec
  8 POS6-0.GW1.ATL4.ALTER.NET (152.63.86.81) [AS 701] 160 msec 200 msec 204 msec
  9 uslec-atl-gw.customer.alter.net (157.130.68.10) [AS 701] 200 msec 200 msec 2
00 msec
 10 ge-0-1-0-0.core2.atlagamv.uslec.net (207.59.119.17) [AS 1785] 200 msec 200 m
sec 200 msec
 11 so-0-2-0.core1.chrxncrx.uslec.net (169.130.81.69) [AS 1785] 200 msec 200 mse
c 200 msec
 12 ge-0-0-0-0.core2.chrxncrx.uslec.net (207.59.119.90) [AS 1785] 200 msec 200 m
sec 200 msec
 13 so-0-1-2.core2.gnboncph.uslec.net (169.130.80.253) [AS 1785] 200 msec 208 ms
ec 200 msec
 14 ge-0-0-0.core1.gnboncph.uslec.net (169.130.80.97) [AS 1785] 200 msec 200 mse
c 200 msec
 15 ge-8-0-300.edge1.gnboncph.uslec.net (169.130.102.3) [AS 1785] 200 msec 204 m
sec 200 msec
 16 216.48.47.169 [AS 1785] 200 msec 200 msec 200 msec
 17  *  *  *
 18  *  *  *
 19  *  *  *
 20  *  *  *
 21  *  *  *
 22  *  *  *
 23  *  *  *
 24  *  *  *
 25  *  *  *
 26  *  *  *
 27  *  *  *
 28  *  *  *
 29  *  *  *
 30  *  *  *
route-server>
0
 
DaleFrazierAuthor Commented:
I fixed the problem myself by power cycling my linksys router.  I guess it was holding on to an old route to this particular url.  Thanks for your help anyway experts.

Dale
0
 
ee_ai_constructCommented:
PAQ / Refund
ee ai construct, community support moderator
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

  • 5
  • 3
  • 3
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now