From: jinxy on
On Jan 20, 5:30 pm, jinxy <willand...(a)rogers.com> wrote:
> On Jan 19, 6:29 pm, Mike Easter <Mi...(a)ster.invalid> wrote:
>
>
>
>
>
> > jinxy wrote:
> > > I don't know what to tell you. The owners of the LT run on the Bell
> > > network and it won't connect for them and they live in Bancroft Ont.
> > > We have 4 LT's running off of our wireless router, plus 3 of the 4
> > > ports are cabled and no one ever complains about connectivity
> > > problems. How do I go about fixing it without messing up all of the
> > > other units? Down the rabbit hole we go.
>
> > Start> Run> cmd> ipconfig /all
>
> > What happens if you put this address into a browser addressline on the
> > LT?  http://209.68.27.16/
>
> > That's the IP chicken which will answer by its IP address.
>
> > What is the brand and modelno of your router?  I'll figure out how you
> > can look at its status to see if anything is funny in there.
>
> > --
> > Mike Easter
> >What does ipconfig on one of the other computers on your network say?
>
> The IP on a second pc says- 192.168.1.103 with the same DNS server #
> 64.71.255.198
>
> -When I entered the Ip Chicken address into the browser I get the same
> reply- IE cannot display  the webpage
>
> Router- Linksys m/n WRT54G v.3
> Thanks.-J- Hide quoted text -
>
> - Show quoted text -

I have gone through the steps to change the LT to use Goolge as the
DNS server. When all was changed the same results are produced. IE
cannot display the webpage. I currently doing nightshift so please
excuse any delays in my replies. Thanks for your ongoing interest and
efforts in solving this problem with me.
-J
From: Mike Easter on
jinxy wrote:
> Mike Easter

>> Start> Run> cmd> ipconfig /all

You forgot to tell me what this said when you did it on the LT, perhaps
(actually probably or surely) because I didn't properly configure it for
Vista.

(I'm not very familiar with Vista yet)

Run is an accessory in vista. To get to run and ipconfig /all in Vista, use

Start/ All programs/ Accessories> Run/ cmd/ ipconfig /all

> The IP on a second pc says- 192.168.1.103 with the same DNS server #
> 64.71.255.198

Aha! That is *not* the same DNS IP. You said 64.71.225.198 earlier,
which befuddled me.

That IP above makes perfectly good sense for a Rogers DNS, because its
rDNS is dns.rnc.net.cable.rogers.com

> Router- Linksys m/n WRT54G v.3

OK. That router works the same as mine to look into 192.168.1.1.

When I am mystified, sometimes I just try to look at the router's html
with the funky computer; in this case the LT.

So, to do so, you would put http://192.168.1.1 into the LT's browser's
addressline.

For right now, we won't even put in the password, just see if you can
get 'to' the router's login with the LT.

--
Mike Easter
From: Mike Easter on
jinxy wrote:

> I have gone through the steps to change the LT to use Goolge as the
> DNS server. When all was changed the same results are produced. IE
> cannot display the webpage.

Yes it turns out that the DNS is not the problem; the assigned DNS is
actually a rogers when the correct IP is examined, and the chicken IP
place didn't work either.

You can leave the google IPs in there, it is harmless as long as there
are no mistakes made in the IP address :-)

We have to find the problem somewhere other than DNS. See the other post.


--
Mike Easter
From: jinxy on
On Jan 20, 10:00 pm, Mike Easter <Mi...(a)ster.invalid> wrote:
> jinxy wrote:
> > I have gone through the steps to change the LT to use Goolge as the
> > DNS server. When all was changed the same results are produced. IE
> > cannot display the webpage.
>
> Yes it turns out that the DNS is not the problem;  the assigned DNS is
> actually a rogers when the correct IP is examined, and the chicken IP
> place didn't work either.
>
> You can leave the google IPs in there, it is harmless as long as there
> are no mistakes made in the IP address :-)
>
> We have to find the problem somewhere other than DNS.  See the other post.
>
> --not
> Mike Easter

Sorry about the DNS error :-( Glad you caught it. I tried to put the
192.168.1.1 into the LT's browser bar and got the same results. cannot
display the webpage.
This is what the ipconfig/all shows on the LT.
> DHCP is Enabled
> Ipv4 IP Adress 192.168.1.106 (preferred)
> IPv4 DHCP server 192.168.1.1
> IPv4 DNS servers 8.8.8.8
8.8.4.4
What should the setting read under Windows IP Configuration? I have
Host name: PC, Primary Dns suffix: which is blank, then Node
type:broadcast, next is IP Routing Enabled :no.WINS Proxy Enabled: no,
and finally DNS Suffix Search List: Rogers.com
Just curious, is there an antenna somewhere in laptops, similar to the
way there are built into automobile windsheilds? If so could this be
the culprit?
-J

From: Mike Easter on
jinxy wrote:

> Sorry about the DNS error :-( Glad you caught it. I tried to put the
> 192.168.1.1 into the LT's browser bar and got the same results. cannot
> display the webpage.

Hmmph.

> This is what the ipconfig/all shows on the LT.
>> DHCP is Enabled
>> Ipv4 IP Adress 192.168.1.106 (preferred)
>> IPv4 DHCP server 192.168.1.1
>> IPv4 DNS servers 8.8.8.8
> 8.8.4.4
> What should the setting read under Windows IP Configuration?

All that stuff is normal.

> I have
> Host name: PC, Primary Dns suffix: which is blank, then Node
> type:broadcast, next is IP Routing Enabled :no.WINS Proxy Enabled: no,
> and finally DNS Suffix Search List: Rogers.com

All that stuff is OK.

> Just curious, is there an antenna somewhere in laptops, similar to the
> way there are built into automobile windsheilds? If so could this be
> the culprit?

If there were an antenna problem, you would have a very weak signal.
You can see your signal quality in that network place I described
earlier, Start/ CP/ Network and sharing center - there's a graphic with
Connections - signal strength.

I'm befuddled over how you are getting an IP address from the router,
but you can't see it.

Is your browser configured to use the network? You said you were using
IE, which has vulnerabilities you know, and its connections is in Tools/
Internet Options/ Connections tab

Can you ping the router? -- even if a router is configured to not answer
pings from the WAN it should answer pings from its LAN

Use the same run cmd to ping:

Vista/ Start/ all programs/ accessories/ run/ cmd/ ping 192.168.1.1

You can also try to ping one of the other machines such as whatever was
the IP on another machine on the network, such as .103, ie 192.168.1.103
or whatever it was.

The IP chicken place will also answer pings, try that one 209.68.27.16

Not all webservers will answer a ping.

I tried to ping that rogers nameserver, but it wouldn't answer me, but
I'm not on its network.

Also the google nameserver will answer pings 8.8.8.8

It is going to be a little weird if you can't ping your router.

What is the firewall situation on this vista?

--
Mike Easter