Re: Router debug

Re: Router debug

NewsGroups | Search | Tools
 comp.dcom.sys.cisco  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Re: Router debug terrydoc@o2.ie 06-24-2008
`--> Re: Router debug terrydoc@o2.ie06-24-2008
Posted by terrydoc@o2.ie on June 24, 2008, 4:07 am
If you were  Registered and logged in, you could reply and use other advanced thread options
Thanks for the reply, I'm sorry as in my original post I had changed
some of the IP addresses and it appeared that the source and
destination are all in the same network - this is not the case - see
the correct debug output here. I know the client (10.0.18.35) can ping
the NATted addresses (10.0.0.130/134/135) - so NATting is working ok.
But when the client tries to access the application I get...
3725_Backup#
17:42:35: IP: s=10.0.18.35 (Dialer4), d=10.0.0.135, len 48, rcvd 2
17:42:35: TCP src=2739, dst=3200, seq=3212891754, ack=0, win=32768
SYN

17:42:35: IP: s=10.0.0.135 (local), d=10.0.18.35 (Dialer4), len 40,
sending
17:42:35: TCP src=3200, dst=2739, seq=0, ack=3212891755, win=0 ACK
RST

17:42:35: IP: s=10.0.18.35 (Dialer4), d=10.0.0.135, len 48, rcvd 2
17:42:35: TCP src=2739, dst=3200, seq=3212891754, ack=0, win=32768
SYN

17:42:35: IP: s=10.0.0.135 (local), d=10.0.18.35 (Dialer4), len 40,
sending
17:42:35: TCP src=3200, dst=2739, seq=0, ack=3212891755, win=0 ACK
RST
***************************************************************************************
Is it still the case that the app isn't listening on port 3200?


> It's showing that the source IP 10.10.10.130 is attempting to connect to
> 10.10.10.135 on port 3200 (The SYN packet). The server then responds with a
> RST packet, which indicates that no application is listening on port 3200.
> The source and destination are all inside networks (all on the 10.10.10.x
> network), so no NATing is being done
>
>
>
> > Users cannot connect to the applications but can PING the app servers
> > (10.10.10.130/134/135) - these are NATted - users see them as
> > 192.168.0.42/37/35. Any suggestions on what the router debug output is
> > saying?
>

Pure Networks
Posted by terrydoc@o2.ie on June 24, 2008, 2:58 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
> Thanks for the reply, I'm sorry as in my original post I had changed
> some of the IP addresses and it appeared that the source and
> destination are all in the same network - this is not the case - see
> the correct debug output here. I know the client (10.0.18.35) can ping
> the NATted addresses (10.0.0.130/134/135) - so NATting is working ok.
> But when the client tries to access the application I get...
> 3725_Backup#
> 17:42:35: IP: s=10.0.18.35 (Dialer4), d=10.0.0.135, len 48, rcvd 2
> 17:42:35: TCP src=2739, dst=3200, seq=3212891754, ack=0, win=32768
> SYN
>
> 17:42:35: IP: s=10.0.0.135 (local), d=10.0.18.35 (Dialer4), len 40,
> sending
> 17:42:35: TCP src=3200, dst=2739, seq=0, ack=3212891755, win=0 ACK
> RST
>
> 17:42:35: IP: s=10.0.18.35 (Dialer4), d=10.0.0.135, len 48, rcvd 2
> 17:42:35: TCP src=2739, dst=3200, seq=3212891754, ack=0, win=32768
> SYN
>
> 17:42:35: IP: s=10.0.0.135 (local), d=10.0.18.35 (Dialer4), len 40,
> sending
> 17:42:35: TCP src=3200, dst=2739, seq=0, ack=3212891755, win=0 ACK
> RST
>
***************************************************************************************
> Is it still the case that the app isn't listening on port 3200?
>
>
> > It's showing that the source IP 10.10.10.130 is attempting to connect to
> > 10.10.10.135 on port 3200 (The SYN packet). The server then responds with a
> > RST packet, which indicates that no application is listening on port 3200.
> > The source and destination are all inside networks (all on the 10.10.10.x
> > network), so no NATing is being done
>
>
>
> > > Users cannot connect to the applications but can PING the app servers
> > > (10.10.10.130/134/135) - these are NATted - users see them as
> > > 192.168.0.42/37/35. Any suggestions on what the router debug output is
> > > saying?

OK it is sorted... I had the Dialer interface on the router set up
without "ip nat outside". It is unusual though, as once the router has
the static NATs configured the router responds to the remote PING
requests even if the 3 server are plugged out of the network...

Similar ThreadsPosted
PIX + tcp debug November 11, 2004, 8:36 pm
Pix debug, get more out of it June 15, 2005, 1:41 pm
IOS Debug August 15, 2005, 3:39 am
debug fixup udp November 30, 2004, 9:10 am
Debug QoS cos & dscp September 13, 2005, 11:50 pm
debug packets on PIX with 7.0 October 10, 2005, 9:19 pm
Cisco Pix debug help March 19, 2006, 5:37 am
debug ip packet September 1, 2006, 7:56 pm
PIX 501 vpdn debug help December 11, 2006, 10:15 pm
what does debug outputs mean ? March 22, 2007, 5:53 pm

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map