Netware/SQL Question - A shot in the dark...

[SpyderMan1234]

This probably isn't the best forum to ask such a question but...

This is the setup. It's simple. I have a Windows 2003 server running SQL Server 2000. I have a Netware 6.5 server that is running software which accesses the SQL database on the Windows server. The software uses an .ini file which contains the server name housing SQL Server. TCP/IP and NWLink IPX protocols are installed.

The problem is that the software housed on the Netware server will often connect to the Windows 2003 server beautifully and run great, but after a varying amount of time, performance drops to nearly nothing and the connection all but dies. Then after another varying amount of time, the connection is back up again and running fine. The connection yo-yos like this all day. Up and down and up and down and I cannot figure out why. This happens at all times of the day, so I know it's nothing to do with increased network traffic. If it was a problem as simple as a missing protocol or incorrect setting, I can't help but think it wouldn't make a connection to begin with.

I might also add that the Netware server was just recently upgraded from 6 to 6.5. Firmware and Java was also updated at this time.

Has anyone encountered something like this before? Any help would be appreciated.

Thank you.

 

[stravis]

I would try taking IPX out of the loop and only use TCP/IP for communication with SQL. Once this is done I would make sure that DNS is working properly between the two networks and not providing a slow response time when you perform a ping request from the Novell side to the SQL Server. If possible change the INI file to just use the static ip address of the SQL Server and see if that solves the problem. It is also possible that you could be dealing with lost packets but I would guess the problem is more related to name resolution issues.

stravis