thechangelab.com

3 Responses to “Trendnet TEW-432BRP wireless router as a second wireless access point”

1. Quin Hahn Says:
   November 29th, 2008 at 5:25 pm

   Enjoyed your effort. With that kind of expertise on you part I thought you may have an idea of my problem. I have been using a Netgear Router RP614 v2 as “hard wired” between two computers. My IP is Comcast, broadcasting DHCP through a Arrisi/Touchtone modem. With this hook-up all has worked well with both computer. I bought a TrendNet 54mps 802.11g Wireless Firewall Router. The purpose was to provide a “household” wireless to my laptop. Following the install instructions, it finishes, then notes that I do not have an internet. Reset, reboot, re-wiring, eliminating the 2nd computer all have not solved the problem. Perhaps you would have some ideas. It would be most appreciated.

   Thanks in advance,

   Quin Hahn
   quinh@comcast.net

2. toshiya Says:
   January 17th, 2009 at 4:43 pm

   Hi Quin.

   Just to let you know I’m no pro at this. A lot of trial and error -
   hence my “lab”. Plus, I ended up having to return my Trendnet as it died
   a few weeks later. However, a defective router doesn’t sound like your
   problem. Make sure that the network cable going from the Netgear to the
   Trendnet ISN’T connected to the latter’s WAN port. It should connect to
   one of the – usually – four LAN ports.

   Alternatively, you can try the following. Before doing this you may even
   want to uninstall any software that came with the Trendnet. 99% of the
   time, this kind of software is unnecessary crapware. Most consumer grade
   routers can be configured using a web browser. I also make a few other
   assumptions in the following, but hopefully I’m right about them

   First, disconnect your Trendnet and boot up one of your PCs. Make sure
   that it’s connected to your router and that the modem is on.
   Click on Start -> Run -> type “cmd’ then hit enter. ( “Win key + r” )
   Type “ipconfig /all” then enter.
   The line that says “Default Gateway” shows the IP address of your
   router. Make a note of it. Example, 192.168.2.1
   Also, make a note of the “DNS Servers”.

   Second, disconnect the ethernet cable from the router to your PC and
   connect it to one of the Trendnet’s LAN ports. ( PC < -> Trendnet ) Turn
   on the Trendnet wireless router.
   Check the instruction guide about accessing the web interface.
   Typically, you’ll start up your web browser -> enter the Trendnet’s IP
   address -> you may be prompted for a login and password (use the one in
   the guide). Once you’re in, then you can finally start getting your
   hands dirty.

   Third, settings you need to change:

   router IP address
   -> if your Netgear is doing DHCP, make sure the address is outside the
   DHCP range. For example, mine defaults to 192.168.2.10 to 192.168.2.100.
   So, an IP address higher than 192.168.2.100 – like 192.168.2.250 – is safe.
   Also, you’ll probably want it in the same group. So, if the default
   gateway address (see above) was 192.168.0.1 (note the .0.1), then make
   it 192.168.0.250

   default gateway IP address
   -> the same as your PC’s (see above). So the address of your Netgear router.

   name server aka DNS Servers
   -> the same as your PC’s (see above).

   *Turn off / disable DHCP. You may also want kill the UPnP – a matter of
   preference

   *whatever you want re: wireless settings.

   Fourth, turn off the Trendnet. Get another network cable to connect the
   Trendnet (again use a LAN port) to the Netgear. In other words,
   PC< ->Trendnet< ->Netgear< ->Modem

   Fifth, the judgement day (tests).
   1. Turn on the Trendnet and see if it lights up.
   2. From your PC, start up your browser and try getting to the web
   interface again – of course, you’ll be using the new IP address you set
   for it.
   3. From your PC, start -> run -> “cmd” again. Type “ping [Trendnet IP
   address]“. You should not get the loathed “Request timed out” message.
   4. From your PC again, “ping” the IP address of the Netgear router.
   5. From your PC again, “ping google.com”

   The first three tests are like general hardware tests. Like, I hope it’s
   not busted.
   The fourth one tests if your LAN (local area network) is okay.
   The fifth one tests if your WAN (wide area network, for you aka
   Internet) is okay.
   If all is well, then you can progress to the laptop wireless stuff. Do
   the ping tests and try web interface again.

   If the thing fails the first three tests, I feel pretty comfortable
   saying it’s time to take it back. Unless if someone else out there knows
   more about this.

   Hope this helps and GOOD LUCK!

3. GarykPatton Says:
   June 16th, 2009 at 2:01 am

   Hi. I like the way you write. Will you post some more articles?

Leave a Comment