Win2K workstation ODBC cannot find new SQL Server

We have a network consisting of some Win2K workstations that connect
to two machines running SQL Server 2000 on Windows Server 2000.
Everything has been running OK for quite a while. I just bought a new
WIN 2003 server to replace the two Win2K servers. The new server is
also running SQL Server 2000. My problem is that some of the
workstations cannot see the new server but a few can. When I create a
new ODBC connection, the pull-down list of servers varies from machine
to machine. Some can see all, others can see a few an some can only
see one. I can't seem to find what the configuration difference is.
Here is our configuration:

* SQL1 - Win2K Server running SQL Server 2000 (Part of Win2K AD
domain)
* SQL2 - Win2K Server running SQL Server 2000 (Part of Win2k AD
domain)
* SQL3 - Win2003 Server running SQL Server 2000 (Part of NT4 domain)

* WS1 - Win2K workstation; connects to SQL2 but can see all servers
(Part of Win2K AD domain)
* WS2 - Win2K workstation; connects to SQL2 and can see ONLY SQL2
(part of Win2K AD domain)
* WS3 - Win2K workstation; connects to SQL1 and can see all but SQL3
(part of Win2K AD domain)
* WS4 - Win2K workstation; connects to SQL1 and can see SQL1 and SQL2
(part of Win2K AD domain)
* WS5 - Win2K workstation; connects to SQL3 and can see all machines
in both domains that have SQL server running (part of NT4 domain)

At this point I guess I should clarify why we have such a bizarre
configuration. Our main network has been an NT4 domain for years. A
year ago we were able to replace our main servers with Win2003 servers
but still needed to stay an NT4 domain so there is an NT4 BDC. This
was due to some issues with some really old systems that could not be
part of an AD domain. We think we have a solution but for the near
future the domain will stay NT4 even though most of the servers are
Win2003 and most of the workstations are XP.

The machines listed above were purchased to implement a nerw building
security system (door locks, gate openers, video cameras, etc. They
were originally set up with Win2K server and Win2K workstations. The
system was aging so we got the new SQL3 Win 2003 server to replace the
SQL1 and SQL2 servers. In addition, we now have an enterprise backup
solution that requires the security system to be part of the same
domain. That's why the new SQL3 and new test workstation are part of
the NT4 domain. When we do the cutover, the Win2K workstations will be
switched over to the NT4 domain like the test workstation is.

Within six months we will be getting rid of the NT4 BDC and buying a
Win 2003 server to be the domain controller.

For now I just need to find out how to make all the workstations be
able to see all the SQL Server machines. I don't think the domain has
anything to do with it as I am able to see all SQL server machines in
both domains on two of the workstations.

Can anyone tell me what I should look at to be able to see all? Also,
I tried just typing in the new server name on the workstations that
cannot see the new server but the error said the machine was not
found.

Thanks,
Bill
.

Relevant Pages

  • Re: Clustering
    ... You mentioned WS's above and I assume that means WorkStations. ... Every fifth machine is a boot server. ... Each boot server serves four other machines. ... files were stored on the disk server. ...
    (comp.os.vms)
  • Re: SBS 2003 Misconfigured?
    ... up one of the workstations via remote web connection, ... but why are you looking at the server rather than the workstation? ... (this will show you the DHCP lease info). ... The Netgear, or whatever you use as your gateway to get out to the Internet. ...
    (microsoft.public.windows.server.sbs)
  • Re: Q329873, problems with DCs machine account, need help!
    ... Your best path is to disjoin and then rejoin the workstations to the domain. ... The NETDOM command would do most of the same functions and you may as well ... > couple Mac OSX 10.3 machines to participate in AD. ... > server, so that's obviously not good enough. ...
    (microsoft.public.win2000.active_directory)
  • Re: How vulnerable are Windows servers if you can run e.g. Knoppix on one of the workstations?
    ... > I administer a number of small Win2k domains. ... > or map my way to drives on the Win2k Server and read server files as ... This is a horse of a different color, as you're wondering about a network ... > have physical access to some of her workstations and LAN ports. ...
    (comp.os.linux.security)
  • RE: Windows Universal Storage Server 2003 quits working
    ... day) stops communicating with the domain controllers. ... but no other machines are affected (either servers or ... Local workstations can access files, ... The Server is a Dell NX1950 with a MD3000 Raid Enclosure. ...
    (microsoft.public.windows.server.general)