Can not see my home network across router ports

have you configured the DLINK router to know that 192.168.3.0/24 is reachable via 192.168.1.3 ???

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route

Gateway of last resort is 192.168.1.1 to network 0.0.0.0

C* 192.168.1.0/24 is directly connected, Ethernet0/0 C 192.168.3.0/24 is directly connected, Ethernet0/1 S* 0.0.0.0/0 [1/0] via 192.168.1.1 ExtGate# ============================================ ExtGate#Show int e0/0 Ethernet0/0 is up, line protocol is up Hardware is AmdP2, address is 0050.731b.ca01 (bia 0050.731b.ca01) Internet address is 192.168.1.3/24 MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:00, output 00:00:00, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 6000 bits/sec, 3 packets/sec 5 minute output rate 2000 bits/sec, 3 packets/sec 19234 packets input, 3186361 bytes, 0 no buffer Received 2099 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 input packets with dribble condition detected 19985 packets output, 2087678 bytes, 0 underruns 4 output errors, 16 collisions, 2 interface resets 0 babbles, 0 late collision, 52 deferred 4 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out ExtGate# ======================================================== When logged into the e0/0 interface I get:

ExtGate>ping 192.168.1.1

Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/4 ms ExtGate>ping 192.168.3.1

Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.3.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms ExtGate>ping 192.168.3.2

Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.3.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/4 ms ExtGate>

news4.newsguy.com!extra.newsguy.com!postnews.google.com!o5g2000hsb.googlegroups.com!not-for-mail

Gecko/20070312 Firefox/1.5.0.11,gzip(gfe),gzip(gfe)

My Dlink is a 614+. I see no place to put a static route in that router...BUT... - I put this entry in the firewall section : Allow 192.168.3.1 WAN,192.168.1.1 LAN,192.168.3.1-192.168.3.254 IP (0),*

====

I understand what you are asking, but do not see where it would help me communicate across my Cisco 3620 router ports.

Gerald

Thats not going to help you, you need to access the static route table on the device. If your router is too low-end to deal with it (although most tiny consumer ones I've dealt with do have a static route table.) you'll have to do something else, one by one on the workstations that won't persist across reboots...

Its because of the routing tables in each of the workstations.

Think about what they have (although a 'route print' will show you, its going to be overload at this point).

They know how to reach 192.168.1.0/24. Thats their connected route. Each of them are configured on that network, they know that to reach 192.168.1.0/24 by putting out packets out on the Network.

The other entry that they have is the default route. They're going to push every other packet they don't know about up to your Dlink.

There's nothing in there now to know about 192.168.3.0/24. Its totally off their radar. You have a 2nd router on your network. The workstations have no idea its there. They don't listen to RIP.

Now, there is a protocol built into TCP/IP that will allow your workstations to learn routes like this. ICMP redirects will allow your workstations to learn that the 2nd router is there. BUT, something has to generate them. The usual thing to do so is going to be your default gateway router, your Dlink. Put in a static route there, when a workstation pushes a packet up for 192.168.3.0/24 to your dlink, it should generate an ICMP redirect packet, and push the packet down to your other router. From then on, the workstation should directly generate packets heading for 192.168.3.0/24 over to your cisco router. It all works pretty well usually.

Your other choice if the Dlink doesn't support a static route table (although again, I haven't seen many that don't) is to add a static route into each workstation with the 'route' command from the command line.

Something like route add 192.168.3.0 mask 255.255.255.0 192.168.1.3 metric 1

should work on windows. As I said, this will only work between reboots. Once you reboot your workstation, it'll go away.

This will tell your workstation that all packets for 192.168.3.0/24 should be handled by 192.168.1.3, your cisco router.

The static route in the default gateway works much better though.