Re: Who is my i5 trying to connect to, and why?

are you running any exit programs?
If on a dsl (like me), my door gets knocked on every few minutes.
Mostly windows and unix/linux scripts to the web server, and ftp every so often. Turn on logging in Apache & you will see the attempts.
Same w/ftp, telnet, etc exit pgms.
jim franz
----- Original Message ----- From: "Bradley V. Stone" <bvstone@xxxxxxxxxxxx>
To: <MIDRANGE-L@xxxxxxxxxxxx>
Sent: Sunday, December 23, 2007 9:00 AM
Subject: Who is my i5 trying to connect to, and why?

I was checking out the QSYSOPR messages today and noticed a few of these:

TCP/IP connection to remote system 192.168.1.1 closed, reason code 1.
TCP/IP connection to remote system 89.122.213.8 closed, reason code 2.
TCP/IP connection to remote system 89.122.213.8 closed, reason code 2.
TCP/IP connection to remote system 72.166.155.41 closed, reason code 2.
TCP/IP connection to remote system 72.166.155.41 closed, reason code 2.
TCP/IP connection to remote system 72.166.155.41 closed, reason code 2.
TCP/IP connection to remote system 67.82.120.36 closed, reason code 2.
TCP/IP connection to remote system 70.145.58.103 closed, reason code 1.

Now, I'm pretty sure I don't have anything that would go out to connect to a
remote system (like GETURI). I do have apache running my web page.

The funny thing is, the first one in the list is my router. The other ones,
I have no idea who they are. I looked them up in DNSStuff but nothing
"clicked".

Any ideas?

Brad

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.