September 5, 2002 at 8:01 am
We keep running into instances where a particular machine will be able to connect to another, but others won't. This is one example from a tester:
I have installed FWM5 [our app] - March 6 release build on four computers:
ls-test2vm, running Win 2000
ls-burgett-old, running Win 2000
ls-lastufka-old, running Win 98
ls-test-1, running Win 98
I've tried to open an FW database residing on ls-test2vm from each of the other three (via [the app])
ls-burgett-old is the only one that is unable to do it. When I click on the computer name, ls-test2vm, it searches for a while and then displays the message,
"Ls-test2vm\FW does not have any data" (at this point the message is cut off because of the size of the control it is in - you can actually see only half of the last 'a' in data)
Steve
Steve Miller
September 5, 2002 at 9:21 am
Here's another example. I'm trying to connect to another developer machine that I know is running. I open Enterprise Manager to Register a New Connection. I get an error telling me the connection couldn't be established. Then:
Reason: SQL Server does not exist or access denied.
ConnectionOpen(Open())..
Steve Miller
September 6, 2002 at 2:07 am
What kind of authentication mode are you running? SQL Server or Windows?
In the latter case, the login trying to connect, is the one the application is running in. So it has to be known on the SQL Server, and has to have access to the database.
This can also be due to the 'network' library you are using to connect. Maybe you can check that. And finally, you should be at least be able to ping the server machine. Maybe there's a DNS problem somewhere?
September 6, 2002 at 9:07 am
Both machines are running mixed mode authentication. I've switched the authentication on both, using all 4 combinations of Windows and mixed mode, and it doesn't seem to make a difference.
I am able to connect to another development machine with no problem whatsoever. It has apparently the same setup as the one I can't connect to. I have yet to figure out the difference.
I can use Windows Explorer and able to see shared directories on the computer giving me trouble. So that doesn't appear to be the problem. On the other hand, I get an access error when I try to look in one directory that's supposed to be shared. That just started happening, and don't know if that's a clue.
What should I check to make sure it's not a network problem?
We are working with named instances. When I went into Enterprise Manager, I saw he had a default instance. I deleted the registration for that. The thing that disturbs me is that I can't find the default instance with Add/Remove programs. I don't know if that's related, either.
I have more mysteries than answers, it seems.
Steve
Steve Miller
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply