Jump to content

Recommended Posts

Posted

We've been running TS 2.1 as a Citrix client successfully on 30x via M10000 clients for several months.

We recently bought another 60 via M10000 motherboards that we have installed into 2 classrooms.

All the machines now successfully PXE boot the same image, and use the same global configuration file. They are all able to get their network configuration from DHCP once they have booted.

The problem is that the newer machines cannot connect to the Citrix servers - they display the message

"networking or dial-up problems are preventing communication with the server" . but the older clients still connect fine, even though they all use the same image/configuration.

 

I checked that there are no obvious connection problems - the new machines can resolve the hostnames of the Citrix servers and can ping them and telnet to port 1494 (ICA).

I'm really not understanding what is going on here, we bought the same model motherboard because we know that that the M10000's worked. My suspicion is that Via have slightly changed some of their hardware and the drivers are not upto date?.

I've also tried using the latest 2.2rc4 build, but it has given exactly the same problem.

 

Hopefully I've just overlooked the obvious, and any help is appreciated !

Posted

To troubleshoot, you could try banging in an old NIC that works with your build.

 

You could also check the BIOS settings (possibly downgrade the BIOS on the new ones?) and also check that you have enough licenses for Citrix ;)

Posted

Thanks Ric.

I added a trusty realtek card - booted by PXE then swapped the cable over -- Same problem.

Log files on the citrix servers are displaying: "The terminal server cannot issue a client license."

I know we bought the cals so its looking like we've got a borked windows licensing server.

Posted

check your TS CALs - these can get locked up if you replace a load of machines (hence why I have more than I need). I take it that the server cannot be found with the realtek card either?

 

The TS CALs are tied to the NIC's MAC address so if you have a booting machine with a separate NIC, you could also try booting with that.

Posted
I take it that the server cannot be found with the realtek card either?

 

indeed.

 

The TS CALs are tied to the NIC's MAC address

 

Thanks, I didn't realise that.

 

I'm 99% sure that the Windows TS cals are the problem - I'll confirm later.

THanks again for your help

Posted

This has been resolved and I can confirm it was a windows licensing server issue.

(and I actually assumed it was a linux problem ! - I should know better :wink: )

 

The license server was installed onto a new box and reactiveated, but it appears the Terminal servers didn't pick up the new license server.

I hardcoded the Terminal Servers registry so they could talk to the new license server.

 

thanks again

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...