ODBC ora error installing Oracle

Make sure the sqlnet.ora file is also the same as working machines.

The error stats there isn't a listener running on the HOST you are trying to connect to.

Make sure you are going to the server you think you are going to.  Maybe a local hosts file is pointing to a wrong machine?

It's working on all his other computers.  Hes using a known good ora file.

I understand that is what you said from the first time you said it.

The fact that one machine doesn't work implies something about this machine is different.  There are only a few things it can be.

When people new to Oracle mention a "ora" file, them main one they are talking about is the tnsnames.ora file.  They forget about the sqlnet.ora file that can have some settings that make the tnsnames.ora file "work".

I agree with what slightwv said.  One other possibility is multiple "Oracle_homes", that is: multiple, separate installations of Oracle client software on this "problem" PC.  If that is true, you may be looking at a tnsnames.ora file other than the one that the Microsoft ODBC driver is actually using.

Open RegEdit then check: Hkey-Local_machine, Software, Oracle and see if there is just one Oracle_home, or multiples.

User states back, On the last reinstall, I deleted the registry entries for all the previous homes.  Please give me a more specific change or entry to check.

When you "deleted the registry entries for all the previous homes" did you actually uninstall or physically delete the corresponding software?  Or, is that software still installed on that hard drive?  If that software is still physically on the hard drive, even if the Oracle-related registry entries have been deleted, Microsoft software may still be trying to use it.

Finding that software on disk could be a challenge!  Depending on who did the Oracle software installation, the top-level directory for it could be named anything, and it could be in any directory of the C:\drive (or any other drive on the PC, if it has multiple disks).

stand by, checking that

that's a long "stand by"
what daily rate do you pay for "standing by" ?

Oh, the enduser said he moved the laptop to a diff domain and that "fixed it".  How that did it I have no idea

Off the top of my head it might have been the sqlnet.ora parameter NAMES.DEFAULT_DOMAIN.

I suggested a reimage b/c that's what Ive always done when stuck with this issue.  Is that not the easiest way?

>>Is that not the easiest way?

Sure.  You can always tear down and rebuild your entire house because a toilet flapper needs replacing but it seems like over-kill.

Even if a reimage occurs, most people copy config files like the .ora files around so the reimage likely won't magically fix this.

Something between a working machine and non-working machine is different.  If a working machine is in the domain and the non-working was also in the domain, then I'm not sure how pulling it out magically worked.

It would be hard to diagnose if you didn't have hands-on access.

- so probably easier to reimage....

All I know is that it worked again from the tech.  Not sure what else to say

Thank you everyone.  Frustrating issues....