Re: simple office configuration questions for expert
- From: Jeff Liebermann <jeffl@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 09 Nov 2007 19:52:46 -0800
On Thu, 8 Nov 2007 20:28:29 +0700, "-keevill-" <keevillus@xxxxxxxxx>
wrote:
In my network I have about 50 client machines all running WinXP with USB
wireless adaptors.
Oh-oh.
For wireless connection in the office there are 5 Wireless router/ADSL modem
/ Switches all connected via RJ45 cable to each other ( daisy chain ) into
the network in order to increase the coverage of the wireless network.
Ummm... I suspect you really have *ONE* wireless router/ADSL
modem/switch, and *FOUR* wireless access points, or wireless routers
with the router section disabled and the DHCP servers turned off. If
these boxes are all identical and have ADSL modem sections, then you
have a "double NAT" configuration, which methinks is a rather bad
idea.
Could I trouble you for the manufacturer, model number, and a better
description of how you have this pretzel wired?
I have configured 3 of them with DHCP each on different ranges.
192.168.0.30-50 for one - 192.168.0.100-150 for another and so on.
That will work but is largely un-necessary unless you a filtering
broadcasts through each access point. That will be the case if you
have the router sections enabled and are doing double NAT. Can you
give a better description of the wiring and IP layout?
The others are not configured with DHCP .
I'll assume that means you don't have the DHCP server enabled on the
LAN side.
Some machines are on fixed IP and
others are configured to obtain IP via the DHCP routers.
Internet connection is via ADSL .
I have learned that some machines which are configured to obtain IP and DNS
settings auto, work with good connection to Internet and others do not.
It suits me to have some areas on DHCP for guests who need to connect and
it's easy to just let them take the default of obtain IP & DNS
automatically.
Without a VLAN, they're going to get the same IP's and DNS servers as
everyone else.
Sometimes although a PC connects to an access point on DHCP with a range of
192.168.0.30-50 for example, it obtains an IP address of 192.168.0.125 which
is clearly not right. and when this happens the Internet connection is lost
since the DG is not discovered.
Yep. That's why you really should only have one DHCP server per
network. The mechanism is fairly simple. A random client gets an IP
from DHCP server #1. The client then moves out of range of this
wireless router and DHCP server and blunders into the area serviced by
a different wireless router and DHCP server. Things continue to work
normally until the DHCP lease expires and the client tries to renew
it. Since it can't directly contact the original DHCP server, it
fails and grabs a new lease from the 2nd DHCP server. It would all
work fine except that Windoze XP and I suspect (not sure) Vista have
the irritating habit of sometimes not also updating the default
gateway IP. I've seen it a few times but have never bothered to
troubleshoot the problem. A simple:
ipconfig /release
followed by a:
ipconfig /renew
will solve the problem, at least until the next time the DHCP lease
expires.
Incidentally, if you have Vista machines, there are a few assorted
DHCP bugs that have to be dealt with manually until SP1 arrives.
<http://groups.google.com/group/alt.internet.wireless/msg/52ee76bb33f98ac4>
Many times I have to restart/reboot the routers in order to regain
connection.
Is there something inherently wrong with my configuration which causes this?
Yes, but from your description, I can't tell what you have for
hardware and topology.
What you should be doing is something like this:
ADSL
Modem ===== Router ==== wireless 1
==== wireless 2
==== wireless 3
==== wireless 4
==== wireless 5
The modem, router, and wireless 1 are all in the same box.
The 4 "wireless" boxes are plugged into the LAN ports.
The router should be 192.168.1.1 and have the DHCP server enabled.
It should be the only DHCP server in the system.
The various "wireless" devices are being run as access points. That
means that if it happens to be a wireless router, then nothing is
plugged into the WAN(internet) port and the DHCP servers are all
disabled. The management interface should be 192.168.1.2 thru
192.168.1.5 for each access point. The wiring can be daisy chained
for convenience, but that makes troubleshooting (watching the flashing
lights) and monitoring (sniffing) somewhat awkward.
If you're trying to do something special for "guest" machines and
visitors, I usually suggest that you get a completely separate router
and wireless device for their use, that never hits the inside LAN at
any point. I find this method easier and cheaper than dual SSID's.
However, if your unspecified equipment can handle dual SSID's, that's
the way to deal with guest devices.
Diversion: Reading between your lines, you have 50 desktops connected
with USB wireless devices. That's a rather large number of wireless
devices to be running in a small area. I suspect that some of these
desktops could instead be connected via CAT5, which will take the load
off the wireless and possibly reduce the number of access points.
--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831-336-2558 jeffl@xxxxxxxxxxxxxxxxxxxxxx
# http://802.11junk.com jeffl@xxxxxxxxxx
# http://www.LearnByDestroying.com AE6KS
.
- Follow-Ups:
- Re: simple office configuration questions for expert
- From: -keevill-
- Re: simple office configuration questions for expert
- References:
- simple office configuration questions for expert
- From: -keevill-
- simple office configuration questions for expert
- Prev by Date: Re: Better at a Distance
- Next by Date: Re: Better at a Distance
- Previous by thread: simple office configuration questions for expert
- Next by thread: Re: simple office configuration questions for expert
- Index(es):
Relevant Pages
|
