maybe try different settings for browser protocol and ica master
browser (maybe port number?)
On Mon, Oct 17, 2011 at 21:56, Amodei, Anthony aamo...@premierprizm.com wrote:
Hello,
Has anyone had issues configuring the Citrix Receiver? I keep getting a
‘Network is unreachable’ message .
Hi Anthony.
We are using Citriy Receiver and it works. There are some issues:
- Bevore starting the Citrix Receiver run as superuser:
ln -s /usr/lib/libXm.so.4 /usr/lib/libXm.so.3.0.2
Simply put this commandline in an executable file stored
in
Hi Dave,
using a router as the dhcp-server is no problem. OTC uses a dhcp-proxy to
notice the pxe-boot requests. You should not install openthinclient on a
machine which already used as dhcp-server.
Name resolution should be used. Be sure that you can resolve (network-wide)
an IP for the name
Hello and thanks in advance!
Has anyone been successful in setting up dual screen thin clients using the ATI
radeon cards? No matter what driver I try from the list it just crashes on thin
client boot, the only options that work are Automatic or Vesa, but of course
none of these allow for dual
Hi Jorn.
Many thanks for coming back to me.
Last weekend I created a DHCP server from an old machine to see what a
difference it would make to the Thin Client boot up time.
I have been taking two sets of timing namely from thin client startup until the
Welcome to Thin Client Window and then
Hi Gary,
Could you remember what name resolution is necessary on your system ?
I have set up a Linux OTC server, a Linux based DHCP server together vwith a
router(for internet) and one other Dell Optiplex GX280 as the Thin Client.
Problem is that it is taking several minutes to reach the Thin
HI,
I have successfully connected OTC clients on 0.4.5 to Windows 2003 terminal
servers using Windows 2003 license servers. I am trying to transition
everything to Windows 2008 but have run into a problem. I'm am
not getting any errors from either the OTC side or the Windows side so I'm
not sure
Dave,
a very efficient way to troubleshoot this would be to launch a
packetsniffer like Wireshark on the OTC server and to capture the packet
stream. If you're a bit savvy about network protocols, you should see in
no time the root of the problem.
B.
On 10/18/11 21:10, David Wilson wrote:
In addition to my previous mail: check also with ethtool the connection
parameters of the network cards involved and consecutively the
connection parameters on the switch. Wrong type of negotiation can lead
to serious network delays like you experience them.
B.
On 10/18/11 21:00, David Wilson
