Re: Wireless router help



That changes everything. Thanks for including the relevant information in your two posts.

I assumed (incorrectly) that your WAN port was an Ethernet interface, as most routers used in residential settings are configured that way.

The ISP equipment you have described has an Ethernet interface; the router's WAN interface is not Ethernet, therefore they are not compatible.

The guy who sold the router to you must have known the router did not meet your needs if he advised you to "just use lan 1". This person is apparently not your friend, as they have taken advantage of you.

To utilize the functionality of a router, traffic must pass through it (i.e.: your devices on the LAN side, the ISPs devices on the WAN side). My earlier post explained why you can not access the management interface from your host.

Right now you have the equivalent functionality of a wireless Access Point with the exception that you can't even effectively manage it.

Ideally you would return the router to the non-friend, get your money back, and buy another wireless router.

If that can not be done, consider the following two options:

Option A: Buy another wireless router with the appropriate WAN interface. Sell the existing router to someone who actually needs a router with a DSL WAN interface.

Option B: Buy a "non-wireless" router with the appropriate WAN interface. Attach the existing wireless router to it (LAN port of one device to LAN port of the other) using a "cross-over" Ethernet cable. The wireless router will provide the wireless connectivity. The non-wireless router would provide the security. In order for this to work you would need the LAN IP addresses of the two routers to be on the same network (e.g.: 192.168.1.0). HOWEVER, the two IP addresses must NOT be the same (e.g.: 192.168.1.1, 192.168.1.2). You would then be able to manage both devices from your host.

If you pursued option B, you would want to configure the two routers to have different IP addresses PRIOR to connecting the two routers together as described above. If they were connected together and had the same IP address, you would not succeed in configuring them.

Option A would be simpler, and easier for you to implement based on your skill set.

See if you can return the router to the non-friend. If that fails, I suggest you pursue Option A.

It's unfortunate that the manufacturer is not committed to providing adequate documentation. Typically, I would avoid buying products from such manufactures. If they can't meet their obligations, I can't be bothered buying their product (not even second hand).

Best Regards,
News Reader

nam-kha@xxxxxxxxxxxxx wrote:
OK Thanks, I have 4 lan ports on the back of the router and a dsl port
with a different type of connector. Guy I bought the router from said
just use lan 1. Assuming (correct me if i'm wrong) the dsl port is
what you call the wan port, what cabling do i need? I don't want to
break the isp provided lan cat5 lead that originally plugged straight
into the lan port on my pc

btw, i did not get a manula with the router, i bought it second hand.
I have downloaded both uk and spanish manuals from e-tech website, but
they are only 2 pages long and don't really help

Many thanks,

nam-kha

On 27 Mar, 21:28, News Reader <u...@xxxxxxxxxxx> wrote:
You have connected the ISPs device to the first of four LAN ports.

This is incorrect!

You connect ISP equipment to the WAN port. Your wired equipment gets
connected to the LAN ports. Your wireless also connects to the LAN side
of the router via RF (wireless).

The purpose of a router is to sit between two networks and facilitate
connections between them. Also, if traffic is not passing through the
router, how do you expect to derive the security benefits of the router?

What you want is for the router's WAN port to acquire an IP address from
a DHCP server of your ISP. Your host (computer) would acquire an IP
address from the DHCP server within the router. The host would then have
an IP address on the same network (192.168.1.0) as the router's web
server interface, and you would be able to access the web interface.

Right now, your host has an IP address from your ISP's network (not
192.168.1.0), and doesn't know how to reach the router's web interface.

Correct your cabling.

Configure your host with a static IP address (e.g.: 192.168.1.2)
temporarily, connect to the router, turn DHCP back on, configure your
host to use DHCP again, and resume whatever router configuration you desire.

Best Regards,
News Reader



nam-...@xxxxxxxxxxxxx wrote:
Hi guys,
I live in rural spain so can't get a landline let alone broadband. I
signed up with a local ISP who came out and installed an antenna on my
roof so I can access the internet via their wifi hotspot. Basically I
have a lan cable from this to plug into my laptop. OK works great. So
then I get more adventurous and buy a wireless router so I don't need
the lan cable to my laptop but use the laptops in built wifi to
connect to the router and the internet.
Everything works fine, but I can't access the router to change it's
settings anymore.
Guy I bought it off told me to turn off dhcp, so I accessed router
setup via html at 192.168.1.1 and did just that. He also told me to
change from unsecured to secured, but after I've turned of dhcp I
can't get the setup page on that IP anymore.
Heres a few more details -
windows vista home premium
compaq with inbuilt wifi
e-tech adwg02 wireless router
isp's network cable from antenna plugged into 1st of four lan
connections
network settings show my computer with an IP allocated from ISP, a
gateway with IP allocated by ISP, and in the middle, the ssid of the
router, but with no IP.
It all works fine but I need to access the router to turn on security.
Any ideas, help appreciated.
Thanks,
Nam-kha- Hide quoted text -
- Show quoted text -

.



Relevant Pages

  • Re: Remote Desktop problems
    ... my pc with the wan address I gave her....the wan changes periodically, ... > router doesn't "know" what that ip is and for what computer. ... >>> forwarding is for TCP port not udp. ... >>>> connection for my pc in her Network Connections area. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Remote Desktop problems
    ... my pc with the wan address I gave her....the wan changes periodically, ... > router doesn't "know" what that ip is and for what computer. ... >>> forwarding is for TCP port not udp. ... >>>> connection for my pc in her Network Connections area. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Remote Desktop problems
    ... my pc with the wan address I gave her....the wan changes periodically, ... > router doesn't "know" what that ip is and for what computer. ... >>> forwarding is for TCP port not udp. ... >>>> connection for my pc in her Network Connections area. ...
    (microsoft.public.windowsxp.general)
  • Re: Remote Desktop problems
    ... my pc with the wan address I gave her....the wan changes periodically, ... > router doesn't "know" what that ip is and for what computer. ... >>> forwarding is for TCP port not udp. ... >>>> connection for my pc in her Network Connections area. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Publish Web Server behind SBS 2003 Standard
    ... I ended up plugging another router into the WAN. ... How to configure Internet access in Windows Small BusinessServer2003http://support.microsoft.com/kb/825763/en-us ... network interface on right (By default the interface name should be ... input 80 in Outgoing port box. ...
    (microsoft.public.windows.server.sbs)