Re: Oracle Discoverer 3.1 won't connect on Windows XP

Kydd wrote:
> Charles Hooper wrote:
> > Check the Advanced TCP/IP settings on the computer's network card.
> > Specifically, look at the DNS tab in the box titled "DNS suffix for
> > this connection's addresses in DNS". Compare that with the other
> > computers that are working correctly.
>
> Exactly the same.
>
> > Install Wireshark/Ethereal on the client computer to see the packets
> > that are being passed to the network. Install Filemon to determine the
> > files that are being accessed on the client computer. Compare those
> > logs with logs from another computer that is working properly.
>
> Started with Filemon. One strange difference is that on the working
> computer, when I try to make the connection I see that
> \orant\NET80\NLTUS.MSB is being accessed. On the bad computer, I see
> \orant\NET80\TNSUS.MSB as well as \orant\RDBMS\ORAUS.MSB being read in
> addition to NLTUS.MSB.

Good start.

TNSUS.MSB is the SQL*Net message file (Metalink note 309632.1) ORAUS.MSB has descriptions of RDBMS error messages (Metalink note 1072632.6)

Using FileMon, do you see the computer accessing the TNSNAMES.ORA, SQLNET.ORA, or PROTOCOL.ORA files on the non-functional and functional computers?

At a command prompt on a computer that works, and one that does not, type SET and press enter. Do you see an environment variable named LOCAL_DOMAIN or something similar (sorry, can't recall the exact name)?  You can see the effects of this using Wireshark/Ethereal.

Charles Hooper
PC Support Specialist
K&M Machine-Fabricating, Inc. Received on Mon Nov 06 2006 - 19:58:49 CST