Networking Forums

Networking Forums > Network Hardware > Broadband Hardware > Cannot find server dns error (single website not accessible)

Reply
Thread Tools Display Modes

Cannot find server dns error (single website not accessible)

 
 
Shawn
Guest
Posts: n/a

 
      09-21-2004, 03:15 AM
using a MN500 and a cable connection to internet. When we
use the MN500 now (since last thursday) we can't access a
website (http://www.utep.edu). if we unplug the wireless,
and go straight into the cable modem, we can access said
site. Is this a problem with the new SP2 firewall, or the
MN500? I tried the MTU fix mentioned on the board, but
that really didn't have anything to do with our situation
anyway, I don't think.
 
Reply With Quote
 
 
 
 
joker
Guest
Posts: n/a

 
      09-21-2004, 02:44 PM
Do a tracert with a direct connection & one using the router.


Post the results here.

Shawn wrote:

> using a MN500 and a cable connection to internet. When we
> use the MN500 now (since last thursday) we can't access a
> website (http://www.utep.edu). if we unplug the wireless,
> and go straight into the cable modem, we can access said
> site. Is this a problem with the new SP2 firewall, or the
> MN500? I tried the MTU fix mentioned on the board, but
> that really didn't have anything to do with our situation
> anyway, I don't think.


 
Reply With Quote
 
Shawn
Guest
Posts: n/a

 
      09-22-2004, 01:23 AM
tracert www.utep.edu
(directly into cable modem)

Tracing route to www.utep.edu [129.108.1.15]
over a maximum of 30 hops:

1 14 ms 14 ms 13 ms 10.97.64.1
2 26 ms 8 ms 11 ms srp2-0.elpstxhe-
rtr2.elp.rr.com [24.92.99.206]
3 20 ms 19 ms 22 ms pos2-2.austtxrdc-
rtr4.elp.rr.com [24.92.99.10]
4 19 ms 20 ms 21 ms pos6-0.austtxrdc-
rtr6.texas.rr.com [24.93.33.101
]
5 23 ms 23 ms 31 ms 192.124.226.17
6 44 ms 43 ms 43 ms elp-gw-a8-0-0-1.tx-bb.net
[192.12.10.166]
7 36 ms 35 ms 40 ms utep-gw.tx-bb.net
[192.12.10.58]
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




this one is with the Microsoft Wireless plugged in, then
with the IP address to the site:



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

C:\Documents and Settings\Mom>tracert www.utep.edu
Unable to resolve target system name www.utep.edu.

C:\Documents and Settings\Mom>tracert

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w
timeout] target_name

Options:
-d Do not resolve addresses to
hostnames.
-h maximum_hops Maximum number of hops to search
for target.
-j host-list Loose source route along host-list.
-w timeout Wait timeout milliseconds for each
reply.

C:\Documents and Settings\Mom>tracert www.utep.edu
Unable to resolve target system name www.utep.edu.

C:\Documents and Settings\Mom>tracert 129.108.1.15

Tracing route to 129.108.1.15 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.2.1
2 10 ms 8 ms 10 ms 10.97.64.1
3 9 ms 17 ms 10 ms srp2-0.elpstxhe-
rtr2.elp.rr.com [24.92.99.206]
4 23 ms 20 ms 22 ms pos2-2.austtxrdc-
rtr4.elp.rr.com [24.92.99.10]
5 20 ms 22 ms 22 ms pos6-0.austtxrdc-
rtr6.texas.rr.com [24.93.33.101
]
6 24 ms 23 ms 23 ms 192.124.226.17
7 35 ms 36 ms 34 ms elp-gw-a8-0-0-1.tx-bb.net
[192.12.10.166]
8 42 ms 48 ms 37 ms utep-gw.tx-bb.net
[192.12.10.58]
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
>-----Original Message-----
>Do a tracert with a direct connection & one using the

router.
>
>
>Post the results here.
>
>Shawn wrote:
>
>> using a MN500 and a cable connection to internet. When

we
>> use the MN500 now (since last thursday) we can't access

a
>> website (http://www.utep.edu). if we unplug the

wireless,
>> and go straight into the cable modem, we can access

said
>> site. Is this a problem with the new SP2 firewall, or

the
>> MN500? I tried the MTU fix mentioned on the board, but
>> that really didn't have anything to do with our

situation
>> anyway, I don't think.

>
>.
>

 
Reply With Quote
 
Joker
Guest
Posts: n/a

 
      09-22-2004, 11:15 AM
Dang. It looks like once you reach their network at IP address
"192.12.10.58" they don't respond to ping requests, which is what the
tracert is doing.

What is the DNS set to on the computer then?

What is the DNS set to on the router (in the WAN Page)? (Is it set to
dynamic or static?)

Shawn wrote:

> tracert www.utep.edu
> (directly into cable modem)


> 7 36 ms 35 ms 40 ms utep-gw.tx-bb.net
> [192.12.10.58]
> 8 * * * Request timed out.
>
> this one is with the Microsoft Wireless plugged in, then
> with the IP address to the site:
>
>
> C:\Documents and Settings\Mom>tracert www.utep.edu
> Unable to resolve target system name www.utep.edu.
>


> C:\Documents and Settings\Mom>tracert 129.108.1.15
>
> Tracing route to 129.108.1.15 over a maximum of 30 hops
>
> 8 42 ms 48 ms 37 ms utep-gw.tx-bb.net
> [192.12.10.58]
> 9 * * * Request timed out.


 
Reply With Quote
 
Guest
Posts: n/a

 
      09-24-2004, 02:17 AM
now yesterday, the website showed up...here's the tracert
on it now:

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

C:\Documents and Settings\Mom>tracert www.utep.edu

Tracing route to www.utep.edu [129.108.1.15]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 12 ms 10 ms 8 ms 10.97.64.1
3 14 ms 9 ms 20 ms srp2-0.elpstxhe-
rtr2.elp.rr.com [24.92.99.206]
4 25 ms 21 ms 25 ms pos2-2.austtxrdc-
rtr4.elp.rr.com [24.92.99.10]
5 28 ms 21 ms 37 ms pos6-0.austtxrdc-
rtr6.texas.rr.com [24.93.33.101
]
6 33 ms 28 ms 39 ms 192.124.226.17
7 37 ms 48 ms 70 ms elp-gw-a8-0-0-1.tx-bb.net
[192.12.10.166]
8 37 ms 45 ms 39 ms utep-gw.tx-bb.net
[192.12.10.58]
9 * * * Request timed out.
10 *
>-----Original Message-----
>Dang. It looks like once you reach their network at IP

address
>"192.12.10.58" they don't respond to ping requests, which

is what the
>tracert is doing.
>
>What is the DNS set to on the computer then?
>
>What is the DNS set to on the router (in the WAN Page)?

(Is it set to
>dynamic or static?)
>
>Shawn wrote:
>
>> tracert www.utep.edu
>> (directly into cable modem)

>
>> 7 36 ms 35 ms 40 ms utep-gw.tx-bb.net
>> [192.12.10.58]
>> 8 * * * Request timed out.
>>
>> this one is with the Microsoft Wireless plugged in,

then
>> with the IP address to the site:
>>
>>
>> C:\Documents and Settings\Mom>tracert www.utep.edu
>> Unable to resolve target system name www.utep.edu.
>>

>
>> C:\Documents and Settings\Mom>tracert 129.108.1.15
>>
>> Tracing route to 129.108.1.15 over a maximum of 30 hops
>>
>> 8 42 ms 48 ms 37 ms utep-gw.tx-bb.net
>> [192.12.10.58]
>> 9 * * * Request timed out.

>
>.
>

 
Reply With Quote
 
Guest
Posts: n/a

 
      09-24-2004, 02:19 AM
almost forgot: DNS is:
Primary Domain Name System (DNS): 24.93.40.64

and WAN is Dynamic
>-----Original Message-----
>Dang. It looks like once you reach their network at IP

address
>"192.12.10.58" they don't respond to ping requests, which

is what the
>tracert is doing.
>
>What is the DNS set to on the computer then?
>
>What is the DNS set to on the router (in the WAN Page)?

(Is it set to
>dynamic or static?)
>
>Shawn wrote:
>
>> tracert www.utep.edu
>> (directly into cable modem)

>
>> 7 36 ms 35 ms 40 ms utep-gw.tx-bb.net
>> [192.12.10.58]
>> 8 * * * Request timed out.
>>
>> this one is with the Microsoft Wireless plugged in,

then
>> with the IP address to the site:
>>
>>
>> C:\Documents and Settings\Mom>tracert www.utep.edu
>> Unable to resolve target system name www.utep.edu.
>>

>
>> C:\Documents and Settings\Mom>tracert 129.108.1.15
>>
>> Tracing route to 129.108.1.15 over a maximum of 30 hops
>>
>> 8 42 ms 48 ms 37 ms utep-gw.tx-bb.net
>> [192.12.10.58]
>> 9 * * * Request timed out.

>
>.
>

 
Reply With Quote
 
Joker
Guest
Posts: n/a

 
      09-24-2004, 04:43 PM
I that set in the router or the computer?

(E-Mail Removed) wrote:
> almost forgot: DNS is:
> Primary Domain Name System (DNS): 24.93.40.64
>
> and WAN is Dynamic
>
>>-----Original Message-----
>>Dang. It looks like once you reach their network at IP

>
> address
>
>>"192.12.10.58" they don't respond to ping requests, which

>
> is what the
>
>>tracert is doing.
>>
>>What is the DNS set to on the computer then?
>>
>>What is the DNS set to on the router (in the WAN Page)?

>
> (Is it set to
>
>>dynamic or static?)
>>
>>Shawn wrote:
>>
>>
>>>tracert www.utep.edu
>>>(directly into cable modem)

>>
>>> 7 36 ms 35 ms 40 ms utep-gw.tx-bb.net
>>>[192.12.10.58]
>>> 8 * * * Request timed out.
>>>
>>>this one is with the Microsoft Wireless plugged in,

>
> then
>
>>>with the IP address to the site:
>>>
>>>
>>>C:\Documents and Settings\Mom>tracert www.utep.edu
>>>Unable to resolve target system name www.utep.edu.
>>>

>>
>>>C:\Documents and Settings\Mom>tracert 129.108.1.15
>>>
>>>Tracing route to 129.108.1.15 over a maximum of 30 hops
>>>
>>> 8 42 ms 48 ms 37 ms utep-gw.tx-bb.net
>>>[192.12.10.58]
>>> 9 * * * Request timed out.

>>
>>.
>>


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Website not accessible on 2003 server lei Windows Networking 1 12-13-2006 11:45 PM
Cannot Find Server or DNS error (Tried everything) ripdoozer@yahoo.com Wireless Internet 4 07-13-2006 03:04 AM
cannot find server or dns error l kellar Broadband Hardware 1 03-17-2005 10:45 PM
Can't find server error sporatically with mn 700 Broadband Hardware 1 07-18-2004 01:43 AM
can't find server error kyle Broadband Hardware 1 06-27-2004 08:15 PM



1 2 3 4 5 6 7 8 9 10 11