Re: Strange PC networking problem
- From: Steve de Mena <steven@xxxxxxxxxxxxxxx>
- Date: Sat, 24 Mar 2007 15:04:41 -0700
David Fritzinger wrote:
In article <BLudnYgOcZtIHZjbnZ2dnUVZ_ojinZ2d@xxxxxxxxxxx>,
Maverick <Sun@xxxxxxxxx> wrote:
Steve de Mena wrote:
Dave Fritzinger wrote:From what I understand so far, is that all the home router boxes I've seen always have the ip address of 192.168.1.1 and the obvious subnet mask set to always 255.255.255.0 with the last digit reserved for the local lan.
On Mar 23, 4:34 pm, Steve de Mena <ste...@xxxxxxxxxxxxxxx> wrote:
Dave Fritzinger wrote:
On Mar 20, 10:57 am, "PC Guy" <p...@xxxxxxxxxxx> wrote:No, absolutely not. It has to get it from DHCP,
"Tim Murray" <no-s...@xxxxxxxxxxxx> wrote in messageOK, I finally got a chance to look at my wife's computer this
news:0001HW.C224C9C50001C5DDF0488648@xxxxxxxxxxxxxxxxxxxxxxxxxxx
I think a key item is this:It's no wonder you Mac advocates despise Windows. It's obvious you are
I could use her computer to log in to the router,I would not bet a lung on it, but I think in order to do that, the
and make configuration changes.
computer
must have had an IP issued to it. Thus, we can rule out things like
running
over your max IP limit. But the question is whether you can make config
changes with a self-assigned IP of the form 127.x.x.x.
The result of the ipconfig /all is important.
I see this from time to time but usually on wireless. The times I've seen
it
the fix was to (a) completely delete the connection from the Networks
control
panel and reboot, and if that was not sufficient, then (b) remove the
network
hardware adapters and reboot. The drivers are already there, so Windows
should have no problem reloading them when it boots up again.
completely clueless about it. There is nothing wrong with the cable, port,
PC interface, or IP address. We know this because he said:
"Finally, I could use her computer to log in to the router, and make
configuration changes."
If there were a problem with any of these he would not be able to log into
the router. Thus any suggestions to removenetworkhardware adapters,
drivers, replace the cable are completely useless. Even statically assigning
IP addresses is very unlikely to solve the problem. The fact that he can
connect to the router indicates that he is having issues getting off of the
localnetwork. The likely causes of the problem are incorrect DNS entries,
missing default router, or a bad subnet mask. Also "self-assigned" IP
addresses do not fall within the 127.0.0.0/8network. Thatnetworkis
reserved for loopback addresses. What you are thining of are private IP
addresses (PIPs, otherwise known as RFC-1918 addresses) which fallen within
one of the following networks:
10.0.0.0/8
127.16.0.0/12
192.168.0.0/16
Dave, before performing any of the suggestions please post the output of the
commands I, and a few others, have given you. The two most useful ones are
the nslookup and ipconfig commands.
afternoon (She usually packs it away to take to work before I get
home). The problem was really simple, and something I suspected a
couple of days ago. The router address that the computer was looking
for was wrong (192.168.0.1 instead of 192.168.1.1, which is how the
router was set up). This brings up a rather naive question about
Windows. Can the networking be set up to automatically find the router
address?
or be entered in manually.
Yet, on the nework preference pane on my laptop, there are no entries
in the DNS server box, until I plug my laptop in, either at work or at
home, and it finds the router. Also, if what you say is the case, how
would you conncect to networks when you are traveling, or when you go
to Starbucks (or whatever)?
Starbucks or whomever has DHCP servers!
Your machine puts out a DHCP request at a broadcast address and the DHCP server replies with information which your machine typically accepts. This information includes a IP address, Subnet Mask, Default Gateway, DNS server(s), and can have other stuff too, like default domain search orders, WINS servers, etc.
The fact the DNS server box is blank means that they are DHCP assigned. If there is something there than it was over-written manually. Go to a terminal screen on your Mac and type "nslookup" and when it loads type "server" and you'll see all your DNS servers.
I know that is how it works on my Macs, which makes it easyWhat is the Mac doing magically? On mine it gets
for me to carry my laptop into work and plug it into the network
there. There must be a setting in Windows that allows the same.
the router (default gateway) from DHCP. Just like
my Windows boxes.
So does mine. But, it finds the router automatically, as far as I can
tell. I certainly don't have to manually enter the address of the
router.
Nothing can find a router as there are no "characteristics" for which a device can determine that something IS a router. Your machine has to be specifically TOLD what the default gateway (router) is. If you have to guess it is usually ".1" on the subnet you are on, just out of tradition.
So it looks like Apple and Microsoft are banking on it and just hard coding it in there as a default.
I'm not sure this is the case. With my old D-link router, the default address was 192.168.0.100 (and it gave out ip addresses from 192.168.0.101 to 150). I had an old airport (801.11.b), and the default was something like 10.1.1.1.
No computer assumes anything for a router IP address, nor would they ever hard code any of the common IPs. They send out a broadcast request to DHCP servers and get reply or replies back and thats how they get the router IP and their own IP.
The subnet mask 255.255.255.0 is a "Class C" network of 254 addresses.
Steve
.
- Follow-Ups:
- Re: Strange PC networking problem
- From: Maverick
- Re: Strange PC networking problem
- References:
- Strange PC networking problem
- From: Dave Fritzinger
- Re: Strange PC networking problem
- From: Tim Murray
- Re: Strange PC networking problem
- From: PC Guy
- Re: Strange PC networking problem
- From: Dave Fritzinger
- Re: Strange PC networking problem
- From: Steve de Mena
- Re: Strange PC networking problem
- From: Dave Fritzinger
- Re: Strange PC networking problem
- From: Steve de Mena
- Re: Strange PC networking problem
- From: Maverick
- Re: Strange PC networking problem
- From: David Fritzinger
- Strange PC networking problem
- Prev by Date: Re: apple TV -Just out - already broke
- Next by Date: Re: Strange PC networking problem
- Previous by thread: Re: Strange PC networking problem
- Next by thread: Re: Strange PC networking problem
- Index(es):
Relevant Pages
|