I noticed that other thread on the SQL error was closed.

You should really try to resolve the naming issue. Setting the IP address instead of a hostname is a bad policy.
It is like hardcoded passwords in batch scripts i.e a complete nightmare to maintain if things change in the future.

Get your network admin involved and/or NT admin to work out what the name resolution problem is.

I posted this warning because i have been thru the experience, you don't want to go there

Have Fun