Re: The page cannot be displayed

Tech-Archive recommends: Fix windows errors by optimizing your registry

aa
Date: 02/12/04


Date: Thu, 12 Feb 2004 20:38:21 -0000

Thanks, Ronald.
1. It gets harder and then easier. It's hard trying to figure it out and
when you do, you say, "That was an easy fix."

Is it? You are not a Microsoft salesman, are you?
I have been suffering in this NG with the same question for two months now
and still oneone could offer a fix, even a not an easy one. You probably
noticed that thought I floated several questions, they are about the same
problem.

2. nslookup -q=ns bt.net returns:

Server: my.router
Address: 192.168.1.1
DNS request timed out
    timeout was 2 seconds
DNS request timed out
    timeout was 2 seconds
*** Request to my.router timed out

Please note that I have the same on the other computer which has no "The
page cannot be displayed " problem. Therefore it might not be relevant to my
problem. But in any case it should work as you predicted - what needs
fixing?

3. I got a non-authoritative answer because I do not have a bt.net zone in
my DNS.
How do I find out is I have a bt.net zone in my DNS?

4. I would check the network settings of the router that is not working and
compare it with one that does

I have just one router. All the "network" is two PCs and a router between
them. Well, there is a third PC there, but not to complicate things I
willnot discuss its problems for the moment.

4. Regarding setting DNS on the other computer - I looks like shooting in
the dark hoping to heat something. Why should I change these setting if they
had been working fine for the previous three months, and still work on
another computer?

As you said at the beginning "It's hard trying to figure it out and when you
do, you say, "That was an easy fix."
To be able to say that one needs to understand causes - so far simple logic
tells me that no pint to chane settings on one w2k if the work on another
w2k unless there is a clearly understood reason why.

Probably the result of nslookop mentioned in 2 give you a hint?
"Roland Hall" <nobody@nowhere> wrote in message
news:esYc3ZV8DHA.2656@TK2MSFTNGP11.phx.gbl...
> "aa" wrote:
> : Thnks, Roland.
> : The deeper into the forest, the fatter the freedom-fighters are.
>
> Ya' heavy artillery! (O:=
>
> : I thought that, as the literature says, to network two w2k to share
files
> : and a printer one needs no network knowlegde. Just plug them into the
> router
> : and here you go.
>
> Well, switch perhaps. Router if the router also has a switch.
>
> : No I see how naive I was.
>
> It gets harder and then easier. It's hard trying to figure it out and
when
> you do, you say, "That was an easy fix."
>
> : 1. 130.57.4.70 works OK on all the computers
> : 2. "NAT Port redirection, forwarding and DMZ" - does not make things any
> : clearer for I do not know what DMZ is. Is it necessary to study the
whole
> MS
> : Network+ Certification Course to make two w2k work together :-) ?
>
> I hope not. I'm not A+ certified!
> DMZ is the same as it was in Korea, Vietnam. DeMilitarized Zone. In IT,
> DMZ is an area that has no protection and generally sits between two
> firewalls or off to the side but never within the private network.
> Companies who host their own Internet web servers may choose to put them
in
> the DMZ. It's not a good idea to let public traffic mix with private
unless
> a VPN is used and then it's not really public although it may travel
across
> a public network, like the Internet.
>
> : 3. > This is not a DNS server. Your desktop is pointing it's Primary
DNS
> : server
> : > to the router. If the router could pass the information then you
should
> : > point it there but if not, then you're going to have to point it to
the
> : > ISP's DNS server and make sure port 53 is open on the firewall.
> :
> : Oh, God!
> : a. How I learn if the router could pass the information ?
> : b. How do I point it to the ISP's DNS server and make sure port 53 is
> open
> : on the firewall ?
>
> Simple. Use nslookup which uses port 53 from one of the workstations.
Type
> this in:
>
> nslookup -q=ns bt.net
>
> What you should get is:
>
> Server: (the FQDN (fully qualified domain name) of your DNS server)
> Address: (it's IP address)
>
> Non-authoritative answer:
> bt.net nameserver = ns1.bt.net
> bt.net nameserver = ns2.bt.net
> bt.net nameserver = ns0.bt.net
>
> ns0.bt.net internet address = 194.72.6.51
> ns2.bt.net internet address = 217.35.209.188
>
> I got a non-authoritative answer because I do not have a bt.net zone in my
> DNS.
>
> You will have to do this on the workstation that is working but try on
both.
> The other should have an issue.
>
> : 4. I can browse to http://192.168.1.1 and login to the router settings.
> : But I am very nervous about tempering with them because two other
> computers
> : on this router work fine, therefore the problem should be in the
computer
> : settings, rather then with the router, and changing router might make
> : problems on the other computers, might it not?
>
> I would check the network settings of the router that is not working and
> compare it with one that does. One of them, IMHO, is setting the primary
> DNS setting manually. If the one that works is manual, set the one that
> doesn't work the same. If the one that works is dynamic, then set the
other
> accordingly. I don't believe you have to reboot on W2K after modifying
the
> Primary DNS server.
>
> : However the existing TCP/IP and DHCP settings might be of interest:
> :
> : LAN IP Network Configuration
> : For NAT Usage
> : 1st IP Address : 192.168.1.1
> : 1st Subnet Mask : 255.255.255.0
> : For IP Routing Usage : disabled
> : 2nd IP Address :192.168.2.1
> :
> : 2nd Subnet Mask :255.255.255.0
> :
> : DHCP Server Configuration
> : Server Enabled
> : Start IP Address : 192.168.1.11
> : IP Pool Counts : 50
> : Gateway IP Address : 192.168.1.1
> : DHCP Server IP Address for Relay Agent : blank
> : DNS Server IP Address blank
>
> If you set this line above to the bt.net primary DNS address, it may
provide
> it for the computers that are set to obtain DNS via DHCP or automatically.
> One of these should do it:
> ns0.bt.net internet address = 194.72.6.51
> ns2.bt.net internet address = 217.35.209.188
>
> You only need the address.
>
> : Primary IP Address : blank
> : Secondary IP Address: blank
> :
> : Dynamic DNS Setup is not enabled
>
> If you enable this, it may obtain the DNS automatically from the ISP and
> with the DHCP being provided to the workstations, if they are set to get
> their DNS settings automatically, then they should get it from the router.
>
> : RIP protocol control - disabled
> : NAT setup:
> : Private IP Address Range defined by RFC-1918:
> :
> : 10.0.0.0 --- 10.255.255.255 (10/8 prefix)
> : 172.16.0.0 --- 172.31.255.255 (172.16/12 prefix)
> : 192.168.0.0 --- 192.168.255.255 (192.168/16 prefix)
> :
> : DMZ Host Setup
> : everything blank
> : Port Redirection Table is empty except 0 for all public ports
>
> If the others are working, I'm sure port 53 is allowed to pass. Nslookup
> can confirm it. I'm betting that the ones that work have their DNS
settings
> set manually (static). I believe the one that is not working has
everything
> set to get it from the DHCP server but the router has DNS turned off so it
> cannot provide it.
>
> HTH...
>
> --
> Roland Hall
> /* This information is distributed in the hope that it will be useful, but
> without any warranty; without even the implied warranty of merchantability
> or fitness for a particular purpose. */
> Online Support for IT Professionals -
> http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
>
>



Relevant Pages

  • Re: Cannot connect to RWW from home PC
    ... eth0 172.26.0.1/16 Extra none ... That would be the address you need a DNS record for. ... One question - if I reset the Thomson Router will that clear all the ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... No 10.0.0.138 is the address used to log onto Thomson's router to make the ... On the DNS question I can add an MX record in the DNS area of GoDaddy's ... eth0 172.26.0.1/16 Extra none ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... NIC, you need to specify an external DNS server for DNS, instead of the ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... You say "And in the router you need to forward to your external nic IP" ... You say "You need the domain hoster to setup a DNS record that will be ... We have rerun CEICW sort of hoping it would sort out the router but no ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Even a single-NIC configuration should have ONLY the LAN IP of the server as ... Then you can run the CEICW or use the DNS console to enter ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)