linksys WAP54G connection problem

Hello
This is my setup:
ADSL modem connected to a 4-port switch, then the linksys WAP54G (with
newest firmware) connects to that, and also 2 other computers. The WAP54G
serves 3 laptops around the house.

The laptops connect to the access point with no problems, but they don't
have a connection to the internet. So I tried to connect to the access point
via the web interface (with the standard 192.168.1.245 address that is set
for it) from one of the wired computers, and I couldn't. It times out. So I
loaded the Linksys Setup Wizard, and when it searches the network for a
linksys machine, it doesn't find it. So I'm wondering whether it's because
the modem isn't assigning an IP address to the access point or whether it's
some hardware problem with the ethernet connection.
By the way, the switch shows the link light as on, when the access point is
connected, so the connection is there, just no communication. Oh, and when I
send a ping to 192.168.1.245 the "Link/Act" light on the access point blinks
twice, and then the ping times out after about 2 seconds, then it blinks
twice again, and the ping times out, and it could go on forever like that.
This makes me wonder then whether something is blocking the communication.

thanks for the help!

Taking a moment's reflection, d.p. mused:
|
| Hello
| This is my setup:
| ADSL modem connected to a 4-port switch, then the linksys WAP54G (with
| newest firmware) connects to that, and also 2 other computers. The WAP54G
| serves 3 laptops around the house.

What are you using for DHCP? If using static IPs, what are you using
for NAT ... assuming you are sharing the xDSL connection among all of the
computers? Regarding the WAP54G specifically, it does not perform any of
those functions above. Also, in order to connect to its web configuration
page, you'll need to be in the same IP range and subnet. It is generally
recommended to do all configuration of wireless components with a wired
connection (i.e.. computer connected to router, WAP54G connected to same
router).

the ADSL modem is the DHCP server. It is connected to the 5th "in" port on
the switch. All the other components are connected via that switch as well
using the normal ports These components are the linksys access point and two
wired computers. The laptops use wireless, and also get their IP's from the
modem. The access point is just a "pass-through" in a sense. NAT is used and
the IP range that's used is the standard 192.168.1.x.
I connect to the wireless access point using a wired computer, via the
switch.
Everything has been working great in the past. It just recently started
acting like this.



"mhicaoidh" <®êmõvé_mhic_aoidh@hotÑîXmailSPäM.com> wrote in message
news:H4MRc.274322$Oq2.58050@attbi_s52...
> Taking a moment's reflection, d.p. mused:
> |
> | Hello
> | This is my setup:
> | ADSL modem connected to a 4-port switch, then the linksys WAP54G (with
> | newest firmware) connects to that, and also 2 other computers. The
WAP54G
> | serves 3 laptops around the house.
>
> What are you using for DHCP? If using static IPs, what are you using
> for NAT ... assuming you are sharing the xDSL connection among all of the
> computers? Regarding the WAP54G specifically, it does not perform any of
> those functions above. Also, in order to connect to its web configuration
> page, you'll need to be in the same IP range and subnet. It is generally
> recommended to do all configuration of wireless components with a wired
> connection (i.e.. computer connected to router, WAP54G connected to same
> router).
>
>

"d.p." <(E-Mail Removed)> wrote in message
news:411791d1$0$7122$(E-Mail Removed)...
> the ADSL modem is the DHCP server. It is connected to the 5th "in" port on
> the switch. All the other components are connected via that switch as well
> using the normal ports These components are the linksys access point and
two
> wired computers. The laptops use wireless, and also get their IP's from
the
> modem. The access point is just a "pass-through" in a sense. NAT is used
and
> the IP range that's used is the standard 192.168.1.x.
> I connect to the wireless access point using a wired computer, via the
> switch.
> Everything has been working great in the past. It just recently started
> acting like this.
>
>
>
> "mhicaoidh" <®êmõvé_mhic_aoidh@hotÑîXmailSPäM.com> wrote in message
> news:H4MRc.274322$Oq2.58050@attbi_s52...
> > Taking a moment's reflection, d.p. mused:
> > |
> > | Hello
> > | This is my setup:
> > | ADSL modem connected to a 4-port switch, then the linksys WAP54G (with
> > | newest firmware) connects to that, and also 2 other computers. The
> WAP54G
> > | serves 3 laptops around the house.
> >
> > What are you using for DHCP? If using static IPs, what are you
using
> > for NAT ... assuming you are sharing the xDSL connection among all of
the
> > computers? Regarding the WAP54G specifically, it does not perform any
of
> > those functions above. Also, in order to connect to its web
configuration
> > page, you'll need to be in the same IP range and subnet. It is
generally
> > recommended to do all configuration of wireless components with a wired
> > connection (i.e.. computer connected to router, WAP54G connected to same
> > router).

Is there really no router in this picture, or is what you called a 4-port
switch actually a router? How about a make and model?

What you are trying to do is to connect your home network with the cable
provider's network. The device that connects two or more networks is a
router. I'm having trouble understanding how this ever worked if you don't
have a router.

Ron Bandes, CCNP, CTT+, etc.

"Ron Bandes" <RunderscoreBandes @yah00.com> wrote in message
news:jGMRc.47804$(E-Mail Removed). net...
> "d.p." <(E-Mail Removed)> wrote in message
> news:411791d1$0$7122$(E-Mail Removed)...
> > the ADSL modem is the DHCP server. It is connected to the 5th "in" port
on
> > the switch. All the other components are connected via that switch as
well
> > using the normal ports These components are the linksys access point and
> two
> > wired computers. The laptops use wireless, and also get their IP's from
> the
> > modem. The access point is just a "pass-through" in a sense. NAT is used
> and
> > the IP range that's used is the standard 192.168.1.x.
> > I connect to the wireless access point using a wired computer, via the
> > switch.
> > Everything has been working great in the past. It just recently started
> > acting like this.
> >
> >
> >
> > "mhicaoidh" <®êmõvé_mhic_aoidh@hotÑîXmailSPäM.com> wrote in message
> > news:H4MRc.274322$Oq2.58050@attbi_s52...
> > > Taking a moment's reflection, d.p. mused:
> > > |
> > > | Hello
> > > | This is my setup:
> > > | ADSL modem connected to a 4-port switch, then the linksys WAP54G
(with
> > > | newest firmware) connects to that, and also 2 other computers. The
> > WAP54G
> > > | serves 3 laptops around the house.
> > >
> > > What are you using for DHCP? If using static IPs, what are you
> using
> > > for NAT ... assuming you are sharing the xDSL connection among all of
> the
> > > computers? Regarding the WAP54G specifically, it does not perform any
> of
> > > those functions above. Also, in order to connect to its web
> configuration
> > > page, you'll need to be in the same IP range and subnet. It is
> generally
> > > recommended to do all configuration of wireless components with a
wired
> > > connection (i.e.. computer connected to router, WAP54G connected to
same
> > > router).
>
> Is there really no router in this picture, or is what you called a 4-port
> switch actually a router? How about a make and model?
>
> What you are trying to do is to connect your home network with the cable
> provider's network. The device that connects two or more networks is a
> router. I'm having trouble understanding how this ever worked if you
don't
> have a router.
>
> Ron Bandes, CCNP, CTT+, etc.
>
>
The WAP54G can act as a router.
AG

"AG" <(E-Mail Removed)> wrote in message
news:4117a0b3$0$44243$(E-Mail Removed)...
> The WAP54G can act as a router.
> AG

Nothing that I see in the product documentation leads me to believe that
this is true.

Ron Bandes, CCNP, CTT+, etc.

The modem/router is the SMC ADSL Barricade Router (SMC7401BRA), which get's
an IP address assigned to it. It in turn acts as the DHCP server, providing
all the NAT config, etc. There's a 4-port switch (5 ports, but the 5th
connects to the router), which is the 3com OfficeConnect Switch 5. Two wired
computers connect to it, and one wireless access point (the Linksys WAP54G).
I really think the problem lies with the Linksys AP, because the wired
computers are fine. The wireless devices find the AP, but that's where it
stops. They can't get to the router to get an IP address, and then get
internet access.
The AP itself doesn't use DHCP, but it has a fixed IP, that it gets by
default - 192.168.1.245 (it can be changed, but I haven't done that).

But the most puzzling thing is that it acts as if the connection exists (the
Link./Act light is on on the AP, and the link light on the switch is on),
and when I ping any local address (including its own .245) the Link/Act
light on the AP blinks, but the ping times out. Is it possible that it
somehow got its IP address changed to one that can't be accessed? If that's
the reason, then is there a program that scans the whole local network and
tells me the IP addresses of all the devices?

On the other hand, I doubt that scanning the network for all devices would
help, since even the Linksys Connection Wizard couldn't find it, and it
doesn't use the web interface, but a standalone program.

I also tried resetting it, but I'm not sure if it resets to factory defaults
or just restarts it.

I hope everything is clear now.

thanks for the help!



"Ron Bandes" <RunderscoreBandes @yah00.com> wrote in message
news:%TNRc.48019$(E-Mail Removed). net...
> "AG" <(E-Mail Removed)> wrote in message
> news:4117a0b3$0$44243$(E-Mail Removed)...
> > The WAP54G can act as a router.
> > AG
>
> Nothing that I see in the product documentation leads me to believe that
> this is true.
>
> Ron Bandes, CCNP, CTT+, etc.
>
>

Taking a moment's reflection, AG mused:
|
| The WAP54G can act as a router.

The WAP54G can only act as an Access Point, AP Client, Wireless
Repeater, or Wireless Bridge. It cannot act as a router.

Taking a moment's reflection, d.p. mused:
|
| The AP itself doesn't use DHCP, but it has a fixed IP, that it gets by
| default - 192.168.1.245 (it can be changed, but I haven't done that).

You either need to have the AP have a fixed IP within the IP range and
subnet of the modem/router, or you need to have the router assign same to
AP. If it is in a different IP range (i.e. your router is assigning
192.168.100.x, and the AP is 192.168.1.245) then this will disrupt
communication.

Additionally, do you have WEP/WPA enabled? Are you broadcasting your
SSID? Are you filtering MAC Addresses? Generally, it is best to start with
encryption off, SSID on (no need to turn it off once you enable encryption
anyway), and no MAC filtering. Once you confirm connectivity, then start
securing things.

Hi,
I agree with the IP story of the previous poster.
I didn't manage to ping the WAP54G with the default IP address
192.168.1.245.
Changed the address to 192.168.0.101 => everything o.k.

By the way, a firewall can cause problems as well. Make your to trust the IP
address of the AP.
Normally the address range 192.168.0.0 - 0.255 is trusted, the address
192.168.1.x is outside this range (my experience with Norton Internet
Security).
Change the firewall settings or change the IP address. I went for a change
of the default IP address.

/rob

"mhicaoidh" <®êmõvé_mhic_aoidh@hotÑîXmailSPäM.com> wrote in message
news:fwRRc.275491$Oq2.127024@attbi_s52...
> Taking a moment's reflection, d.p. mused:
> |
> | The AP itself doesn't use DHCP, but it has a fixed IP, that it gets by
> | default - 192.168.1.245 (it can be changed, but I haven't done that).
>
> You either need to have the AP have a fixed IP within the IP range and
> subnet of the modem/router, or you need to have the router assign same to
> AP. If it is in a different IP range (i.e. your router is assigning
> 192.168.100.x, and the AP is 192.168.1.245) then this will disrupt
> communication.
>
> Additionally, do you have WEP/WPA enabled? Are you broadcasting your
> SSID? Are you filtering MAC Addresses? Generally, it is best to start
with
> encryption off, SSID on (no need to turn it off once you enable encryption
> anyway), and no MAC filtering. Once you confirm connectivity, then start
> securing things.
>
>