[THIN] Re: Windows 2000 Terminal server in NT Domain -- Update

  • From: "Joseph Finley" <jfinley@xxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Wed, 9 Apr 2003 14:26:57 -0400



Well, it happened again about an hour ago while I was out to lunch.  One =
of
my techs had to power it off and power on.  Next step is NIC drivers.

Joe



-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On =
Behalf
Of Joseph Finley
Sent: Monday, April 07, 2003 8:59 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Windows 2000 Terminal server in NT Domain




I just checked and we are in fact running 6.1.03.0.  I will update and
reboot tonight.  I will also check into the corrupt BDC someone =3D =
suggested.

Thanks.
Joe


-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On =
=3D
Behalf Of tobias.bjorkskog@xxxxxxxxxxxxxxxxx
Sent: Monday, April 07, 2003 1:58 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Windows 2000 Terminal server in NT Domain




Hi!

We had the same problems after installing SP3.

We updated our NIC drivers for Intel(R) PRO/1000 F Server Adapter.

Our previous driver was version 6.1.03.0, and now we have 6.4.16.0
installed.

I think that fixed the problem, because our server hasn't hanged/crashed
since we updated our drivers.

regards, Tobias






=3D20

                    "Joseph Finley"

                    <jfinley@prcont        To:     <thin@xxxxxxxxxxxxx>

                    rol.com>               cc:

                    Sent by:               Subject:     [THIN] Windows =
=3D
2000
Terminal server in NT Domain            =3D20
                    thin-bounce@fre

                    elists.org

=3D20

=3D20

                    05.04.2003

                    01:19

                    Please respond

                    to thin

=3D20

=3D20





Hopefully, some one knows what this is.

I've opened a case with Microsoft 4 months ago, and they still have yet =
=3D
=3D3D to figure out that it is.=3D3D20

Problem:  At anytime during the day, a terminal server, running Citrix, =
=3D
=3D3D will report the following error in the event log:

The session setup to the Windows NT or Windows 2000 Domain Controller
\\PRCPDC for the domain PRCWF is not responsive.  The current RPC call =
=3D =3D3D
from Netlogon on \\PRC-MF5 to \\PRCPDC has been cancelled.


This server has about 30-40 users on it and when this happens, everyone
get's completely locked up.  I cannot log into the server in console =
=3D3D =3D
mode. I have to power it off and reboot. =3D3D20

I have a PDC and BDC.  If I leave the console logged in and this =3D3D =
=3D
happens, I
can ping both PDC/BDC by IP, by name and I can NBTSTAT -A IP.    I ran a
sniffer for a while and sent them in to Microsoft for examination.  This =
=3D
=3D3D was 3 weeks ago.  I've been handed around to 3 techs and they =
claim =3D3D
everything looks fine in my DNS/WINS.  I even edited a lmhosts. File to
point =3D3D directly to the PDC....I need heklp on this.  It happens to =
4 =3D of
my servers all
running:

Compaq Proliant DL series (380 & 360)
Windows 2000 w/ SP3
Citrix MF 1.8 w/ FR-1 sp2+
Connected to a Cisco 4003 switch.




Need help on this.

Joe

********************************************************
This Week's Sponsor - ThinPrint
Simply the best print solution for
Microsoft Terminal Services 
and Citrix Metaframe.
http://www.thinprint.com/
**********************************************************

For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm

Other related posts: