"Should be simple" test network problem. 1

[soonerkid]

Please forgive if this post belongs in a different forum. If so, just point me to it and I'll repost there.

I am relatively new to setting up "from scratch" networks. I am trying to set up a small office test bed network that includes a CISCO 2600 router CISCO 3550 series switch and 2 workstations for the lone purpose of training. I need it connected to the internet for updates/patching and anti-virus updates, etc.

The office is set up as a workgroup and is connected to the internet by dial-up (yea, I know) through a NETGEAR 8 port hub. All IPs are on the 192.168.0.0 network.

I have run a straight-through cat5 cable from the hub to fast 0/0 on the 2600 router and assigned 192.168.0.254 255.255.255.0. On fast 0/1 I have assigned 192.168.4.1 255.255.255.0. I have enabled RIP for both networks.

The switch VLAN is assigned 192.168.4.2 255.255.255.0 with a default gateway of 192.168.4.1.

The .4 network pings to everything up to and including fast 0/0 (192.168.0.254) but will not go through to anything further (I.E. A Win2003 server in the workgroup with an IP of 192.168.0.1 serving internet to the rest of the functioning workgroup).

The .4 network workstations/switch/router all see each other fine.

Fast 0/0 on the router (192.168.0.254) can ping everything on both sides including the above mentioned 2003 server as well as all of the .4 workstations and the switch.

The established workgroup computers can ping through to fast 0/0 (192.168.0.254) but no further and can not get fast 0/1 (192.168.4.1).

Now, there is probably something very obvious to those of you that have more experience but I am stuck. And again, If I posted this in the incorrect forum, please point me in the right direction and I'll repost.

I am thankful for any feedback and appreciate your time.

 

[plshlpme]

what device is your gateway for the 192.168.0.0 network?
it will need to have a route in it to tell all those devices that the 192.168.4.0 network is via 192.168.0.254...

if its a cisco.. then its just

ip route 192.168.4.0 255.255.255.0 192.168.0.254

if it is some other type of device then youll need to add that route by whatever means are available.

your 2600 has both networks configured and that is why it can ping through to both sides. but the 192.168.0 network has no knowledge of the 192.168.4 network. unless of course you have rip full configured on the 192.168.0 network then it is a different problem. do you have rip v1 or v2? youll need version 2 for classless routing.

 

[soonerkid]

Thank you for responding! I tried the ip route command but I had the wrong IP addresses. I am away from the office at the moment but I will try the correct IPs as soon as I get to work in the morning.

I am just using the CISCO 2600 as the gateway and I am hoping that it will suffice.

At the moment I am unsure of which version of RIP I am using but the CISCO literature that I was using to configure the router led me to believe that both were available and it appeared to be an auto configuration ...If I wanted to use just one or the other I would have to enter other commands to specify the version ...is this incorrect?

In the morning I will try the correct IP route command to see if it works. I will keep you posted ...thanks for your time and effort. It's much appreciated.

 

[soonerkid]

RIP version 1 and 2 (Tx and Rx) enabled for both 0/0 and 0/1 on router.

Unable to set static ip route 192.168.4.0 255.255.255.0 192.168.0.254 on router ...it kicked back that it was on "this machine" which makes sense ...sorry for my lack of exp.

Do I need to add a physical bridge to perform gateway functions? Or can I make it work with the hardware I have through configuration?

 

[plshlpme]

what do you have set for a default route on your windows server and the established workgroup computers.

i took it that your 2600 router was new to the network... is it also your gateway to the internet?

 

[soonerkid]

The router, switch and both .4 workstations are all new. The windows server is pulling default gateway/DNS information from the ISP and the established workstations are using the server IP for a default gateway (192.168.0.1).

The router is not the gateway to the internet. I want to set it up so I can break/fix for training without killing the internet for the server or established workstations.

The Windows Server is connected via RJ11 to POTS for dial-up and cat5 to a NETGEAR hub. All established workstations are connected to the hub via cat5. It's cat5 from the hub to my new router.

 

[plshlpme]

ok so your server is acting as a router.
you will need to add a route on it to the 192.168.4 network
that should allow all your clients to talk to the .4 network.


i think youll need something like this in your windows server..

-p : When used with the add command, the specified route is added to the registry and is used to initialize the IP routing table whenever the TCP/IP protocol is started. By default, added routes are not preserved when the TCP/IP protocol is started. When used with the print command, the list of persistent routes is displayed. This parameter is ignored for all other commands. Persistent routes are stored in the registry location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\PersistentRoutes.

route add -p 192.168.4.0 mask 255.255.255.0 192.168.0.254

 

[soonerkid]

Trying this now ...will let you know the outcome shortly (can't reboot server for a few more minutes).

Should I still have RIP configured on the router? If so I want to make sure it's set up correctly. I only have the two networks entered in the RIP configuration (192.168.4.0 and 192.168.0.0) with no neighbor. Suggestions? Add the .0 network for a neighbor?

 

[soonerkid]

Route added to the default reg string, server restarted, no joy.

 

[soonerkid]

With this reg string entered, shouldn't a "route print" command from windows prompt reveal persistent routes? Mine is still showing "None".

 

[soonerkid]

I added this string to the routing table on the server through a command prompt instead of the reg and I am pinging away.

 

[soonerkid]

Now I can't get the router to see the DNS servers being assigned by the ISP. Possibly an issue with the ISP gateway?

 

[plshlpme]

so now you can ping on the lan.. but you cannot get to the internet from the .4 network... does your windows server have any restrictions to which subnets can "nat" through it?

normally on a cisco there would be an access-list that would determine this... are you just using windows internet connection sharing or do you have some sort of software acting as a router on that server.

 

[soonerkid]

I do not know of any restrictions for NAT that would be configured on the server.

As of yet, there is no security set up on the router. I'll set all that up after clean comms have been established.

Just using connection sharing ...no routing software has been installed.

 

[plshlpme]

ok well you need a router now at this point
your new clients on the 192.168.4 network can get around your lan because your 2600 router is connecting both networks together...

in order to get to the internet the 2600 router would need a default route using the windows server as the next hop address

so on the 2600 you would need
ip route 0.0.0.0 0.0.0.0 [windows server address]

give that a try

 

[soonerkid]

That worked perfectly! Thanks very much for all your suggestions ...I learned a lot! If I run into something else I will repost here. Again, THANKS!!!