RT314 as a switch

[Mediaman]

I need a 10/100 switch in one of my rooms and happen to have a long forgotten (Netgear RT314 router) unit which would be perfect if I can turn off DCHP

Unfortnately I cannot get into the admin pages if I open a browser to 192.168.0.1 with a standalone PC wired to its LAN port ; I just get page not found. I know I did not change the default, but it was lent out, so who knows. Still I just want to use it as a switch.

IPconfig shows:

DCHP enabled
Autoconfigration IP address =169.254.42.19
Subnet Mask = 255.255.0.0.
Dafault Gateway - blank

No reset button. While docs say I can telnet to it via the serial port, it says I must know the IP address, so no luck there.

If I just use switch as is, does the IP config info suggest I can 'safely' use it as a switch given gateway is blank? ( even though DCHP shows as enabled?) My system is all using 10.xx.xx.xx with a mask of 255.255.255.0

 

[YeOldeStonecat]

Maybe DHCP already is disabled. When you get a 169.254.xxx.xxx address...that's the Windows auto assign IP when it cannot find a DHCP service to pull an IP from.

Try setting the workstation manually, 192.168.0.10/255.255.255.0. Can leave the gateway and DNS blank. Then try to log into the router at 192.168.0.1

If that doesn't work..maybe it was reconfigured to 192.168.1.1, so take same approach to try that.

 

[jdabbs]

No reset button. While docs say I can telnet to it via the serial port, it says I must know the IP address, so no luck there.

Telnet via TCP/IP and a terminal session over serial are two different functions. You shouldn't need an IP for a direct connection, just the connection parameters.

 

[Mediaman]

Telnet via TCP/IP and a terminal session over serial are two different functions. You shouldn't need an IP for a direct connection, just the connection parameters.

True, I dont need an IP to connect, but per the dcoumentation, I need to 'know' the IP address when connecting via telnet. See below. I guess I can locate a serial cable, use Hyperterminal and try it out (back to the future!)

The docs do talk about the need to assign an IP if you dont know it (exactly my scenario) ....but they dont tell you HOW TO ASSIGN...only HOW TO ACCESS. Perhaps it will be obvious if I can connect via telnet.

Ref: (from ftp://downloads.netgear.com/files/netgear1/RT3guide.pdf)

You can access the built-in interface by a Telnet call from any TCP/IP workstation on the LAN or the remote network. In order to use the Telnet Protocol, you must know the current IP address of the router. If you do not know the router’s current IP address, you must use a serial connection to
assign an IP address. The router is shippped with a default address of 192.168.0.1.

To establish a Telnet connection from the LAN, you must set up your workstation to reach the IP address of the router by doing one of the following:
• Set your workstation to an IP address on the currently programmed subnet of the router.
• Add a route to the static routing table of the workstation to indicate that the router can be
reached through the local LAN port.

To access the router by Telnet from a Windows PC:
1. From the Windows toolbar, select Start.
2. Select Run...
3. In the Open field, type:telnet 192.168.0.1

 

[Dennis Wood]

We had one of these..yes you'll need a serial cable (wired correctly) and good old hyperterminal. It was one of the few devices I've worked with at this price point where you could "get under the hood" and program filters etc.

 

[Mediaman]

I found a serial cable and connected the router for my last ditch effort for to breathe life into this old but rock solid unit.

When I try to connect (via command window or hyperterminal) , it tells me that it cannot open connection to host of port 23.

I googled this and it tells me to:

a) start the telnet service
b) open port 23

Not sure I know how to do either!. I used a command window for telnet as well as Hyperterminal, as well as "Microsoft Telnet;, but not sure if that covers (a). Read elsewhere to use Control Panel/Administrative Tools/Services and start the service there. but I did not see it to select.

No clue re (b).

Using an XP machine.

 

[jdabbs]

What were the connection parameters you used to connect via hyperterminal?

 

[Mediaman]

It was as per the documentatiion, ie, I opened a command window and used

hypertrm.exe/ttelnet address [ : port ]

ie

hypertrm.exe/t 192.168.0.1

 

[jdabbs]

It was as per the documentatiion, ie, I opened a command window and used

hypertrm.exe/ttelnet address [ : port ]

ie

hypertrm.exe/t 192.168.0.1

That's not a terminal session, try 9600-8-N-1.

Edit: Like so:
http://www.petri.co.il/csc_how_to_use_hyperterminal_with_cisco_routers_and_switches.htm

 

[Mediaman]

You want me to type that in a command line?? I assume no!

I checked the link - not sure want to type when it asks me to connect, but I do get to the COM1 screen (sometimes) and then a blank hyperterminal screen. After that the keyboard does not respond (wrong emulation I guess).

If I type telenet from the dos prompt, it too tells me it cant open port 23.

Not having much luck.

 

[jdabbs]

http://www-tss.cisco.com/eservice/compass/common/tasks/task_veri_Config_Hyperterminal.htm

Follow these directions exactly, with the exception of using COM1 instead of COM2 (there may be a bit of guesswork as to which com port is used, but COM1 is usually the correct one). When you get to a place you don't understand, post your question.

 

[Mediaman]

jdabbs, thanks for the spoon feeding here.... and now that I followed each step as outlined, it of course got me in!

First prompt was password - only took 15 tries ( I had set it almost 8years ago).

After that it was menu driven and straighforward - even for me! DCHP was not enabled, and I saw the IP address was 192.168.1.91 which I would have never guessed. I reset it to my new convention, and now it is accessile via the browser - yay!

So thanks again for sticking with me, and thanks for my brand new switch!