Options

NAT problem with port forwarding

Steve10393Steve10393 Member Posts: 32 ■■□□□□□□□□
I can't get this bittorrent protocol to forward for some reason. These are my current NAT statements.

ip nat inside source list 1 interface FastEthernet0/1 overload
ip nat inside source static tcp 192.168.10.1 26866 71.x.x.x 26866 extendable
ip nat outside source static tcp 72.x.x.x 26866 192.168.10.1 26866 extendable

Fa 0/1 is the egress port going to my cable modem.


interface FastEthernet0/0
ip address 192.168.10.1 255.255.255.0
ip nat inside
load-interval 30
duplex auto
speed auto
!
interface FastEthernet0/1
ip address dhcp
ip nat outside
load-interval 30
duplex auto
speed auto
service-policy output xxxxxxxxxx


any help?

Comments

  • Options
    mikearamamikearama Member Posts: 749
    Steve,

    Post the contents of your access list... the one named in the nat statement (list 1).
    There are only 10 kinds of people... those who understand binary, and those that don't.

    CCIE Studies: Written passed: Jan 21/12 Lab Prep: Hours reading: 385. Hours labbing: 110

    Taking a time-out to add the CCVP. Capitalizing on a current IPT pilot project.
  • Options
    NetstudentNetstudent Member Posts: 1,693 ■■■□□□□□□□
    One question....Why do you have static translations for the same private address, but different public addresses?
    There is no place like 127.0.0.1 BUT 209.62.5.3 is my 127.0.0.1 away from 127.0.0.1!
  • Options
    Steve10393Steve10393 Member Posts: 32 ■■□□□□□□□□
    Standard IP access list 1
    10 permit any (639673 matches)


    There is another computer on my network, a labtop, and also a linksys wireless G router with no broadcast on and a unique ssid.

    As far as the different public IP addy's, according to the cisco page I read, the inside command uses the inside global ip addy and the outside statement uses the outside global ip addy.

    All I know is that if I connect the cable modem directly to the pc and use a public addy for the computer the port gets forwarded fine, but when it's going through my network it does not so I assume it's NAT.
  • Options
    Steve10393Steve10393 Member Posts: 32 ■■□□□□□□□□
    Oh, fixed the first static nat statement. I missed the error, the first private address should indeed have been 192.168.10.2, the address of the pc. This change did not have any effect however, and it should be noted I've tried these two static NAT statements with UDP as well since I wasn't sure if it was using TCP to communicate or not. This is the protocol it uses for DHT(?) to find peers, I think, or something. Anyways not transferring files, is the point.
Sign In or Register to comment.