Problem after installing .Net framework on SQL server

[MustangPriMe]

We run an Access 2000 ADP internally which uses a SQL Server 2000 backend.
The SQL Server has today had .Net framework 1.1 installed on it as part of the Windows Software Update Services (WSUS) requirements. Since the update, clients using Windows 2000 have been unable to access the database - SQL server apperently rejecting any connections to it.
Windows XP users aren't experiencing any problems, and if one of the Windows 2000 users logs onto a Windows XP machine, they are then OK.
Does anyone know the cause, and more importantly the fix(!) for this problem?
Thanks,
Paul

 

[danvlas]

Named pipes or TCP/IP?

If you change (in the client) the server name with the server IP it might just work. I'm not sure, but it's worth a try.


HTH


Daniel Vlas
Systems Consultant

http://www.geocities.com/danvlas/AutoMail.html

 

[MustangPriMe]

Got it working again now!

Using the IP address instead of the server name had no effect, but checking whether Named pipes or TCP/IP appeared in the SQL server network configuration made me realise that we used to have both enabled, and only TCP/IP was now showing. Adding Named Pipes back in has the Windows 2000 machines happy once again.
Not sure if it was the .Net framework install that knocked it out, or whether some else had done it, and it only took effect at the point of reboot.
Any idea why the Windows XP machines were fine (presumably using TCP/IP) and the Windows 2000 machines were not (presumably only trying to use Named Pipes), when all machines were using exactly the same Access .ADP?