From: Blaine S. <bla...@ad...> - 2007-05-18 23:10:55
|
Bayless Kirtley wrote: > Blaine, > > It turns out that the problem was not exactly as I described yesterday. > Having a little more patience with the thing today (or maybe I was just > distracted for a minute) it actually did connect but was extremely slow > in doing so. For example, to first establish a JDBC Connection took > a full minute. Then the program asks for a password and verifying it > actually took a little longer than a minute. I was then able to query an > entire relatively small table and present it which took about 15 seconds. > All of these operations normally are essentially instantaneous. > > Telnet did not work to either local or remote computer but someone > suggested that Windows disables the telnet port by default. Telnetting to port 9001 has absolutely nothing to do with telnet port 23, on client or server side. > I was also > unable to connect to the local database using the IP address. I tried > disabling the firewall and antivirus programs, still with no success. As > a last resort, I disabled the DHCP server in the router and hard coded > IP addresses for both computers. After that, I could reenable the firewall > and antivirus and all works well. It appears that the problem lies in the > DHCP server for some reason. For my application, it is probably best > to leave them fixed anyway. > > So, problem solved. Thanks very much for your help. It did certainly > get me thinking along the right lines to solve the problem. > You're welcome. > Bayless > > |