MetaFrame XP Problem After Upgrade from NT 4.0

(this was also posted in the migration section)
Hello:

We put our first Windows Server 2003 AD DC up this past
Saturday. We still have 2 NT 4.0 BDCs. Now users cannot
access Citrix on different PCs. If they use the same PC
that they used prior to the AD upgrade, it works fine. If
they try to use Citrix from another PC now, it looks like
it logs them on for a split second and then logs them off.
The Citrix servers are all Windows 2000 Server SP4 in a
MetaFrame XP FR1 farm. I don't know too much about Citrix,
and the Citrix admin doesn't seem to know it that well
either! But I did do the AD upgrade and everything else
seems to be working fine.

If I leave the user password blank or put in a wrong
password, Citrix does prompt me, so I'm making the intial
connection to Citrix. I also see a connection to one of
the Citrix servers when I do a netstat command. I've
checked the Citrix KB without much success. One thing I'd
like to know is how to find out which DC the Citrix
connection is using to authenticate the user. The Citrix
servers themselves are using the new 2003 DC for
authentication. Thank you.

Thanks guys in the migration section for your insight. I
had to make our new 2003 AD DC the TS Licensing Server and
activate it. After that Citrix is working well again. Note
to anyone upgrading from an NT domain to AD - make sure
you have TS Licensing Server in your upgrade plans if you
currently use TS or Citrix! In our AD upgrade test we DID
test Citrix after upgrading from NT 4.0 to AD, but we
logged on with the same user account on the test
workstation, so Citrix worked. Who would have thought to
log on with an entirely different account on the
workstation? It looks like the TS/Citrix server maintains
some info on the last client logon and if you log on using
the same workstation, it won't need to issue you a new TS
license, or something along those lines.

Now, let me vent a little about this. I'm the new guy at
the company and have a good grasp of NT, AD, and Exchange,
but I'm not that great with TS or Citrix. My manager
supposedly looked at the errors on the Citrix servers and
even though there were tons of TS licensing errors, he
couldn't put two and two together. I also looked at those
TS licensing errors and mentioned it to our so-called
Citrix admin and he really didn't think too much of it and
me being a rookie with TS and Citrix, I didn't question
him. And then we also have this desktop support guy who
had to put his 2 cents into it, which was pretty much
useless.

Anyway, the moral of the story is: always question
everything other IT people tell you. From my experience,
most of the IT guys I've worked with are really clueless.
It doesn't take much to slap together a Windows network
and have it up and running, so anyone could do that. The
real skill comes from designing the network efficiently,
securely, with fault tolerance in mind, and company growth
in mind. Also, obviously, good troubleshooting skills. Ok,
thanks for again for your responses and letting me vent.

MX

"MX" <(E-Mail Removed)> wrote in message
news:1aa8b01c44ee9$b1d2df70$(E-Mail Removed)...
> Anyway, the moral of the story is: always question
> everything other IT people tell you. From my experience,
> most of the IT guys I've worked with are really clueless.
> It doesn't take much to slap together a Windows network
> and have it up and running, so anyone could do that. The
> real skill comes from designing the network efficiently,
> securely, with fault tolerance in mind, and company growth
> in mind. Also, obviously, good troubleshooting skills. Ok,
> thanks for again for your responses and letting me vent.

It's probably rather a widespread issue. We get questions in this group that
a trained Admin or Networker with reasonable skills should not even have to
ask. But some may be people that are just learning and are working with lab
networks, so we have to cut them some slack.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com