CCNA - RPC Between Subnets

Author

RPC Between Subnets

Joe Dali

2004-01-19, 4:31 pm

Hi guys,

You helped me a ton a few weeks ago with my 3640.

I have another one for you.

How can I get the two networks (192.168.1.x and 192.168.2.x) to communciate via RPC/Windows networking?

I cannot connect to a host on either subnet from eachother.

Do I need an access list to permit any and all between the 2 subnets?

Thanks alot for any suggestions.

DrWatsonJr

2004-01-19, 6:06 pm

I believe RPC uses NetBIOS broadcasts, therefore, if you configure helper addresses on each router interface for the other subnet's host machine, it should work.

Example...

On Ethernet 1
ip address 192.168.10.1 255.255.255.0
ip helper-address 192.168.20.10

On Ethernet 2
ip address 192.168.20.1 255.255.255.0
ip helper-address 192.168.10.10

Joe Dali

2004-01-19, 6:17 pm

Thanks DRWJr, I actually tried that before posting per the routergod.com article featuring Trinity.

No luck though ... still no connectivity.

I guess I need Host files, WINS?

Access list that allows ALL?

Thanks for any help.

DrWatsonJr

2004-01-19, 7:09 pm

Yeah, actually you can put the IP addresses and host names in your lmhosts file (WINS). you should also be able to connect to the other machine by using it's IP address.

Example:

If you go to "start, then run" and type in \\192.168.10.10 you should be able to connect.

Joe Dali

2004-01-19, 7:49 pm

I can't even ping host to host ... so I guess my issues are deeper.

But, host on 2nd network can connect to the Internet just fine.

Hmmmmmmmm ...

DrWatsonJr

2004-01-19, 8:29 pm

Default Gateway issue?

Joe Dali

2004-01-19, 8:31 pm

Well all use a DG of my Linksys router --- 192.168.1.1 ...

Ugh.

dmaftei

2004-01-20, 8:40 am

quote:
Originally posted by Joe Dali
so I guess my issues are deeper.

Post the routing tables off your hosts ('route print' in a cmd shell).

Joe Dali

2004-01-21, 9:27 pm

Route print from host on 192.168.2.x network.

C:\Documents and Settings\administrator.DALI>route print
==============================
==============================
===============
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 10 b5 43 44 91 ...... HP EN1207D-TX PCI 10/100 Fast Ethernet Adapter -
McAfee Firewall Network Filter Miniport
==============================
==============================
===============
==============================
==============================
===============
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.2.10 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.2.0 255.255.255.0 192.168.2.10 192.168.2.10 1
192.168.2.10 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.2.255 255.255.255.255 192.168.2.10 192.168.2.10 1
224.0.0.0 240.0.0.0 192.168.2.10 192.168.2.10 1
255.255.255.255 255.255.255.255 192.168.2.10 192.168.2.10 1
Default Gateway: 192.168.1.1
==============================
==============================
===============
Persistent Routes:
None

I asked our network engineers today how to route netbios over one router with 2 interfaces and they couldnt' offer me a suggestion either. I don't get it ...

dmaftei

2004-01-21, 10:06 pm

quote:
Originally posted by Joe Dali
Route print from host on 192.168.2.x network...

With this routing table your host will never go beyond 192.168.2.0/24, because your default route points to an unreachable gateway. Try changing the gateway for the default route, the "0.0.0.0" line, to 192.168.2.1 (I'm assuming that's your router's interface on 192.168.2.0/24).

Joe Dali

2004-01-21, 11:00 pm

Thanks D, but I actually tried that initially thinking that any hosts on .2 net would need to specify that as the DG but no dice. If you see my other thread, I solved the problem of not being able to reach the web by using 192.168.1.1 as the DG using a static route on the Linksys.

To sumamrize, I have one 3640, two Ethernet interfaces.

--- 192.168.1.30
--- 192.168.2.1

Linksys cable router acts as the DG for both networks: 192.168.1.1

Linksys has static route entry for 192.168.2.x network.

My dilema is communication between hosts on one router with 2 ethernet interfaces.

I've tried using IP-HELPERS etc. with no luck.

I guess its impossible. NO WAY!!!

Any CCIEs out there?

HELP, I don't understand why its so difficult.

UGH.

dmaftei

2004-01-22, 8:44 am

You may have a problem on the router, that's true, but you also have the host problem. With the current routing table your poor 192.168.2.10 host is dropping everything sent outside 192.168.2.0/24 (think about ARP...)

Fix your default route first (I don't think you need lmhosts, just put the correct gateway), then convince yourself that your router can talk with your poor host (ping the router from the host, and the host from the router). Once you know that you can get to the router, it's time to investigate why you cannot go through the router. At that point we'll probably ask for relevant stuff from the router (routing table and access lists).

Joe Dali

2004-01-22, 10:06 pm

Router#sh run
Building configuration...

Current configuration:
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Router
!
enable secret 5 $1$o4XX$65P8hEP2jDlZTSMO2pmwr/
!
ip subnet-zero
!
isdn voice-call-failure 0
!
controller T1 1/0
!
controller T1 1/1
!
controller T1 1/2
!
controller T1 1/3
!
interface Ethernet0/0
ip address 192.168.1.30 255.255.255.0
ip helper-address 192.168.2.1
ip helper-address 192.168.2.10
no ip directed-broadcast
!
interface Ethernet0/1
ip address 192.168.2.1 255.255.255.0
ip helper-address 192.168.1.30
ip helper-address 192.168.1.2
no ip directed-broadcast
!
interface Serial2/0
no ip address
no ip directed-broadcast
shutdown
!
interface Serial2/1
no ip address
no ip directed-broadcast
shutdown
clockrate 125000
!
interface Serial2/2
no ip address
no ip directed-broadcast
shutdown
clockrate 125000
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.1.1
no ip http server
!
line con 0
transport input none
line aux 0
line vty 0 4
password duh
login
!
end

Pings:

Router#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/1/4 ms
Router#ping 192.168.1.2

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

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

So, router can ping everything, but hosts cant ping between subnets ... hmmm

Route print from poor host:

C:\Documents and Settings\administrator.DALI>route print
==============================
==============================
===============
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 10 b5 43 44 91 ...... HP EN1207D-TX PCI 10/100 Fast Ethernet Adapter
McAfee Firewall Network Filter Miniport
==============================
==============================
===============
==============================
==============================
===============
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.10 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.2.0 255.255.255.0 192.168.2.10 192.168.2.10 1
192.168.2.10 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.2.255 255.255.255.255 192.168.2.10 192.168.2.10 1
224.0.0.0 240.0.0.0 192.168.2.10 192.168.2.10 1
255.255.255.255 255.255.255.255 192.168.2.10 192.168.2.10 1
Default Gateway: 192.168.2.1
==============================
==============================
===============
Persistent Routes:
None

I DID change the DG as you suggested and you and I can get to the Net which is cool ... I think I'm almost there, I think its a access-list not set issue, who knows though ... I'm just a caveman ... LOL.

I'm trying to add a static route and keep getting bad argument ... hmmm.

Joe Dali

2004-01-22, 10:12 pm

How about applying an any any AL on the whole friggen router?

: o

dmaftei

2004-01-22, 10:37 pm

All right, let's take it easy, this starts to become interesting.

1. You don't need any access list. You don't have any, so your interfaces are wide open. That's good (for now...)

2. The 'ip helper-address' are useless for now. Forget about RPC for the moment; let's get the hosts to ping each other, and to ping you don't need 'ip helper-address'.

3. Two of the three pings are to the router's own interfaces; only 192.168.1.2 goes out. Who's 192.168.1.2? The HappyHost?

4. What about PoorHost (192.168.2.10)? Can you ping it from the router?

Is this your topology?

PoorHost --- Router -- HappyHost

PoorHost: 192.168.2.10
HappyHost: 192.168.1.2

dmaftei

2004-01-22, 10:52 pm

Do a 'show ip route' on the router.

Joe Dali

2004-01-22, 11:12 pm

Thank you thank you for your help with this weird issue ...

Router#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
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, E - EGP
i - IS-IS, 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.2.0/24 is directly connected, Ethernet0/1
S* 0.0.0.0/0 [1/0] via 192.168.1.1
Router#

Joe Dali

2004-01-22, 11:14 pm

Router#ping 192.168.2.10

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

Interesting that the router can ping all ...

Router#ping 192.168.1.2

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

dmaftei

2004-01-22, 11:21 pm

OK, so before I hit the hay, can you confirm which of the following works and which doesn't:

- from PoorHost you can ping Router
- from PoorHost you can ring HappyHost
- I know that from Router you can ping both hosts
- from HappyHost you can ping Router
- from HappyHost you can ping PoorHost

We'll resume tomorrow; have a good one.

Joe Dali

2004-01-22, 11:29 pm

Happy host:

C:\Documents and Settings\Administrator>ping 192.168.1.30

Pinging 192.168.1.30 with 32 bytes of data:

Reply from 192.168.1.30: bytes=32 time=2ms TTL=255
Reply from 192.168.1.30: bytes=32 time=1ms TTL=255
Reply from 192.168.1.30: bytes=32 time=1ms TTL=255
Reply from 192.168.1.30: bytes=32 time=1ms TTL=255

Ping statistics for 192.168.1.30:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\Documents and Settings\Administrator>ping 192.168.2.1

Pinging 192.168.2.1 with 32 bytes of data:

Request timed out.

Joe Dali

2004-01-22, 11:31 pm

"poor host":

C:\Documents and Settings\administrator.DALI>ping 192.168.1.2

Pinging 192.168.1.2 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\administrator.DALI>ping 192.168.1.30

Pinging 192.168.1.30 with 32 bytes of data:

Reply from 192.168.1.30: bytes=32 time=1ms TTL=255
Reply from 192.168.1.30: bytes=32 time=1ms TTL=255
Reply from 192.168.1.30: bytes=32 time=1ms TTL=255
Reply from 192.168.1.30: bytes=32 time=1ms TTL=255

Ping statistics for 192.168.1.30:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

C:\Documents and Settings\administrator.DALI>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=2ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

Hmm, can ping E0/0 but not host on that network ... but can reach the Linksys outbound DG ...

Joe Dali

2004-01-22, 11:37 pm

How does this differ being that its on the same router instead of being between two different routers is what I wonder? Shouldn't in my mind ... but I failed 640-407 by a few (5) points in 2000, lol ...

dmaftei

2004-01-22, 11:37 pm

Joe, there's something wrong with the router's routing table, but I'm too tired now. We'll atack it again tomorrow.

(Even better, maybe a fairy-ccie steps in and brings light

)

Joe Dali

2004-01-22, 11:44 pm

Hey no worries man, this is a real life exercise we can all learn from ... most people need to route Windows over routers! :0)

O fairy CCIE, bring forth your wizdum and enlighten us, for thou art indeed a god(ess).

boyam

2004-01-24, 12:07 am

My first post here

I'm curious as to what you have as your gateway in the static route statement on the linksys router. The gateway should be 192.168.1.30. I think the linksys router is confiscating (in some way) your pings from the 1.x network so they never make it back to the 2.x network.

To prove the theory, Place a route statement on the happyhost by typing at the command prompt route add 192.168.2.0 mask 255.255.255.0 192.168.1.30. This will keep happyhost from using the default gateway to find its way to the 2.x network.

Joe Dali

2004-01-24, 2:17 am

That worked ~ ! ~ ... You guys rock ... funny, I tried adding route add statements and kept getting "Bad Argument" messages, but your's worked on the first try, which leads me to believe I was doing something wrong, obviously ... thanks man ...

From happy host - pings to sad host:

C:\Documents and Settings\Administrator>ping 192.168.2.10

Pinging 192.168.2.10 with 32 bytes of data:

Reply from 192.168.2.10: bytes=32 time=2ms TTL=127
Reply from 192.168.2.10: bytes=32 time=1ms TTL=127
Reply from 192.168.2.10: bytes=32 time=1ms TTL=127
Reply from 192.168.2.10: bytes=32 time<1ms TTL=127

Ping statistics for 192.168.2.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 1ms

C:\Documents and Settings\Administrator>

boyam

2004-01-24, 9:01 pm

Glad it worked. Nothing like seeing Replys after seeing a bunch of request timed outs.

Sponsored Links