cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
cancel
749
Views
0
Helpful
1
Replies

problems doing NAT to a DCLINK server TCP port 3003

We use scanners talking to a DCLINK server on port 3003, when setting up NAT to the backup server  it will not connect to port 3003, though we can ping it and telnet on port 23 see relevent config below:

interface GigabitEthernet0/0.17

description DR Voice Vlan

encapsulation dot1Q 17

ip address 172.16.17.253 255.255.255.0

ip wccp 61 redirect in

ip nat outside

!

interface GigabitEthernet0/0.176

description DR data vlan

encapsulation dot1Q 176

ip address 172.17.6.252 255.255.255.0

ip wccp 61 redirect in

ip flow ingress

ip flow egress

ip nat inside

!

interface FastEthernet0/3/0

description N3008351R IPMAN

bandwidth 10000

ip address 172.28.6.254 255.255.255.252

ip wccp 62 redirect in

ip flow ingress

ip flow egress

ip nat outside

!

ip nat inside source static 172.17.6.174 172.16.17.230

sh ip nat trans

Pro      Inside global                Inside local               Outside local                Outside global

udp 172.16.17.230:161       172.17.6.174:161   172.17.7.206:1647  172.17.7.206:1647

icmp 172.16.17.230:3528   172.17.6.174:3528 172.17.7.206:3528  172.17.7.206:3528

---            172.16.17.230      172.17.6.174                                ---                                          ---

anybody any ideas I have not had problems before with NAT, the server has not got any firewall setup

1 Reply 1

raga.fusionet
Level 4
Level 4

hi,

If you can ping and telnet and you have a one to one translation, I highly doubt it is an issue with the NAT configuration.

I would start looking at the server itself.

Raga

Review Cisco Networking for a $25 gift card