Network problem when idle

Question

Hi!
I don´t know if I´m in the right topic.
My english is not that good, but I´ll do my best to explain my problem.
I work with Forms 6. So I have at C:\orant the oci*.dll of this version.
I also use sql tools (http://www.sqltools.net/) to run script in my database.
I like Oracle SQL Developer, but it is too slow and heavy. SQL Tools is light and fast.
Both with Forms Builder, as with SQL Tools, if I let they connected to the database, but idle for a while (lets say half hour).
My network connection goes down.
I´m not talking about database connection. I´m talking about the network connection, as if the network cable was removed.
First, i thought it could be the SQL Tools. So I stoped to use for a week, but the problem did not stop. Then I thought that could be the forms builder. I did the same test (a week), but the problem remains.
I tried to download and use for sql tools the oci version 11. Did not work.
I don´t think it is a server configuration, because if it was, just the database connection should be broken.
I think it´s something with oracle libs (dll).
I made sure that it´s nothing but the Forms Builder or SQL Tools that could cause the problem.
I´m sure that is something that it´s common for both of them, that´s why i tried to use the most recent oci version for sql tools.
When network is down. If i close one of them, the network comes back alive.
Does anyone has any idea about what it could be?

Answer 1

Id definitely troubleshoot to see whats going on with the nic at the point it loses connection, I mean you know its one of the programs right, but narrow it down to the exact call. run windump, output to log, recreate issue, stop log.
Download windump
http://www.winpcap.org/windump/install/default.htm
windump also needs winpcap, download from here
http://www.winpcap.org/default.htm
Create a batch file called dumptest.bat with the following line which captures all network traffic to/from the host
windump -A -a -vv -s 0 host <your client name>
then in dos>
dumptest > mytest.log
and let it run
generate the issue, when network connectivity lost, CTRL + C the command line and edit mytest.log and check whats going on when it kills. might be something there.