Cluster Node Communications

I just rebuilt a 2 node W2k/SQL2k cluster that resides in
a NT4 domain. The cluster itself seems to be working
fine, the website that runs off of the virtual SQL server
is running fine.
However, both nodes in the cluster are not able to
communicate with other machines in my 2 other
trusted/trusting domains. My other 2 domains are W2k
based domains. Prior to the rebuild there were no
communication problems accross domains.
If I try to browse to the nodes in Windows Explorer I get
the message "No logon servers currently available to
service your request" and if I try to logon to one of the
nodes at the console using my user name and domain, it
says the domain is unavailable.
Any assistance would be greatly appreciated.
Patrick G.
You can check a few things.
1. Make sure your domain trust(s) are still in place and functioning correctly. If you don't have the W2K support tools installed (ie in a prod environment), run dsa.msc and check that you can browse the remote domain and list groups and users in the rem
ote domain (eg attempt to add a global group from the remote domain to a local domain group - you can do this with committing the change).
2. Make sure the account you are using has a valid SQL Server login on the remote SQL Server (or your account is in the builtin admins group on the remote server - if the other domain are willing to trust you with local admins on the remote server or the
remote domain).
Are both domains in W2K native or do you have W2K and W2K3 forests in the mix?

Client-side printing from NT with SP2

We have installed SP2 and client-side printing from the browser is working
fine for our users on XP/IE6. However, we have some users with NT4/IE6 on
their machines. They are able to view reports, but when they click the Print
icon, nothing happens (no error, no prompt, nothing).
Is the ActiveX control for printing included in SP2 supported for clients
using NT4?Ah, crap...
Same here. That's a show stopper!!!
"MELMEL" <MELMEL@.discussions.microsoft.com> wrote in message
news:DDFF5917-13B1-44D2-8138-EB44818B579D@.microsoft.com...
> We have installed SP2 and client-side printing from the browser is working
> fine for our users on XP/IE6. However, we have some users with NT4/IE6 on
> their machines. They are able to view reports, but when they click the
Print
> icon, nothing happens (no error, no prompt, nothing).
> Is the ActiveX control for printing included in SP2 supported for clients
> using NT4?|||When a product is given end of lifetime that really does mean that. It might
work or it might not but MS spends 0 time testing with it. It is not part of
their test suite. Extended support expired almost a year ago. I assume the
users can continute to export to PDF and print that way.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Fredrick Bartlett" <rick_bartlett@.WeDoNET.net> wrote in message
news:Os2pNyPUFHA.3184@.TK2MSFTNGP15.phx.gbl...
> Ah, crap...
> Same here. That's a show stopper!!!
> "MELMEL" <MELMEL@.discussions.microsoft.com> wrote in message
> news:DDFF5917-13B1-44D2-8138-EB44818B579D@.microsoft.com...
> > We have installed SP2 and client-side printing from the browser is
working
> > fine for our users on XP/IE6. However, we have some users with NT4/IE6
on
> > their machines. They are able to view reports, but when they click the
> Print
> > icon, nothing happens (no error, no prompt, nothing).
> >
> > Is the ActiveX control for printing included in SP2 supported for
clients
> > using NT4?
>|||We didn't test on NT4. We tested on XP, Win 2003, Win 2000, Win 98 and
WinME.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:O8w1aIYUFHA.580@.TK2MSFTNGP15.phx.gbl...
> When a product is given end of lifetime that really does mean that. It
> might
> work or it might not but MS spends 0 time testing with it. It is not part
> of
> their test suite. Extended support expired almost a year ago. I assume the
> users can continute to export to PDF and print that way.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Fredrick Bartlett" <rick_bartlett@.WeDoNET.net> wrote in message
> news:Os2pNyPUFHA.3184@.TK2MSFTNGP15.phx.gbl...
>> Ah, crap...
>> Same here. That's a show stopper!!!
>> "MELMEL" <MELMEL@.discussions.microsoft.com> wrote in message
>> news:DDFF5917-13B1-44D2-8138-EB44818B579D@.microsoft.com...
>> > We have installed SP2 and client-side printing from the browser is
> working
>> > fine for our users on XP/IE6. However, we have some users with NT4/IE6
> on
>> > their machines. They are able to view reports, but when they click the
>> Print
>> > icon, nothing happens (no error, no prompt, nothing).
>> >
>> > Is the ActiveX control for printing included in SP2 supported for
> clients
>> > using NT4?
>>
>

Client attaches to wrong server

Hello All,
I am running SQL server 7 sp4 on an NT4.0 SP6a, I'll call it machin2. I =
am=20
also running SQL server 7 sp2 on an NT4.0 SP6a, I'll call it machine 1. =
Two=20
databases. I am trying to move the database on machine 1 to the server=20
machine 2. I have installed sql and installed all of the patches ( i =
think) for=20
SQL7 sp4 on machine 2. I copied over a back up of the original=20
database(just the data) running on machine 1 to machine 2 after a clean=20
install. Then ran all the patches and updates to get machine 2 to SQL7 =
sp4.=20
Now my problem is if both servers are running my clients will only =
connect=20
to machine 1 no matter what. I have tried specifying ip address in the =
Client=20
utility and still no connection to machine 2. IT connects just fine with =
no=20
errors but it is machine1 not machine2. I f I stop sql services on =
machine1=20
and try to connect to machine2 I get the eror : native SQL error 10004.=20
Cannot locate or connect to SQL server. I can connect to both machines =
with=20
the enterprise utility, but from the client I can only connect to =
machine 1. If I=20
am at the console I can connect to machine 2, but that is the only way I =
know of. I can ping machine2 by name and it resolves correctly if I use =
the=20
-a option when I ping also.
I think I have all of the patches installed to fix everything in SP4 =
but I'm=20
not certain. Any help would be great.
Thanks
Robert SmithCheck the client machines for aliases under the
MSSQLServer\Client\ConnectTo key.
Otherwise, make network traces from the client machine.
run ipconfig /flushdns
ipconfig /registerdns
then start Microsoft Network Monitor or network sniffer.
Then attempt a connection from Query Analyser.
Review the trace and verify that the tcp session is connecting to the
correct machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks! That took care of it. Fpr some reason the connect to key was=20
referencing the wrong server.
Thanks again for the help!

>--Original Message--
>Check the client machines for aliases under the=20
>MSSQLServer\Client\ConnectTo key.
>Otherwise, make network traces from the client machine.
>run ipconfig /flushdns
>ipconfig /registerdns
>then start Microsoft Network Monitor or network sniffer.
>Then attempt a connection from Query Analyser.
>Review the trace and verify that the tcp session is connecting to the=20
>correct machine.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no =
rights.
>
>.
>|||You're welcome!
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Client attaches to wrong server

Hello All,
I am running SQL server 7 sp4 on an NT4.0 SP6a, I'll call it machin2. I =
am=20
also running SQL server 7 sp2 on an NT4.0 SP6a, I'll call it machine 1. =
Two=20
databases. I am trying to move the database on machine 1 to the server=20
machine 2. I have installed sql and installed all of the patches ( i =
think) for=20
SQL7 sp4 on machine 2. I copied over a back up of the original=20
database(just the data) running on machine 1 to machine 2 after a clean=20
install. Then ran all the patches and updates to get machine 2 to SQL7 =
sp4.=20
Now my problem is if both servers are running my clients will only =
connect=20
to machine 1 no matter what. I have tried specifying ip address in the =
Client=20
utility and still no connection to machine 2. IT connects just fine with =
no=20
errors but it is machine1 not machine2. I f I stop sql services on =
machine1=20
and try to connect to machine2 I get the eror : native SQL error 10004.=20
Cannot locate or connect to SQL server. I can connect to both machines =
with=20
the enterprise utility, but from the client I can only connect to =
machine 1. If I=20
am at the console I can connect to machine 2, but that is the only way I =
know of. I can ping machine2 by name and it resolves correctly if I use =
the=20
-a option when I ping also.
I think I have all of the patches installed to fix everything in SP4 =
but I'm=20
not certain. Any help would be great.
Thanks
Robert Smith
Check the client machines for aliases under the
MSSQLServer\Client\ConnectTo key.
Otherwise, make network traces from the client machine.
run ipconfig /flushdns
ipconfig /registerdns
then start Microsoft Network Monitor or network sniffer.
Then attempt a connection from Query Analyser.
Review the trace and verify that the tcp session is connecting to the
correct machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Thanks! That took care of it. Fpr some reason the connect to key was=20
referencing the wrong server.
Thanks again for the help!

>--Original Message--
>Check the client machines for aliases under the=20
>MSSQLServer\Client\ConnectTo key.
>Otherwise, make network traces from the client machine.
>run ipconfig /flushdns
>ipconfig /registerdns
>then start Microsoft Network Monitor or network sniffer.
>Then attempt a connection from Query Analyser.
>Review the trace and verify that the tcp session is connecting to the=20
>correct machine.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no =
rights.
>
>.
>
|||You're welcome!
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.