Re: Win2K workstation ODBC cannot find new SQL Server

When you say "can see" I think you mean that the SQL Server name populates in the drop down list, and that the listing is the problem that you are trying to solve.
In SQL Server 2000, the list is populated by using UDP (User Datagram Protocol). My guess is that your problem is based on your TCP subnets, and that some routers are not forwarding UDP packets. This a common configuration to reduce network noise. However it's not likely a change, so if you Windows 2003 is sitting next to your other servers (and is on the same subnet), then this isn't making sense.
Also, you should be able to connect, even if the UDP broadcasts are blocked. But you would have to provide a port number if the SQL Server is a named instance. You can test all this, by going to a workstation that does not "see" the SQL Server, and try to connect using the IP address and TCP port number, in the format xxx.xxx.xxx.xxx,1433. Port 1433 is the default, but the SQL Server error log will tell you what port the SQL Server is really listening on.
If you are using named pipes, it's the pipe name that is passed to the client using UDP.
Hope this helps.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

<mcbill20@xxxxxxxxx> wrote in message news:6a4b2d02-e59f-4f01-b1fa-6771ae191639@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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: SBS 2003 Unable to connect to database STS_Config
    ... Uninstall the SQL server from the SBS 2k3 server from add/remove programs ... Uninstall Microsoft SQL Server Desktop Engine (SHAREPOINT) ... If AV software install any extra IIS virtual directory, ...
    (microsoft.public.windows.server.sbs)
  • Re: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 C
    ... I also checked the individual patch levels for the .NET drivers, SQL Server ... The SQL Server is fully patched, however Windows Update reported that the OS ... Lock pages in memory -- I guess you might have taken care of it as well. ...
    (microsoft.public.sqlserver.clustering)
  • RE: migrating from wmsde to sql server
    ... Click Start, point to All Programs\Microsoft SQL Server, and then click ... then click New SQL Server Registration. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 Unable to connect to database STS_Config
    ... Uninstall the SQL server from the SBS 2k3 server from add/remove programs ... Uninstall Microsoft SQL Server Desktop Engine (SHAREPOINT) ... If AV software install any extra IIS virtual directory, ...
    (microsoft.public.windows.server.sbs)
  • Re: Is There a Client/Server Version of Access ?
    ... Are all the workstations on the same LAN? ... There's also the newer SQL Server Express, ... If you upgrade a PC with Office already ...
    (comp.databases.ms-access)
Loading