asked on

TCP Reset-I Cisco Firewall

Remote user connecting with Terminal Server to map a drive on the server has been able to do this for many months. Now we are receiving a syslog message as follows:
Teardown TCP connection 3508033 faddr 124.24.126.36/3767 gaddr 165.123.12.161/445 laddr 192.168.1.3/445 duration 0:00:00 bytes 0 (TCP Reset-I)

This occurs even though a Terminal server session runs from the same machine at the same time that port 445 is rejected by the server (if I understand the message correctly).

User obviously receives a message about network address not found. This is a server running Win2K Server and the user running Win XP.

Thanks for your help.

td_miles

What version IOS are you running (use "show version") ?

Have there been any changes to cause this ? Have you upgraded the IOS ? Have you upgraded Terminal Server ? Have you changed OS on the PC ?

If it was working happily, then something must have changed to cause it not to work.

Les Moore

Has user installed cable router that is now doing DHCP and NAT at home?
Is their local LAN now 192.168.1.x
Is the Term server IP 192.168.1.3 ?

DEllis3

ASKER

nicpix up 187 days 19 hours

Hardware: SE440BX2, 128 MB RAM, CPU Pentium II 350 MHz
Flash i28F640J5 @ 0x300, 16MB
BIOS Flash AT29C257 @ 0xfffd8000, 32KB

0: ethernet0: address is 00d0.b76b.7ee4, irq 11
1: ethernet1: address is 00d0.b73f.e6c9, irq 15
2: ethernet2: address is 00d0.b7a0.9987, irq 10

No change to the firewall.
No change to the OS other than MS patches.
No change to the PC OS (XP) other than MS patches.
Term server IP address on the DMZ is 192.168.1.3. External address is as shown in the quesion.

I will have to check with the user when she arrives this morning as to her local IP address and NAT. She is using cable modemwith a fixed external ip address. I will post the answer to this last question, but it may be tomorrow as she lives too far to return home and back today.

Thanks for your help.

DEllis3

ASKER

User at home is using cable modem and wireless at home. Her IP address at home 192.168.1.102, with default gateway 192.168.1.1

ASKER CERTIFIED SOLUTION

Les Moore

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

DEllis3

ASKER

We will try that, but I don't think it is the answer: The external address is the one that she sends to. We are not using a VPN but rather Terminal Server. The external address is 165.123.12.161. She doesn't see the 192.168.1.x address. Also, she is able to connect to the same IP address using Terminal Server port 3389. It is only the port 445 for mapping a drive that will not hold the connection.

Thanks for your help. I will try to have her change her local gateway and see what happens.

Tim Holman

No comment has been added to this question in more than 21 days, so it is now classified as abandoned..
I will leave the following recommendation for this question in the Cleanup topic area:

--> Accept: lrmoore

Any objections should be posted here in the next 4 days. After that time, the question will be closed.

tim_holman
EE Cleanup Volunteer