DNS on Windows 2000 Server & Windows 2003 Server

We are having numerous issues with disconnects after upgrading our PDC to a
Windows 2003 environment. We have several Windows 2000 Servers running SQL
Databases that users connect to. The issue as described in my post found
under client connections is that the network connection is good but we are
getting RPC errors & "The object invoked disconnected message". Our Windows
2003 Server is running DNS. It was suggested by a developer to install the
DNS windows components found under networking on all other servers.
Will this work? Or will we cause DNS issues as a result of it?Hi
Installing DNS on every server will not solve your problem.
DNS Service in Windows 2003 is reliable so there is not need to setup many
of them.
What the the exact error number and error messages you are getting? Are any
errors logged in the SQL Event Log?
Regards
Mike
"Cstewart" wrote:
> We are having numerous issues with disconnects after upgrading our PDC to a
> Windows 2003 environment. We have several Windows 2000 Servers running SQL
> Databases that users connect to. The issue as described in my post found
> under client connections is that the network connection is good but we are
> getting RPC errors & "The object invoked disconnected message". Our Windows
> 2003 Server is running DNS. It was suggested by a developer to install the
> DNS windows components found under networking on all other servers.
> Will this work? Or will we cause DNS issues as a result of it?
>|||The errors that are appearing on the client side are as follows:
"The object invoked has disconnected from its clients" and/or "RPC server
unavailable"
Here is more information that I posted previously:
We have recently upgraded our main server from NT4 to Active Directory
(Windows 2003 Server). Our SQL Database is 2000 and is running on a Windows
2000 Server Box. We use com+ components to connect to our database. Since
the change on our PDC to 2003 Server AD, we have had several errors such as
"The object invoked has disconnected from its clients" as well as RPC Server
Unavailable. This occurs even when the user is consistently active. We have
applied latest Windows Service Pack to clients xp sp2 and to the windows 2000
server box. If you reboot the server and or/stop services (Com+ and Dcom) on
the client end, they can get back in. You can browse to the machine no
problem through exporer - right to the database. Issue is only in SQL 2000.
Any assistance would be greatly appreciated. Note: I have also checked
using netstat -a to see if all ports were being used and that is not the
case. This is happening on more than one users connection and I am certain
it is not network based - ping 100%, can browse, two locations within
building etc.
Note: Problems occur regardless if client is at Service Pack 2 or 1.
I have checked the event log on the server and nothing reported. I have
checked the error logs in the SQL directory of Logs and nothing reported.
Any suggestion as to what other logs (if any) to look at?
Thank you for your assistance.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Installing DNS on every server will not solve your problem.
> DNS Service in Windows 2003 is reliable so there is not need to setup many
> of them.
> What the the exact error number and error messages you are getting? Are any
> errors logged in the SQL Event Log?
> Regards
> Mike
> "Cstewart" wrote:
> > We are having numerous issues with disconnects after upgrading our PDC to a
> > Windows 2003 environment. We have several Windows 2000 Servers running SQL
> > Databases that users connect to. The issue as described in my post found
> > under client connections is that the network connection is good but we are
> > getting RPC errors & "The object invoked disconnected message". Our Windows
> > 2003 Server is running DNS. It was suggested by a developer to install the
> > DNS windows components found under networking on all other servers.
> >
> > Will this work? Or will we cause DNS issues as a result of it?
> >
> >