Tnsping

[awearBren]

Hi, I guess this could be in the wrong forum but I looked, I thought about it and this seemed as good as any. apologies if I irk anyone.

I have a database called db1 on a server S1.
S1 was recently (2 months ago) given a new IP: 129.*.*.* changed to 192.*.*.*
users connect to db1 via two applicaions A1 and A2 (Mercatus and 1 inhouse app). I always thought that A1 & A2 both used a tnsnames file to connect to the database.

I have a user who gets a tnstime out error when launching the inhouse A2 but A1 works no problem.

From his laptop when I tnsping db1 I get a timeout. tnsping is looking for the database on the old & wrong ip address for S1.

When I ping the hostname of S1 from the laptop it resolves to the new & correct address.

I don't understand where tnsping is getting the old ip info from.

I have searched the registry for the old ip - nothing found.
I have been through all host & lmhost files - nothing found
I have specified ip instead of host in the tnsnames file - no change
i have checked the routing table - nothing found.
I have searched for other tnsnames files - nothing found
I have checked the sqlnet.ora file and all looks good.
I flushed the dns - no change.

Has anyone any ideas why tnsping might be routing to the old ip?

thanks for reading and I hope it makes sense.

[johnwill]

Well, this makes no sense to me, but one thing stands out.

Even though you obfuscated the IP addresses, 129.x.x.x is a public IP address, and 192.x.x.x is a private IP address. That indicates that this server was recently moved to be behind a router or gateway, which is likely the issue when you are trying to connect to it.