Need help on connecting Wi-Fi to wired LAN

We have a wired Windows 2000 Server with about 25 Windows XP users connected
through a switch. A DSL router also connects to the switch, and the DSL
connection is successfully shared by all users. At the front end is a Cisco
PIX firewall that is also the DHCP server.

Since several users, as well as visiting consultants, have notebooks that
also need access to the network and Internet, we do have places where they
can 'plug in'. But because of the layout of the building and limited network
jacks, this sometimes becomes inconvenient. Using a wireless AP at different
places would really help make the system more flexible.

To try and determine how practical this idea was, I hooked a Netgear MR814
wireless router to the LAN switch as an AP. I left many of the default
setting and activated the DHCP server function and opened the HTTP port. The
IP address ranges were matched up so there's no area of conflict, but
presently the subnets are different. At this point, I didn't know what else
to change.

The results -- My Compaq notebook computer with built-in Wi-Fi sees the AP
and connects to the Internet through the system just fine. However, I can't
see the rest of the network or access the server.

My question is, what do I need to do next to have access to the server and
other network devices? Or is this even possible using this equipment?

Thanks.

Leon

Disable the Netgear's DHCP server and don't use the WAN port. Use one of
the LAN ports to connect to your network.

You don't need the Netgear to act as a router, just an access point.


Bob

"Leon Willard" <(E-Mail Removed)> wrote in message
news:bf7hs9$blp45$(E-Mail Removed)...
> We have a wired Windows 2000 Server with about 25 Windows XP users
connected
> through a switch. A DSL router also connects to the switch, and the DSL
> connection is successfully shared by all users. At the front end is a
Cisco
> PIX firewall that is also the DHCP server.
>
> Since several users, as well as visiting consultants, have notebooks that
> also need access to the network and Internet, we do have places where they
> can 'plug in'. But because of the layout of the building and limited
network
> jacks, this sometimes becomes inconvenient. Using a wireless AP at
different
> places would really help make the system more flexible.
>
> To try and determine how practical this idea was, I hooked a Netgear MR814
> wireless router to the LAN switch as an AP. I left many of the default
> setting and activated the DHCP server function and opened the HTTP port.
The
> IP address ranges were matched up so there's no area of conflict, but
> presently the subnets are different. At this point, I didn't know what
else
> to change.
>
> The results -- My Compaq notebook computer with built-in Wi-Fi sees the AP
> and connects to the Internet through the system just fine. However, I
can't
> see the rest of the network or access the server.
>
> My question is, what do I need to do next to have access to the server and
> other network devices? Or is this even possible using this equipment?
>
> Thanks.
>
> Leon
>
>
>
>

Hey Bob,

Your suggestion seemed almost too simple. Could it really be that
easy? --Well, I'll tell you, it worked like a charm. Another example of
someone (me) jumping to an overly complex solution to a problem. . . I hate
it when that happens . . .!

Thanks.

Leon


"Bob Hall" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Disable the Netgear's DHCP server and don't use the WAN port. Use one of
> the LAN ports to connect to your network.
>
> You don't need the Netgear to act as a router, just an access point.
>
>
> Bob
>
> "Leon Willard" <(E-Mail Removed)> wrote in message
> news:bf7hs9$blp45$(E-Mail Removed)...
> > We have a wired Windows 2000 Server with about 25 Windows XP users
> connected
> > through a switch. A DSL router also connects to the switch, and the DSL
> > connection is successfully shared by all users. At the front end is a
> Cisco
> > PIX firewall that is also the DHCP server.
> >
> > Since several users, as well as visiting consultants, have notebooks
that
> > also need access to the network and Internet, we do have places where
they
> > can 'plug in'. But because of the layout of the building and limited
> network
> > jacks, this sometimes becomes inconvenient. Using a wireless AP at
> different
> > places would really help make the system more flexible.
> >
> > To try and determine how practical this idea was, I hooked a Netgear
MR814
> > wireless router to the LAN switch as an AP. I left many of the default
> > setting and activated the DHCP server function and opened the HTTP port.
> The
> > IP address ranges were matched up so there's no area of conflict, but
> > presently the subnets are different. At this point, I didn't know what
> else
> > to change.
> >
> > The results -- My Compaq notebook computer with built-in Wi-Fi sees the
AP
> > and connects to the Internet through the system just fine. However, I
> can't
> > see the rest of the network or access the server.
> >
> > My question is, what do I need to do next to have access to the server
and
> > other network devices? Or is this even possible using this equipment?
> >
> > Thanks.
> >
> > Leon
> >
> >
> >
> >
>
>
>

Leon,

I'm glad it worked for you, but now I have to warn you that you have
just opened a BIG security hole in your network. An unwanted intruder might
be able to access your nework while sitting outside in a parked car. While
no one would intentionally install open LAN ports outside their company's
security, WiFi can do exactly that unless proper measures are taken.

I recommend you go back into the Netgear box and set up 128-bit WEP and
MAC filtering. That will give you a fair start at keeping unwanted people
out of your network.

When someone new wants to connect, input their wireless MAC address and
give them the WEP key. Also, in a business environment, you should change
the WEP key at least once a week.

Until WPA security is available for all of your gear, you should check
into a VPN solution for security.

Bob

"Leon Willard" <(E-Mail Removed)> wrote in message
news:bfdbt2$db3u8$(E-Mail Removed)...
> Hey Bob,
>
> Your suggestion seemed almost too simple. Could it really be that
> easy? --Well, I'll tell you, it worked like a charm. Another example of
> someone (me) jumping to an overly complex solution to a problem. . . I
hate
> it when that happens . . .!
>
> Thanks.
>
> Leon
>
>
> "Bob Hall" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Disable the Netgear's DHCP server and don't use the WAN port. Use one
of
> > the LAN ports to connect to your network.
> >
> > You don't need the Netgear to act as a router, just an access point.
> >
> >
> > Bob
> >
> > "Leon Willard" <(E-Mail Removed)> wrote in message
> > news:bf7hs9$blp45$(E-Mail Removed)...
> > > We have a wired Windows 2000 Server with about 25 Windows XP users
> > connected
> > > through a switch. A DSL router also connects to the switch, and the
DSL
> > > connection is successfully shared by all users. At the front end is a
> > Cisco
> > > PIX firewall that is also the DHCP server.
> > >
> > > Since several users, as well as visiting consultants, have notebooks
> that
> > > also need access to the network and Internet, we do have places where
> they
> > > can 'plug in'. But because of the layout of the building and limited
> > network
> > > jacks, this sometimes becomes inconvenient. Using a wireless AP at
> > different
> > > places would really help make the system more flexible.
> > >
> > > To try and determine how practical this idea was, I hooked a Netgear
> MR814
> > > wireless router to the LAN switch as an AP. I left many of the default
> > > setting and activated the DHCP server function and opened the HTTP
port.
> > The
> > > IP address ranges were matched up so there's no area of conflict, but
> > > presently the subnets are different. At this point, I didn't know what
> > else
> > > to change.
> > >
> > > The results -- My Compaq notebook computer with built-in Wi-Fi sees
the
> AP
> > > and connects to the Internet through the system just fine. However, I
> > can't
> > > see the rest of the network or access the server.
> > >
> > > My question is, what do I need to do next to have access to the server
> and
> > > other network devices? Or is this even possible using this equipment?
> > >
> > > Thanks.
> > >
> > > Leon
> > >
> > >
> > >
> > >
> >
> >
> >
>
>

Bob,

Thanks for the warning. We are aware of these things, and will take some
security measures once we decide by who and how this new wireless capability
will be used. Also, we are in an old industrial building that's already
giving us 'interference' problems and very limited range. But as we solve
the range problems, then the security problems become more of an issue.

Your warning comes at a good time, and reminds us not to forget the security
issue as we learn to take advantage of this new capability, and especially
as we begin to add more users.

Thanks again.

Leon


"Bob Hall" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Leon,
>
> I'm glad it worked for you, but now I have to warn you that you have
> just opened a BIG security hole in your network. An unwanted intruder
might
> be able to access your nework while sitting outside in a parked car.
While
> no one would intentionally install open LAN ports outside their company's
> security, WiFi can do exactly that unless proper measures are taken.
>
> I recommend you go back into the Netgear box and set up 128-bit WEP
and
> MAC filtering. That will give you a fair start at keeping unwanted people
> out of your network.
>
> When someone new wants to connect, input their wireless MAC address
and
> give them the WEP key. Also, in a business environment, you should change
> the WEP key at least once a week.
>
> Until WPA security is available for all of your gear, you should check
> into a VPN solution for security.
>
> Bob
>
> "Leon Willard" <(E-Mail Removed)> wrote in message
> news:bfdbt2$db3u8$(E-Mail Removed)...
> > Hey Bob,
> >
> > Your suggestion seemed almost too simple. Could it really be that
> > easy? --Well, I'll tell you, it worked like a charm. Another example of
> > someone (me) jumping to an overly complex solution to a problem. . . I
> hate
> > it when that happens . . .!
> >
> > Thanks.
> >
> > Leon
> >
> >
> > "Bob Hall" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > Disable the Netgear's DHCP server and don't use the WAN port. Use one
> of
> > > the LAN ports to connect to your network.
> > >
> > > You don't need the Netgear to act as a router, just an access point.
> > >
> > >
> > > Bob
> > >
> > > "Leon Willard" <(E-Mail Removed)> wrote in message
> > > news:bf7hs9$blp45$(E-Mail Removed)...
> > > > We have a wired Windows 2000 Server with about 25 Windows XP users
> > > connected
> > > > through a switch. A DSL router also connects to the switch, and the
> DSL
> > > > connection is successfully shared by all users. At the front end is
a
> > > Cisco
> > > > PIX firewall that is also the DHCP server.
> > > >
> > > > Since several users, as well as visiting consultants, have notebooks
> > that
> > > > also need access to the network and Internet, we do have places
where
> > they
> > > > can 'plug in'. But because of the layout of the building and limited
> > > network
> > > > jacks, this sometimes becomes inconvenient. Using a wireless AP at
> > > different
> > > > places would really help make the system more flexible.
> > > >
> > > > To try and determine how practical this idea was, I hooked a Netgear
> > MR814
> > > > wireless router to the LAN switch as an AP. I left many of the
default
> > > > setting and activated the DHCP server function and opened the HTTP
> port.
> > > The
> > > > IP address ranges were matched up so there's no area of conflict,
but
> > > > presently the subnets are different. At this point, I didn't know
what
> > > else
> > > > to change.
> > > >
> > > > The results -- My Compaq notebook computer with built-in Wi-Fi sees
> the
> > AP
> > > > and connects to the Internet through the system just fine. However,
I
> > > can't
> > > > see the rest of the network or access the server.
> > > >
> > > > My question is, what do I need to do next to have access to the
server
> > and
> > > > other network devices? Or is this even possible using this
equipment?
> > > >
> > > > Thanks.
> > > >
> > > > Leon
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
>
>

Leon,

Thanks. That makes me feel better. I'd hate to learn that someone used
that WLAN to do serious damage to your company.

This technology is incredibly useful, but must be used with care.


Bob

"Leon Willard" <(E-Mail Removed)> wrote in message
news:bff9g5$e3302$(E-Mail Removed)...
> Bob,
>
> Thanks for the warning. We are aware of these things, and will take some
> security measures once we decide by who and how this new wireless
capability
> will be used. Also, we are in an old industrial building that's already
> giving us 'interference' problems and very limited range. But as we solve
> the range problems, then the security problems become more of an issue.
>
> Your warning comes at a good time, and reminds us not to forget the
security
> issue as we learn to take advantage of this new capability, and especially
> as we begin to add more users.
>
> Thanks again.
>
> Leon
>
>
> "Bob Hall" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Leon,
> >
> > I'm glad it worked for you, but now I have to warn you that you have
> > just opened a BIG security hole in your network. An unwanted intruder
> might
> > be able to access your nework while sitting outside in a parked car.
> While
> > no one would intentionally install open LAN ports outside their
company's
> > security, WiFi can do exactly that unless proper measures are taken.
> >
> > I recommend you go back into the Netgear box and set up 128-bit WEP
> and
> > MAC filtering. That will give you a fair start at keeping unwanted
people
> > out of your network.
> >
> > When someone new wants to connect, input their wireless MAC address
> and
> > give them the WEP key. Also, in a business environment, you should
change
> > the WEP key at least once a week.
> >
> > Until WPA security is available for all of your gear, you should
check
> > into a VPN solution for security.
> >
> > Bob
> >
> > "Leon Willard" <(E-Mail Removed)> wrote in message
> > news:bfdbt2$db3u8$(E-Mail Removed)...
> > > Hey Bob,
> > >
> > > Your suggestion seemed almost too simple. Could it really be that
> > > easy? --Well, I'll tell you, it worked like a charm. Another example
of
> > > someone (me) jumping to an overly complex solution to a problem. . .
I
> > hate
> > > it when that happens . . .!
> > >
> > > Thanks.
> > >
> > > Leon
> > >
> > >
> > > "Bob Hall" <(E-Mail Removed)> wrote in message
> > > news:(E-Mail Removed)...
> > > > Disable the Netgear's DHCP server and don't use the WAN port. Use
one
> > of
> > > > the LAN ports to connect to your network.
> > > >
> > > > You don't need the Netgear to act as a router, just an access point.
> > > >
> > > >
> > > > Bob
> > > >
> > > > "Leon Willard" <(E-Mail Removed)> wrote in message
> > > > news:bf7hs9$blp45$(E-Mail Removed)...
> > > > > We have a wired Windows 2000 Server with about 25 Windows XP users
> > > > connected
> > > > > through a switch. A DSL router also connects to the switch, and
the
> > DSL
> > > > > connection is successfully shared by all users. At the front end
is
> a
> > > > Cisco
> > > > > PIX firewall that is also the DHCP server.
> > > > >
> > > > > Since several users, as well as visiting consultants, have
notebooks
> > > that
> > > > > also need access to the network and Internet, we do have places
> where
> > > they
> > > > > can 'plug in'. But because of the layout of the building and
limited
> > > > network
> > > > > jacks, this sometimes becomes inconvenient. Using a wireless AP at
> > > > different
> > > > > places would really help make the system more flexible.
> > > > >
> > > > > To try and determine how practical this idea was, I hooked a
Netgear
> > > MR814
> > > > > wireless router to the LAN switch as an AP. I left many of the
> default
> > > > > setting and activated the DHCP server function and opened the HTTP
> > port.
> > > > The
> > > > > IP address ranges were matched up so there's no area of conflict,
> but
> > > > > presently the subnets are different. At this point, I didn't know
> what
> > > > else
> > > > > to change.
> > > > >
> > > > > The results -- My Compaq notebook computer with built-in Wi-Fi
sees
> > the
> > > AP
> > > > > and connects to the Internet through the system just fine.
However,
> I
> > > > can't
> > > > > see the rest of the network or access the server.
> > > > >
> > > > > My question is, what do I need to do next to have access to the
> server
> > > and
> > > > > other network devices? Or is this even possible using this
> equipment?
> > > > >
> > > > > Thanks.
> > > > >
> > > > > Leon
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>