Search results for query: *

If you have to upgrade only one, ensure you upgrade the DC..that is the one that needs to be the higher revision, always.

actually that makes it easier as you don't have to troubleshoot it.... look at my reply above and from the outside WAN, ensure the outside ip address is in the client server location and that you click on firewalls, and put a check on "use alternate address for firewalls" don't worry...

stop the IIS service on the server before you re-reregister the port...

one thing you could do is do a search on the internet for wtsuprn.inf file...check on citrix' or the thin.net websites...if you get the *.txt file and open it, it'll list like 500 printers and what the terminal server should use to substitute...you should rename your original wtsuprn.inf file...

Okay...here is what you wanna do...on your lan where your local subnet is, you can connect locally right? Fine, that's how it should be. Now on the WAN side, there are two things...one, although you did the altaddr on the server, if there is a firewall, then that alternate address also needs to...

you can install the cmc onto a win2kpro machine... it's on the cd...look in w2k, administration, and you'll see cmc...install it from there and you can administer the farm.

What version of MF are you on, hotfixes, etc, include MS service packs... any hotfixes on the CSG? Is it intel or solaris? what version are the clients?

is there a switch between the servers and the clients?

there is another posting along the same lines as yours and they say that they contacted wyse and found out that the ica client on the 2500t were not fully compatible with mf1.8 sp3. as they are discontinued item, they haven't done any testing with them. You may be able to contact wyse just to...

I was wondering if wyse had a newer version of the ica client that you could flash onto the units. Have the units ever worked sucessfully? if so, what was the sp level of the mf server? You could back out of sp3 to get back to sp2 level and try that...

what version of nfuse are you running? You are on MFXP FR1?

Have you checked connection config tool on all the servers? or user properties? There may be a setting that is time-based for disconnects to reset the session

Not 100% sure this will work, but have you tried putting it back to the default in the registry, then closing out, then from a command prompt or run command line typing "change user /install", then going back to the registry, making the change, exit out of the registry, go back to run...

Citrix Secure gateway is an easily configurable solution to provide SSL/TLS transerval from client to server. It is comprised of a CSG server and a secure ticket authority--this can be on a mfserver or standalone, your choice. Whether you are your own ticket authority or not, you configure the...

did you remap the drives prior to installing MFXP? there is a known issue that the COM+ gets hosed.... Also, check in computer management,users and groups and see if you disabled any of the internet guest accounts. If so, enable them, then run the nfuse installation....that worked for me (I...

do a search on the server for nfuse.properties file, open it in wordpad/notepad and scroll down until you see Address=[NFuse_IPv4Address]...change it to [NFuse_IPv4AddressAlternate] this tells the Nfuse server there is another address it should use. save, stop/start IIS...try that...remember...

is there anyway that you can upgrade the client? Wyse should be able to give you a package that you can ftp to the thinclient boxes....can you try that? My fault, I thought you were on MFXP....are you planning on moving to that?

Okay, before you relicense, run clicense in_use_by to see if you have the licenses really... Can you do a netmon trace from the client to the server to see where it fails? citrix spans subnets, so this is interesting. I don't think it's a licensing issue...let me know what the trace shows...

What kind of hub/switch are you using between the Citrix Server and the thin clients?

Okay, let's take NFuse outta the picture for now, except I want to know if in the nfuse.properties page you've set the altaddr there and if nfuse is on the same server. Just for fun, install the ica client on the nfuse server if it's a separate box and try to make a connection from there, is it...