Possibly. You are running nFuse with Project Columbia, right? I would
install SP1 for MF, as it does fix quite a bit of things. Also, if your
Subscription Advantage is current, you can also use FR1 which includes
the mighty Citrix Universal Printer Driver.
CHRIS LYNCH - MCSE, CCNA, CCA
NETWORK ENGINEER - INFORMATION TECHNOLOGY
NRT Incorporated, 27271 Las Ramblas, Mission Viejo, CA 92691
Chris.lynch@xxxxxxxxxx Tel 949.367.3406
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Drazen Vidakovic
Sent: Tuesday, July 16, 2002 3:33 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Clients cannot connect to published app.
No, it did not work. I have all listeners disabled, I have "Server
respond to client broadcast messages" ON
>From Nfuse, when it can not connect I have
NFuse could not complete the operation:
The Citrix Server reported an unspecified error.
I am thinking of shutting down the second server and see what will
happend.
Could it be that on first server I have WIN2000SP2/MFXPFR1
and on second only WIN2000/MFXP?
Drazen
At 21:05 15/07/2002 -0700, you wrote:
If your clients are running either 6.30 or have the Application Set set
to Always Use Specified Server Protocol, and that is set to TCP/IP+HTTP,
then there is absolutely no reason why you would even need the NetBIOS
listener enabled on any of your MF servers.
Let me know how this works.
CHRIS LYNCH - MCSE, CCNA, CCA
NETWORK ENGINEER - INFORMATION TECHNOLOGY
NRT Incorporated, 27271 Las Ramblas, Mission Viejo, CA 92691
Chris.lynch@xxxxxxxxxx Tel 949.367.3406
-----Original Message-----
From: Drazen Vidakovic [mailto:drazen@xxxxxxxxxxxxxxxxxxxxxxx]
Sent: Monday, July 15, 2002 4:09 PM
To: lynch00@xxxxxxx
Subject: RE: [THIN] Re: Clients cannot connect to published app.
Server is farm one does not have any,
BUT
server2 in farm two had every single listener enabled
server1 has only listener on netbios network listener
I disabled UDP and IPX and left NetBios on.
Drazen
At 15:52 15/07/2002 -0700, you wrote:
>So, the Farms do not know about each other. Did you by chance create
>any "listeners" in both farms? Check to see by viewing the properties
>of each server, and then checking in the Metaframe Settings tab. I do
>believe this gives the servers the ability to "see" each other. I'm
>not completely sure about this, but I do believe reading this somewhere
>in a Citrix doc.
>
>CHRIS LYNCH - MCSE, CCNA, CCA
>NETWORK ENGINEER - INFORMATION TECHNOLOGY
>NRT Incorporated, 27271 Las Ramblas, Mission Viejo, CA 92691
>Chris.lynch@xxxxxxxxxx Tel 949.367.3406
>
>
>-----Original Message-----
>From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
>Behalf Of Drazen Vidakovic
>Sent: Monday, July 15, 2002 3:50 PM
>To: thin@xxxxxxxxxxxxx
>Subject: [THIN] Re: Clients cannot connect to published app.
>
>
>They were, but NT4/XP is in different farm anyway and is running in
>native mode.
>On that site, there is no MF1.8.
>
>I have now
>NT4/XP farm one without XML service or published appl at all. No IIS.
>
>WIN2000/XP in farm two with 50 users and XML services and published
>appl WIN2000/XP in farm two in building without any user, XML services
>on, no
>
>published appl defined
> Both servers run CTXXMLSS on port 80 without IIS.
>
>Drazen
>
>At 15:19 15/07/2002 -0700, you wrote:
> >I didn't mean disable the XML service, but rather make sure that both
> >servers are listening on the same TCP port for the XML service. For
> >instance, if you have one server with the XMP service configured to
> >listen to TCP port 2000, and another server listening on TCP port 80,
> >then you WILL get the infamous "I/O Error". Both servers need to be
> >listening on one or the other, not both. Also, you cannot disable
> >the XML port on one of the servers, unless your MF XP server is
> >running in Native Mode. Then either one will not "know" about each
> >other.
> >
> >CHRIS LYNCH - MCSE, CCNA, CCA
> >NETWORK ENGINEER - INFORMATION TECHNOLOGY
> >NRT Incorporated, 27271 Las Ramblas, Mission Viejo, CA 92691
> >Chris.lynch@xxxxxxxxxx Tel 949.367.3406
> >
> >
> >-----Original Message-----
> >From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
> >Behalf Of Drazen Vidakovic
> >Sent: Monday, July 15, 2002 2:55 PM
> >To: thin@xxxxxxxxxxxxx
> >Subject: [THIN] Re: Clients cannot connect to published app.
> >
> >
> >Well, that one did not work. I still have "I/O error" and with NFuse
> >and CSG is specifically problematic because users are losing faith in
> >this kind of scenario.
> >
> >Any suggestion is wellcome.
> >
> >Drazen
> >
> >At 16:33 11/07/2002 +1200, you wrote:
> > >Actually, I have one NT4/MFXP on the same LAN doing one specific
> > >application. Totally different farm. You recon, that can cause all
> > >this
> >
> > >problems? This server was running for last 2 months.
> > >
> > >I'll disable XML services on NT4 and I'll see what happens in next
> > >couple of days.
> > >
> > >Drazen
> > >
> > >At 15:45 10/07/2002 -0700, you wrote:
> > >>The onlything I can image why you would get this error
> > >>intermittantly is if you do have another MetaFrame sever on the
> > >>same
>
> > >>segment (IP
> > >>subnet) that has the XML service installed, and the XML service is
> > >>configured on another port number. Possibly a 1.8 server? Do you
> > >>have the XP farm running in Native mode?
> > >>
> > >>Also, fire up CMC, right-click on your server, and in the GENERAL
> > >>tab see what IP address it has. Then, run IPCONFIG and see if the
> > >>IP addresses match, which they should.
> > >>
> > >>CHRIS LYNCH - MCSE, CCNA, CCA
> > >>NETWORK ENGINEER - INFORMATION TECHNOLOGY
> > >>NRT Incorporated, 27271 Las Ramblas, Mission Viejo, CA 92691
> > >>Chris.lynch@xxxxxxxxxx Tel 949.367.3406
> > >>
> > >>
> > >>-----Original Message-----
> > >>From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]
> > >>On Behalf Of Drazen Vidakovic
> > >>Sent: Wednesday, July 10, 2002 3:18 PM
> > >>To: thin@xxxxxxxxxxxxx
> > >>Subject: [THIN] Re: Clients cannot connect to published app.
> > >>Importance: High
> > >>
> > >>
> > >>Unfortunately, I had settings exactly like in that article.
> > >>Yesterday,
> >
> > >>I connected/disconnected 20 times in a row. Click on file on
> > >>desktop
>
> > >>and cancel out of it. 4 times connect, then 5 times "I/O error"
> > >>and then OK again.
> > >>
> > >>Is there any way of tracing down on W2K what is happening, log
> > >>files, anything?
> > >>
> > >>Drazen
> > >>
> > >>At 08:41 10/07/2002 -0700, you wrote:
> > >>
> > >>
> > >>Well, I was wrong about the possibiilty of an MS patch breaking
> > >>something within IMA or the XML service. It appears to be a
> > >>Datacollector problem (or "by design"). You can read this article
> > >>which I just happened to come across right now:
> > >>
> > >>http://hqextsrvsft01.citrix.com/cgi-bin/webcgi.exe/,/?Session=3914
> > >>45
> > >>7,
> > >>U=
> > >>1,ST
> > >>=79,N=0005,K=10657,SXI=5,Case=obj(16124)
> > >>(text may be wrapped)
> > >>
> > >>I have adjusted what the article says to do, and I am now able to
> > >>connect to the MetaFrame server without problem. I believe that
> > >>this is only caused by the fact that you have only One MF XP
> > >>server.
>
> > >>I have another farm that is not on the same physical network, nor
> > >>in
>
> > >>the
> >
> > >>same company. It has 3 servers witin a Native farm, and that has
> > >>no
>
> > >>issues what so ever.
> > >>
> > >>I am interested to see if Drazen and Danny can use this and
> > >>resolve there same problem also.
> > >>
> > >>Thanks,
> > >>
> > >>CHRIS LYNCH - MCSE, CCNA, CCA
> > >>NETWORK ENGINEER - INFORMATION TECHNOLOGY
> > >>NRT Incorporated, 27271 Las Ramblas, Mission Viejo, CA 92691
> > >>Chris.lynch@xxxxxxxxxx Tel 949.367.3406
> > >>
> > >>
> > >>-----Original Message-----
> > >>From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]
> > >>On Behalf Of Drazen Vidakovic
> > >>Sent: Tuesday, July 09, 2002 3:45 PM
> > >>To: thin@xxxxxxxxxxxxx
> > >>Subject: [THIN] Re: Clients cannot connect to published app.
> > >>
> > >>
> > >>Thank you.
> > >>Microsoft Patches:
> > >>
> > >>Q147222
> > >>Q272582
> > >>Q288165
> > >>
> > >>Q305713
> > >>Q283014
> > >>
> > >>Last two were put this Saturday, they are just printing related.
> > >>At some stage, I was suspecting DNS so I put one more on another
> > >>machine just as a backup. Still same problem.
> > >>
> > >>Drazen
> > >>
> > >>At 15:31 9/07/2002 -0700, you wrote:
> > >> >Thanks. What Microsoft patches do you have installed? Just
> > >> >list out the Q numbers, and I can research what they are.
> > >> >
> > >> >The only instance (besides this one) that I have encountered
> > >> >this error
> > >>
> > >> >was when we didn't have our MF 1.8 servers configured with the
> > >> >XML
>
> > >> >service on the same port number. Once we set all of them to the
> > >> >same port number, the error went away.
> > >> >
> > >> >This one is not the case here.
> > >> >
> > >> >CHRIS LYNCH - MCSE, CCNA, CCA
> > >> >NETWORK ENGINEER - INFORMATION TECHNOLOGY
> > >> >NRT Incorporated, 27271 Las Ramblas, Mission Viejo, CA 92691
> > >> >Chris.lynch@xxxxxxxxxx Tel 949.367.3406
> > >> >
> > >> >
> > >> >-----Original Message-----
> > >> >From: thin-bounce@xxxxxxxxxxxxx
> > >> >[mailto:thin-bounce@xxxxxxxxxxxxx]
> > >> >On Behalf Of Drazen Vidakovic
> > >> >Sent: Tuesday, July 09, 2002 2:29 PM
> > >> >To: thin@xxxxxxxxxxxxx
> > >> >Subject: [THIN] Re: Clients cannot connect to published app.
> > >> >
> > >> >
> > >> >At the moment we have only one W2K/XP server in our group. This
> > >> >one was
> > >>
> > >> >the first, and I am just doing second one.
> > >> >
> > >> >It is part of a domain, PDC is in different site, but BDC is
> > >> >right
>
> > >> >beside. We do not run Active directory. Server is on W2K SP2 /
> > >> >XPaFR1 Also I have Citrix patches.
> > >> >XE101W007,XE101W009,XE101W015,XE101W016
> > >> >
> > >> >Problem we are experiencing is very recent. For four months we
> > >> >had
>
> > >> >only
> > >>
> > >> >about 20 users on single machine. All users were connecting to
> > >> >published desktop. Two weeks ago I
> > >> >
> > >> >deployed another 30 users
> > >> >and then problem started.
> > >> >
> > >> >Also, what I noticed is that I have less then 30 users logged
> > >> >in, I don't have problem, 30 or more can't connect. Also,
> > >> >problem is not consistent, one minute user can connect, next
> > >> >minute "I/O Error". With this error, NFuse (and CSG) don't work
> > >> >and that is annoying.
> > >> >
> > >> >When I tried to connect to server to port 80:
> > >> >
> > >> >HTTP/1.1 400 Bad request
> > >> >Server: Citrix Web PN Server
> > >> >Date: Tue, 09 Jul 2002 21:22:41 GMT
> > >> >Connection: Close
> > >> >
> > >> >By the way, I am using ICA file to connect, not Citrix Program
> > >> >Neighborhood. File is attached.
> > >> >
> > >> >
> > >> >[WFClient]
> > >> >Version=2
> > >> >TcpBrowserAddress=10.89.1.20
> > >> >HttpBrowserAddress=wnmf1.printlink.co.nz
> > >> >KeyboardLayout=(User Profile)
> > >> >KeyboardType=(Default)
> > >> >Domain=BSPG
> > >> >
> > >> >[ApplicationServers]
> > >> >WgtnFull=
> > >> >
> > >> >[WgtnFull]
> > >> >Address=WgtnFull
> > >> >InitialProgram=#WgtnFull
> > >> >ClientAudio=Off
> > >> >Compress=On
> > >> >ScreenPercent=95
> > >> >DesiredColor=2
> > >> ># DesiredHRES=4294967295
> > >> ># DesiredVRES=4294967295
> > >> >TransportDriver=TCP/IP
> > >> >WinStationDriver=ICA 3.0
> > >> >BrowserProtocol=HTTPonTCP EncryptionLevelSession=EncRC5-0
> > >> >
> > >> >[EncRC5-0]
> > >> >DriverNameWin32=PDC0N.DLL
> > >> >DriverNameWin16=PDC0W.DLL
> > >> >
> > >> >[Compress]
> > >> >DriverName=PDCOMP.DLL
> > >> >DriverNameWin16=PDCOMPW.DLL
> > >> >DriverNameWin32=PDCOMPN.DLL
> > >> >
> > >> >At 08:48 8/07/2002 -0700, you wrote:
> > >> > >Thanks for the suggestion. I did put the server farm into
> > >> > >Compatibility mode, and the clients were able to connect. It
> > >> > >appears
> > >>
> > >> > >that there might be an XML bug with FR2/SP2.
> > >> > >
> > >> > >Maybe Drazen can test this out and see if his client can
> > >> > >connect
>
> > >> > >to the
> > >> >
> > >> > >published app.
> > >> > >
> > >> > >Also, Drazen. What does your farm look like? How many
> > >> > >servers?
>
> > >> > >Are
> > >>
> > >> > >they part of a domain, or a workgroup? What Feature Release
> > >> > >are
>
> > >> > >you running? Service Packs?
> > >> > >
> > >> > >Thanks,
> > >> > >
> > >> > >
> > >> > >CHRIS LYNCH - MCSE, CCNA, CCA
> > >> > >NETWORK ENGINEER - INFORMATION TECHNOLOGY
> > >> > >NRT Incorporated, 27271 Las Ramblas, Mission Viejo, CA 92691
> > >> > >Chris.lynch@xxxxxxxxxx Tel 949.367.3406
> > >> > >
> > >> > >
> > >> > >
> > >> > >-----Original Message-----
> > >> > >From: Mack, Rick [mailto:RMack@xxxxxxxxxxxxxx]
> > >> > >Sent: Sunday, July 07, 2002 4:57 PM
> > >> > >To: 'lynch00@xxxxxxx'
> > >> > >Subject: RE: [THIN] Re: Clients cannot connect to published
> > >> > >app.
> > >> > >
> > >> > >
> > >> > >Hi Chris,
> > >> > >Sorry. I sent my answer without reading the rest of your
> > >> > >message, hence
> > >> >
> > >> > >the redundancy. When you telnet to the XML port, I'm assuming
> > >> > >that
> >
> > >> > >you get a response after hitting the return key a few times.
> > >> > >That establishes XML is working. A quick and dirty test is to
> > >> > >turn on MF 1.8 compatibility mode via the farm properties in
> > >> > >the
>
> > >> > >CMC. Set your ICA client up to use TCP/IP (NOT tcpip/http).
> > >> > >Published apps "should"
> > >>
> > >> > >work. This will at least establish that there isn't something
> > >> > >really gross happening. Let me know if that works, because
> > >> > >then we
> >
> > >> > >may be able to do
> > >>something
> > >> > >structured.
> > >> > >Regards,
> > >> > >Rick
> > >> > >Ulrich Mack
> > >> > >rmack@xxxxxxxxxxxxxx
> > >> > >Volante Solutions
> > >> > >18 Heussler Terrace, Milton 4064
> > >> > >Queensland Australia.
> > >> > >tel +61 7 3246 7777
> > >> > >
> > >> > >
> > >> > >
> > >> > >-----Original Message-----
> > >> > >From: Chris Lynch [mailto:lynch00@xxxxxxx]
> > >> > >Sent: Sunday, 7 July 2002 8:00 AM
> > >> > >To: 'Mack, Rick'
> > >> > >Cc: thin@xxxxxxxxxxxxx
> > >> > >Subject: RE: [THIN] Re: Clients cannot connect to published
> > >> > >app.
> > >> > >Importance: High
> > >> > >
> > >> > >
> > >> > >Rick,
> > >> > >Yes, I agree that it has to be a browsing issue. I have
> > >> > >already
>
> > >> > >tried to telnet to port 80, and every other port I set the XML
> > >> > >Service to listen on. I can successfully telnet to that port.
> > >> > >When I try to initiate a session to a published application,
> > >> > >the
>
> > >> > >system is
> > >>
> > >> > >in a TIME_WAIT state when trying to connect to the XML port.
> > >> > >It
>
> > >> > >appears that the server is not sending back any information
> > >> > >that
>
> > >> > >the client is requesting. I already know how the client tries
> > >> > >to
>
> > >> > >get a published application. My problem is what is causing
> > >> > >this? Like I said, there is no firewall at all (software or
> > >> > >hardware) in
> >
> > >> > >between the client and the server. Has anyone experienced this
> > >> > >at all? Thanks,
> > >> > >
> > >> > >
> > >> > >CHRIS LYNCH - MCSE, CCNA, CCA
> > >> > >NETWORK ENGINEER - INFORMATION TECHNOLOGY
> > >> > >NRT Incorporated, 27271 Las Ramblas, Mission Viejo, CA 92691
> > >> > >Chris.lynch@xxxxxxxxxx Tel 949.367.3406
> > >> > >
> > >> > >
> > >> > >
> > >> > >-----Original Message-----
> > >> > >From: Mack, Rick [mailto:RMack@xxxxxxxxxxxxxx]
> > >> > >Sent: Friday, July 05, 2002 3:15 PM
> > >> > >To: 'lynch00@xxxxxxx'
> > >> > >Subject: RE: [THIN] Re: Clients cannot connect to published
> > >> > >app.
> > >> > >
> > >> > >
> > >> > >Hi Chris,
> > >> > >Connecting directly to the server doesn't require any ICA
> > >> > >client
>
> > >> > >server
> > >> >
> > >> > >browsing. If you're connecting to a published application, the
> > >> > >ICA
> >
> > >> > >client has to find any metaframe server, get redirected to the
> > >> > >data collector for that zone and then query the it to get
> > >> > >redirected to a server hosting the published application. The
> > >> > >6.3 clients use TCP/IP+HTTP by default. So the client needs to
> > >> > >be directed to one of the servers in the zone, either by
> > >> > >defining a server address list, or
> > >>
> > >> > >by having a DNS entry in your domain (ica) which points to
> > >> > >your metaframe servers. If you don't have a server list
> > >> > >defined on the client, or an appropriate DNS entry, nothing
> > >> > >happens. Another essential component of the published app
> > >> > >resolution process is the
> >
> > >> > >XML service on the Metaframe servers. If this isn't working,
> > >> > >or you've changed the default port address (80) to something
> > >> > >else, things won't work. Try "telnet metaframe_server_ip 80,
> > >> > >and hit return
> > >>
> > >> > >a few times, you should get a response. If you've got IIS
> > >> > >running on the Metaframe servers as well, check the XML
> > >> > >service is running
> >
> > >> > >(net
> > >> > >start) or if its running on a non-standard port address
> > >> > >(defined
> >at
> > >> > >metaframe installation time) then the ICA clients will need to
> > >> > >be changed accordingly. Regards, Rick Ulrich Mack
> > >> > >rmack@xxxxxxxxxxxxxx Volante Solutions
> > >> > >18 Heussler Terrace, Milton 4064
> > >> > >Queensland Australia.
> > >> > >tel +61 7 3246 7777
> > >> > >
> > >> > >
> > >> > >
> > >> > >-----Original Message-----
> > >> > >From: Chris Lynch [mailto:lynch00@xxxxxxx]
> > >> > >Sent: Saturday, 6 July 2002 5:26 AM
> > >> > >To: thin@xxxxxxxxxxxxx
> > >> > >Subject: [THIN] Re: Clients cannot connect to published app.
> > >> > >
> > >> > >
> > >> > >Anyone have any suggestions?
> > >> > >Thanks,
> > >> > >CHRIS LYNCH - MCSE, CCNA, CCA
> > >> > >NETWORK ENGINEER - INFORMATION TECHNOLOGY
> > >> > >NRT Incorporated, 27271 Las Ramblas, Mission Viejo, CA 92691
> > >> > >Chris.lynch@xxxxxxxxxx Tel 949.367.3406
> > >> > >
> > >> > >
> > >> > >-----Original Message-----
> > >> > >From: thin-bounce@xxxxxxxxxxxxx
> > >> > >[mailto:thin-bounce@xxxxxxxxxxxxx]
> >
> > >> > >On
> > >>
> > >> > >Behalf Of Chris Lynch
> > >> > >Sent: Wednesday, July 03, 2002 12:59 PM
> > >> > >To: thin@xxxxxxxxxxxxx
> > >> > >Subject: [THIN] Clients cannot connect to published app.
> > >> > >
> > >> > >
> > >> > >
> > >> > >-----BEGIN PGP SIGNED MESSAGE-----
> > >> > >Hash: SHA1
> > >> > >I have a test server that is running Windows 2000 Server with
> > >> > >Service
> > >>
> > >> > >Pack 2, SRP1SP2, MetaFrame Xpe with SP2/FR2, and I have a
> > >> > >problem connecting clients to published apps. Users can make
> > >> > >a connection
> >
> > >> > >to
> > >>
> > >> > >the server using RDP or ICA, but only a Custom application
> > >> > >connection
> > >>
> > >> > >TO THE SERVER ONLY. Even if they specify an application to
> > >> > >connect to in the Custom ICA Connections, they receive "I/O
> > >> > >Error." The ICA client ver is 6.30.1050 Like I said, I can
> > >> > >connect directly to the server, but not to a Published App.
> > >> > >This
>
> > >> > >server is in a workgroup, and I do have Local users and groups
> > >> > >configured. I remember seeing an article on Citrix talking
> > >> > >about there are some missing REG keys for the
> > >> >
> > >> > >ICA protocol, but I cannot find it anymore. I don't remember
> > >> > >if
>
> > >> > >that
> > >>
> > >> > >article deals with this issue. I do have the FR set on the
> > >> > >server.
> >
> > >> > >I
> > >>
> > >> > >can manage it via the Citrix Management Console. But my test
> > >> > >users get
> > >> >
> > >> > >the infamous "I/O Error". Also, they are not going through a
> > >> > >firewall, they are on the same IP subnet, I do have the XML
> > >> > >Service listenng on the correct port, and the clients are
> > >> > >configured with the
> > >>
> > >> > >correct port for the XML service (which is the default).
> > >> > >Anyone have any suggestions? Thanks, CHRIS LYNCH - MCSE,
> > >> > >CCNA, CCA NETWORK ENGINEER - INFORMATION TECHNOLOGY NRT
> > >> > >Incorporated, 27271 Las Ramblas, Mission Viejo, CA 92691
> > >> > >Chris.lynch@xxxxxxxxxx Tel 949.367.3406 -----BEGIN PGP
> > >> > >SIGNATURE-----
> > >> > >Version: PGP 7.1
> > >> > >iQA/AwUBPSNXnfl56xfvzmMfEQIOQACeLTt+AgAsHH+cbooU7xit98XjUxQAn0
> > >> > >oH
> > >> > >sCt4EoRbkE+uQ0px8GzQHRD/
> > >> > >=f9cK
> > >> > >-----END PGP SIGNATURE-----
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >===================================
> > >> > >For Archives, to Unsubscribe, Subscribe or
> > >> > >set Digest or Vacation mode use the below link.
> > >> > >http://thethin.net/citrixlist.cfm
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >===================================
> > >> > >For Archives, to Unsubscribe, Subscribe or
> > >> > >set Digest or Vacation mode use the below link.
> > >> > >http://thethin.net/citrixlist.cfm
> > >> > >
> > >> > >
> > >> > >
> > >> > >**************************************************************
> > >> > >**
> > >> > >**
> > >> > >***
> > >> > >*
> > >> > >This email may be confidential and/or privileged. Only the
> >intended
> > >> > >recipient may access or use it. Any dissemination,
> > >> > >distribution or copying of this email is strictly prohibited.
> > >> > >If you are not the intended recipient please notify us
> > >> > >immediately by return email
> >and
> > >> > >then erase the email. We use virus scanning software but
> > >> > >exclude
> >all
> > >> > >liability for viruses or similar in any attachment or
> > >> > >message...,..,..,.
> > >> > >
> > >> > >
> > >> > >**************************************************************
> > >> > >**
> > >> > >**
> > >> > >***
> > >> > >*
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >===================================
> > >> > >For Archives, to Unsubscribe, Subscribe or
> > >> > >set Digest or Vacation mode use the below link.
> > >> > >
> > >> > >http://thethin.net/citrixlist.cfm
> > >> >
> > >> >Drazen Vidakovic
> > >> >Technical System Architect
> > >> >LegislationDirect, Blue Start Print Group
> > >> >Drazen.Vidakovic@xxxxxxxxxxxxxxxxxxxxxxx
> > >> >Drazen.Vidakovic@xxxxxxxxxxxxxxxx
> > >> >+64 4 495 2802
> > >> >+64 25 530 876
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >===================================
> > >> >For Archives, to Unsubscribe, Subscribe or
> > >> >set Digest or Vacation mode use the below link.
> > >> >
> > >> >http://thethin.net/citrixlist.cfm
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >===================================
> > >> >For Archives, to Unsubscribe, Subscribe or
> > >> >set Digest or Vacation mode use the below link.
> > >> >
> > >> >http://thethin.net/citrixlist.cfm
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>===================================
> > >>For Archives, to Unsubscribe, Subscribe or
> > >>set Digest or Vacation mode use the below link.
> > >>
> > >>http://thethin.net/citrixlist.cfm
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>===================================
> > >>For Archives, to Unsubscribe, Subscribe or
> > >>set Digest or Vacation mode use the below link.
> > >>
> > >>http://thethin.net/citrixlist.cfm
> > >>
> > >>
> > >>Drazen Vidakovic
> > >>System & Network architect
> > >>Tel: 04 495 2802
> > >>Mobile: 025 530 876
> > >>Email: Drazen.Vidakovic@xxxxxxxxxxxxxxxxxxxxxxx
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>===================================
> > >>For Archives, to Unsubscribe, Subscribe or
> > >>set Digest or Vacation mode use the below link.
> > >>
> > >>http://thethin.net/citrixlist.cfm
> > >
> > >
> > >
> > >
> > >
> > >===================================
> > >For Archives, to Unsubscribe, Subscribe or set Digest or Vacation
> > >mode use the below link.
> > >
> > >http://thethin.net/citrixlist.cfm
> > >
> >
> >Drazen Vidakovic
> >Technical System Architect
> >LegislationDirect, Blue Start Print Group
> >Drazen.Vidakovic@xxxxxxxxxxxxxxxxxxxxxxx
> >Drazen.Vidakovic@xxxxxxxxxxxxxxxx
> >+64 4 495 2802
> >+64 274 530 876
> >
> >
> >
> >
> >===================================
> >This weeks Sponsor:
> >triCerat, Inc
> >ScrewDrivers fxp: Self Configuring Printer Driver with Bandwidth
> >Control Learn more at:
> >http://www.tricerat.com/?page=products&product=sdfxp
> >
> >===================================
> >For Archives, to Unsubscribe, Subscribe or
> >set Digest or Vacation mode use the below link.
> >
> >http://thethin.net/citrixlist.cfm
> >
> >
> >
> >
> >===================================
> >This weeks Sponsor:
> >triCerat, Inc
> >ScrewDrivers fxp: Self Configuring Printer Driver with Bandwidth
> >Control Learn more at:
> >http://www.tricerat.com/?page=products&product=sdfxp
> >
> >===================================
> >For Archives, to Unsubscribe, Subscribe or
> >set Digest or Vacation mode use the below link.
> >
> >http://thethin.net/citrixlist.cfm
>
>Drazen Vidakovic
>Technical System Architect
>LegislationDirect, Blue Start Print Group
>Drazen.Vidakovic@xxxxxxxxxxxxxxxxxxxxxxx
>Drazen.Vidakovic@xxxxxxxxxxxxxxxx
>+64 4 495 2802
>+64 274 530 876
>
>
>
>
>===================================
>This weeks Sponsor:
>triCerat, Inc
>ScrewDrivers fxp: Self Configuring Printer Driver with Bandwidth
>Control Learn more at:
>http://www.tricerat.com/?page=products&product=sdfxp
>
>===================================
>For Archives, to Unsubscribe, Subscribe or
>set Digest or Vacation mode use the below link.
>
>http://thethin.net/citrixlist.cfm
Drazen Vidakovic
Technical System Architect
LegislationDirect, Blue Start Print Group
Drazen.Vidakovic@xxxxxxxxxxxxxxxxxxxxxxx
Drazen.Vidakovic@xxxxxxxxxxxxxxxx
+64 4 495 2802
+64 274 530 876
Drazen Vidakovic
System & Network architect
Tel: 04 495 2802
Mobile: 025 530 876
Email: Drazen.Vidakovic@xxxxxxxxxxxxxxxxxxxxxxx
===================================
This weeks Sponsor:
triCerat, Inc
ScrewDrivers fxp: Self Configuring Printer Driver with Bandwidth Control
Learn more at:
http://www.tricerat.com/?page=products&product=sdfxp
===================================
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link.
http://thethin.net/citrixlist.cfm
