Re: SQLNet won't work after network changes

Kenneth,

A few things to check. First look at the clients TNSNAMES.ORA file. This is the configuration for SQLnet. Check to see that the tcp/ip address was not hardcoded. If so change the ip address to corespond with the new address on the server. You can also use the SQLnet Easy Config tool to delete the old alias and create a new one. Some people find this easier, though editing the file is my preference.

On the NT side, check the following:

1. can you ping the server by name? If not, check the following files: c:\winnt\system32\drivers\etc\lmhosts. c:\winnt\system32\drivers\etc\hosts. These files usually contain the ip address and the machine name. If the files are present and the addresses are incorrect, modify them, save the changes and type the following: NBTSTAT -R The -R must in uppercase.
2. can you ping the server by ip address? If you can't ping by the actual address, you something wrong with your IP configuration on one or both of the machines in question. On each machine ensure the following: - The correct IP address is used - The correct subnect mask is used - The correct gateway is used - The dns entries are correct and reachable - If using WINS, ensure that it is configured correctly. - if using DHCP, get the LAN administrator involved.

Hope this helps.
m

"Kenneth Herskedal" <kenneth.herskedal_at_NOSPAMtrafsys.no> wrote in message news:81j0e7$8m7$1_at_oslo-nntp.eunet.no...
> I have an Oracle 7.3 server on Windows NT workstation and SQLNet on
another
> windows NT. After changing our IP addresses, SQLNet is not connecting to
the
> Oracle server.
>
> How can I fix this? Do I need to reinstall Oracle?
>
> Regards
> Kenneth Herskedal
> www.trafsys.no
>
>
>
Received on Thu Nov 25 1999 - 11:50:41 CST