Enterprise Manager refusing to see server instance.

[meekon5]

After a recent re-build of my PC I have re-installed SQL2k. We are running three development machines (including mine) in the office, and a smallish dedicated SQL server on the network. I have installed the Personal Editon of SQL2k and anything the Development Edition adds.

The Enterprise manager see's all the development instances but refuses to see the network server. I have uninstalled, re-installed, re-configured in every manner possible, including using '.iss' files from both my original machine, and the server, and one of the other developers machines.

But still the main database refuses to connect (specified name, domain\name, IP, everything).

Has anyone any ideas.

From a man with a lot less hair than he started the month with.

 

[Niv3k]

I just got done facing a similar problem (5 minutes ago!) Instead of typing the server name in the enterprise manager, I used the (SQL) servers IP Address. I think it's a problem with the w2k DNS not finding my server by name, but I have to look into that further. Let me know if this helps!

 

[meekon5]

OK five days of doing everything to everything without any joy. Install it, uninstall it, re-install it. Spent most of yesterday digging through '.iss' files, logs for this, logs for that, and anything I could find.

Adjusted all the tcp/ip ports to the same thing across the network. As I did this the other machines stopped seeing our main development server (cue small developer weeping in corner of office). But two of the machines continued to see each other.

Huge amount of winsock errors in main servers logs. Adjusted one of the remaining machines to use winsock proxy as with my own and main server. Pop, it dissapears from the loop.

So remove all winsock from all the machines and there they are back in the loop (cue 1812 style cannons and fire works).

Problem solved. Finally.