| From: |
Lewis G Rosenthal <os2-wireless_users@2rosenthals.com> |
Full Headers
Undecoded message |
| Sender: |
os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com> |
| Subject: |
[OS2Wireless] [Fwd: [Fwd: Re: eCS 1.2/DSL]] |
| Date: |
Fri, 29 Oct 2004 00:37:40 -0400 |
| To: |
os2-wireless_users@2rosenthals.com |
|
|---|
See below, Mark:
On 10/28/2004 12:07 pm, Marcus H. Russell, P.E., L.S. thus wrote :
Lewis G Rosenthal wrote:
Hi, Mark. It surely looks like DHCP is enabled. Please do the following & report your results:
From a command line, type PING 192.168.1.1 and tell us whether you get a
reply (press Ctrl-C to stop the ping). Next, open Mozilla, and enter 192.168.1.1 and see if you can log in (the Linksys default is no username & a password of "admin"). If this works (as I suspect it will), make note of the internet connection type as configured on the main page, & post the setting here. PING 192.168.1.1 yields nothing.
Then you probably have no valid IP address or your interface is configured statically with a 192.168.1.0 subnet address but not able to communicate with the LinkSys box. You're not going anywhere off the network until you can get a response form the LinkSys box, period.
However, PING 127.0.0.1 yields 9 sent, 9 received, 0% loss, rnd-trip 0/0/0
Loopback. This just tells us that the IP stack on the mahcine is working and that the loopback interface (a virtual one) is working (as Stan said).
PING 255.255.255.255 yields 7 trans, 14 received, 0% loss; rnd-trip 0/1/10
Broadcast address. All this means is that something, somewhere, anywhere - in this case your own machine - is listening and responding. Not much help in this situation.
entering 255.255.255.255.255 in browser yields "done." However, browser will not connect to anything.
That's because a broadcast address is a shout out to everyone. There is no such host (and only a "host" - a single machine running a web server - can respond to a browser request). The problem is that you're not connected to your router.
Also, please give us detailed info on your setup, including:
Type of DSL connection you have, and the model of your DSL bridge.
Sent this before. DSL is Verizon supplied modem
No, that's not a detail. What brand is it, Westell? Model? Is it a Wirespeed? Verizon should have supplied you with the basic docs telling you how to plug it in, etc. Look for a model number somewhere. Also, that's the bridge (slightly smaller than the ones you design, as you can see!) :-)
connected to Linksys Broadband Wireless-G router WRTG v1.1
As David mentioned, this sounds as though you have both a wireless G unit and a Wireless B unit, and you are trying to bridge them.
I don't know if I am any closer to getting the eCS router, a Linksys Model BEFW1154 v4 Wireless-B Broadband Router, 2.4 GHz 802.11b, talking to the DSL router.
As Stan pointed out, there's no such model number. The unit you describe here is a BEFW11S4 4-port 802.11b broadband router/access point.
eCS router is connected to box thru Belkin NIC (recognized at eCS 1.2 install)
Let's set this up simply:
Computer running eCS (or anything else) with Belkin NIC --- goes to
LinkSys BEFW11S4 router ---- via CAT-5 (ethernet) cable
1. Now, forget about anything else. Besides the power connected to
the LinkSys and the CAT-5 from the Belkin NIC, nothing else should
be plugged into the LinkSys box. Hold down the reset button in the
back of the LinkSys box for 15 seconds.
2. At the eCS box, make sure that DHCP is enabled for the logical
interface assigned to your Belkin card (probably lan0). You can
check this with the TCP/IP Configuration applet. If it wasn't
already configured for DHCP, make the change in the applet, close
it, shut down and reboot. Skip to step 4.
3. If it was already set for DHCP, open the DHCP Monitor applet. In
the interface box, be sure that the correct interface number is
listed (probably lan0). Select Actions | Release lease and
acknowledge the warning dialog. Once the address has been
released, select Actions | Request lease. You should get an
address on the 192.168.1.0 subnet (at factory defaults, the
LinkSys turns on DHCP services, with anaddress pool starting at
.100, so you should see an address like 192.168.1.100 when you get
a valid lease). Select View | Details, and in the message log,
below, you should see something telling you that it recorded an
offer from server 192.168.1.1, followed by your assigned address
in parentheses.
4. Try pinging 192.168.1.1. If successful, open your browser to that
address, as I mentioned before. Log in per my earlier
instructions. You should get to the setup page.
5. Come back to the list and report your progress. The next step will
be to get the other router set up properly with the DSL, and
finally, to bridge the two units. We'll need to make sure the
firmware is current enough in the BEFW11SR4 for wireless bridging
to work, but that's a few steps down the road. Right now, I want
to make sure we have an entrance ramp and an exit ramp. We'll
build the "bridge" later. :-)
--
Lewis
------------------------------------------------------------
Lewis G Rosenthal, CNA Rosenthal & Rosenthal Accountants / Network Consultants New York / Northern Virginia www.2rosenthals.com
Team OS/2 / NetWare Users International www.novell.com
------------------------------------------------------------ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, send a message to
steward@2rosenthals.com with the command
"unsubscribe os2-wireless_users" in the body
(omit the quotes).
For help with other commands, send a message
to steward@2rosenthals.com with the command
"help" in the body (omit the quotes).
This list is hosted by Rosenthal & Rosenthal
P.O. Box 281, Deer Park, NY 11729-0281. Non-
electronic communications related to content
contained in these messages should be directed
to the above address. (CAN-SPAM Act of 2003)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|