"Nick Le Lievre" <(E-Mail Removed)> wrote in message
news:booego$1fts9f$(E-Mail Removed)...
> "Lars M. Hansen" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > On Mon, 10 Nov 2003 15:01:54 -0000, Nick Le Lievre spoketh
> >
> > >"Lars M. Hansen" <(E-Mail Removed)> wrote in message
> > >news:(E-Mail Removed).. .
> > >>
> > >> The WAP _is_ a wireless hub. You don't have to plug it into a wired
> > >> network (other than for (probably) configuration purposes).
> > >>
> > >> Lars M. Hansen
> > >> www.hansenonline.net
> > >
> > >I really hope your right as I would then be able to position the WAP
> within
> > >range of the PC which already has the wireless card giving me loads
more
> > >range in the surrounding area of the WAP. The manual suggests it need
to
> be
> > >physically connected to a wired network
> > >http://nicklelievre.redirectme.net/wap.jpg
> > >
> > >I hope this is only necessary for config purposes.
> > >
> >
> > As a test, I just started a ping from one wireless laptop to another,
> > then disconnected the cable from my WAP. Traffic was still going between
> > the laptops and the WAP.
> >
> > Also, your manual uses the word "can" not "must" when it describes how
> > to connect the WAP to the network. I guess they often assume that the
> > WAP is to add wireless capabilities to an existing (wired) network.
> >
> > Disclaimer: It does work with my Linksys WAP. It should work with
> > yours...
> >
>
> Thanks for the information. I wonder how does it work. Notebook has IP
> 192.168.2.2 WAP has 192.168.2.3 - the PC 192.168.2.1 for the wireless
> adapter (also running ICS etc)
>
> Notebook has dns/gateway set to 192.168.2.1 when in range of WAP it will
be
> able to find 192.168.2.1 thru the WAP 192.168.2.3 seemlessly.
>
> I guess this is a feature of infrastructure mode.
>
Recieved Adaptec 8060 WAP this lunchtime - connected the Access Point to PC
with both wired (192.168.0.1) & wireless (192.168.2.1) interfaces and
installed the Access Point utility - it couldn`t find the AP no great
surprise as I knew that it would need to be physically connected to network
for configuration.
So I connected it directly into the Wired NIC via the CAT5 patch cable
supplied then ran the Access Point Utility again- still no connection and
the Wired LED on the AP itself wasnt lit I was puzzled.
After spending a few minutes getting out my old 10mbit hub connecting both
devices to that and still not getting the Wired LED lit I pulled the power
plug on the AP and after restoring power magically the Wired LED was now
lit! Searching for the device with the Wireless AP Utility found it with a
default IP of 192.168.0.50 then I wasted a few more minutes trying instantly
set the IP to the wireless subnet 192.168.2.3 and finding that the utility
was unable to find it on each subsequent attempt (remember it has to be
connected physically to a wired subnet for configuration).
When I set the IP to 192.168.0.3 temporarily for configuration purposes I
was able to access the browser based configuration page to set SSID channel
etc and thats when I set the IP to 192.168.2.3 and the Gateway to
192.168.2.1 - I applied the options and now of course it was no longer
accesible via the utility as it was on the wireless subnet.
So tried to ping it from 192.168.2.1/192.168.0.2 the PC with both
wired/wireless subnets and no reply then I said to myself "I haven`t changed
the wireless adapters to infrastructure mode" after doing this on
192.168.2.1 and 192.168.2.2 could then ping 192.168.2.3. I then moved the
WAP to its intended central position where it is now happily working on its
own just plugged into the power source and I can go all over signal in the
room to the left of the WAP is 86% and in the room where 192.168.2.1 is
located 66% this is so much better then before with the AD-HOC Setup I had.