Outgoing access list is 110
Inbound access list is not set
There it is—that’s our problem all right! In case you’re wondering why R2 could telnet
to Server1, it’s because an ACL filters only packets trying to go through the router—not
packets generated at the router. Let’s get to work and fix this:
R2#
config t
R2(config)#
no access-list 110
I just verified that I can telnet from PC1 to Server1, but let’s try telnetting from R1
again:
R1#
telnet 172.16.20.254
Trying 172.16.20.254 ... Open
User Access Verification
Password:
Nice—looks like we’re set, but what about using the name?
R1#
telnet Server1
Translating "Server1"...domain server (255.255.255.255)
% Bad IP address or host name
Well, we’re not all set just yet. Let’s fix R1 so that it can provide name resolution:
R1(config)#
Do'stlaringiz bilan baham: |