May 14, 2008 at 7:20 am
I am running 5 different vb software from 10 client machines to access various SQL 2005 DBs on the server. All software on all machines was running fine. The ethernet LAN cable on one of the machines got unplugged while in operation.
From then, none of the software on this particular client machine can access the SQL Server. The 'dbconnection.open' command fails and an error message 'SQL Server does not exist or Access Denied' is returned.
The same software continues to run fine from all other client machines. All software on all machines uses the same connection string i.e. no change in user name & password.
I tried changing the IP address of the machine, restarting it, changing the workgroup but without success. I then added a new login to the SQL Server with full rights (the same rights as the user in the old connection string). The problem repeats with this new login as well.
It seems that this is a machine specific problem somehow related to the unplugging of the LAN cable.
Could somebody help?
May 14, 2008 at 8:00 am
What on earth made you think this is a security problem?
May 14, 2008 at 8:05 pm
Can you ping the server from the machine by name and IP?
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
May 14, 2008 at 10:55 pm
Yes, I can successfully ping the server from the client machine by IP, haven't tried it with the name.
I can also access the server through Windows Explorer.
May 19, 2008 at 10:11 pm
I have identified the problem. It was an instance of MSDE on the client machine (with a different server name and different login). Connectivity to SQL 2005 was not possible even with the MSDE instance stopped.
I had to uninstall the instance of MSDE from the client machine. Connectivity was restored immediately after the uninstall.
Could anybody shed some light as to why there is a conflict between two different versions of SQL (one local and one on the network)?
May 20, 2008 at 2:04 am
vvikrant (5/19/2008)
Could anybody shed some light as to why there is a conflict between two different versions of SQL (one local and one on the network)?
There is no conflict. You haven't identified the problem. Sorry. Anything else I post would be total conjecture;
Perhaps you had aliases configured, who knows?
May 20, 2008 at 6:28 am
No aliases were configured.
I might not have hit the root of the problem, but it is somehow related to the coexistence of MSDE + SQL 2005.
After uninstalling, I setup MSDE again and the problem repeated!
May 22, 2008 at 6:12 pm
try to fix IIS, and change ur IP, reinstall network driver..
if u hadnt find the reason stop wasting time and reinstall windows.
..>>..
MobashA
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply