Netgear WAB102 not visible on network....

I recently purchased a Netgear WAB102 Access Point to use with my
existing hardwired Ethernet home network. After having some
interesting results plugging the AP into a couple of the hubs within
my system (with and without x-over cables), I was eventually able to
get connection lights and activity on both the AP and the correct port
on my Linksys BEFSR41 Router (without x-overs), indicating to me that
the AP was at the very least talking to the existing network.

My problem is that I am unable to browse to the AP's configuration
screen (via unit name or IP) or even ping the unit itself. I have to
assume that it has not been accepted into the network with the default
settings is has (IP:192.168.0.226/255.255.255.0).

My current network consists of the following components in order of
distance from Cable Modem:
Linksys BEFSR41 Router (IP:192.168.1.1/255.255.255.0)
Alantec PowerHub4000 10MB/S Ethernet
Window NT4 File Server (IP:192.168.1.100/255.255.255.0)
3Com 8port Hub
Windows 2K WRKSTN (IP:192.168.1.X/255.255.255.0)
Windows NT WRKSTN (IP:192.168.1.X/255.255.255.0)
Intel Print Server (IP:192.168.1.X/255.255.255.0)
Windows XP WRKSTN (IP:192.168.1.X/255.255.255.0)
Windows 2K WRKSTN (IP:192.168.1.X/255.255.255.0)

I've had similar problems with older model print servers, in which I
had to take the whole network down and then make sure that my NT
Server was the first PC to join, or else I could not detect the Print
Server. So, I tried that with no success.

Everything I've read about this unit thus far has said how easy it is
to get going, so I think I'm doing something fundamentally wrong. Any
suggestions would be greatly appreciated.

Thanks

(E-Mail Removed) (James) wrote in message news:<(E-Mail Removed). com>...
> I recently purchased a Netgear WAB102 Access Point to use with my
> existing hardwired Ethernet home network. After having some
> interesting results plugging the AP into a couple of the hubs within
> my system (with and without x-over cables), I was eventually able to
> get connection lights and activity on both the AP and the correct port
> on my Linksys BEFSR41 Router (without x-overs), indicating to me that
> the AP was at the very least talking to the existing network.
>
> My problem is that I am unable to browse to the AP's configuration
> screen (via unit name or IP) or even ping the unit itself. I have to
> assume that it has not been accepted into the network with the default
> settings is has (IP:192.168.0.226/255.255.255.0).
>
> My current network consists of the following components in order of
> distance from Cable Modem:
> Linksys BEFSR41 Router (IP:192.168.1.1/255.255.255.0)
> Alantec PowerHub4000 10MB/S Ethernet
> Window NT4 File Server (IP:192.168.1.100/255.255.255.0)
> 3Com 8port Hub
> Windows 2K WRKSTN (IP:192.168.1.X/255.255.255.0)
> Windows NT WRKSTN (IP:192.168.1.X/255.255.255.0)
> Intel Print Server (IP:192.168.1.X/255.255.255.0)
> Windows XP WRKSTN (IP:192.168.1.X/255.255.255.0)
> Windows 2K WRKSTN (IP:192.168.1.X/255.255.255.0)
>
> I've had similar problems with older model print servers, in which I
> had to take the whole network down and then make sure that my NT
> Server was the first PC to join, or else I could not detect the Print
> Server. So, I tried that with no success.
>
> Everything I've read about this unit thus far has said how easy it is
> to get going, so I think I'm doing something fundamentally wrong. Any
> suggestions would be greatly appreciated.
>
> Thanks

FYI - Problem solved...
Disconnected one of the PCs from the Network, changed the IP to match
the range of the AP (192.168.1.x), booted PC first, then attached
already powered up AP to PC with x-over. I was able to ping and view
setup for the unit. Changed the AP to my network ip range
(192.168.1.226), a few more testing steps and then plugged the AP into
the network, and voila.