NAC Windows Client 4.9.3.5 issues with windows 8

Hi, We are using NAC Client 4.9.3.5 and have had no major issues until the Client wanted to test with a Windows 8 Tablet, same issue also occurs on Windows 8 test Laptops.
The NAC client pops up with the message that the version of Software is not supported.
Is there a known workaround for this?
It's currently out of scope for the NAC rollout Project but will cause issues when the client does move to Windows 8.
Any help will be very much appreciated.
Thanks,
Terry

Terry,
Please ensure that you are using Internet Explorer in Desktop Mode and not the default Metro Mode for Tablets.
Note In Windows 8 Operating System, the Internet Explorer has two modes, Desktop and Metro. In the Metro mode, the ActiveX plugins are restricted. You cannot download NAC Agent in the Metro mode. You must switch to Desktop mode and then launch Internet Explorer to download NAC Agent.
This note is found in the "Cisco NAC Appliance - Clean Access Manager Configuration Guide, Release 4.9(3)" found here:
http://www.cisco.com/en/US/docs/security/nac/appliance/configuration_guide/49x/cam/m_webagt.html#wp1473153

Similar Messages

Oracle 9.2.0.6 client JDBC OCI driver compatibility issue with JRockit 1.4.

I have weblogic server 8.1 sp4 running on Linux E3.0 using JRockit 1.4.2_5.
I cannot seem to get the Oracle driver ojdbc14.jar to work. Yes I have added $ORACLE_HOME/bin to my classpath prior to any weblogic classes, I added $ORACLE_HOME/lib and $ORACLE_HOME/jdbc/lib to my LD_LIBRARY_PATH with no luck.
I get the error "no ojdbc10 in java.library.path".
I keep reading in the JDBC driver notes that the driver is compatible with different version of JDK 1.x but not JRockit. Perhaps Oracle 10 has this fixed.
Anyone experiences the same problem ? I am stuck ..

Oracle database 10.2 drivers ojdbc14.jar may also be used with JDK 5.0.
http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm#02_03

Directory Caching issue with Cisco Jabber client for Windows

Hi ,
I am facing cache issue with Cisco Jabber client for Windows. If I do any change related to modification or deletion of contacts in Active Directory/ Callmanager, it does not reflect in the Jabber. Because jabber takes the contacts from the locally stored cache file in the Windows system.
Every time I have to remove the cache file to overcome this issue, practically it's not possible to do the same with all the Widows users. As, if any employee leaves the company and still I can see his contact appears in the "Cisco Jabber client". I have not seen this issue with Android/Apple iOS.
Is there any automated way to remove the cache file?
Here is the detail of CUCM,Presence and Jabber.
CUCM version: 9.1.x
Presence : 9.1.X
Jabber : 10.5 and 10.6

Hello
On our environment we had to install a dedicated Microsoft Certificate Authority "just for Cisco Jabber usage" to house the
Network Device Enrollment Service.
Our certificate for the CUPS were generated on this Certification Authority too.
I discussed this certificate matter with my colleagues this afternoon and nobody seems to remember how these certificates were deployed into the
Enterprise Trust store for the users.
But I think they asked all 400 users to accept the 3 certificates by answering "yes" to the popup instead of using a script deployed by GPO...
I wish you success with that deployment and really hope you have a technical partner that *Knows* this subject.
Our partner left us alone with that unfortunately.
Florent
EDIT: If the "Certutil script method" works, please let me know. This could be useful in our own deployment.

Windows 8 64 bit issues with Cisco AnyConnect Secure Mobility Client version 3.1.04072

I am having an issue with the Cisco AnyConnect Secure Mobility Client version 3.1.04072 on a Windows 8 64 bit laptop.
I am able to create the VPN connection but the connection will not allow data to be transferred.
Stats from a manual connection:
Cisco AnyConnect Secure Mobility Client Version 3.1.04072
VPN Stats
    Bytes Received: 14375
    Bytes Sent: 0
    Compressed Bytes Received: 0
    Compressed Bytes Sent: 0
    Compressed Packets Received: 0
    Compressed Packets Sent: 0
    Control Bytes Received: 0
    Control Bytes Sent: 0
    Control Packets Received: 0
    Control Packets Sent: 0
    Encrypted Bytes Received: 7820
    Encrypted Bytes Sent: 1207
    Encrypted Packets Received: 9
    Encrypted Packets Sent: 3
    Inbound Bypassed Packets: 0
    Inbound Discarded Packets: 0
    Outbound Bypassed Packets: 0
    Outbound Discarded Packets: 0
    Packets Received: 4
    Packets Sent: 0
    Time Connected: 00:03:01
Protocol Info
    Inactive Protocol
        Protocol Cipher: RSA_3DES_168_SHA1
        Protocol Compression: None
        Protocol State: Disconnected
        Protocol: DTLS
    Active Protocol
        Protocol Cipher: RSA_3DES_168_SHA1
        Protocol Compression: Deflate
        Protocol State: Connected
        Protocol: TLS
OS Version
    Windows 8 : WinNT 6.2.9200
Log from the data transmission software:
24/12/2013 12:51:13 - Application version = 1.11.28.0
24/12/2013 12:51:13 - Lodgement Library Version = 1.11.28.0
24/12/2013 12:51:13 - Connection Method = INTERNET
24/12/2013 12:51:13 - DIS Connection Type = Automatic
24/12/2013 12:51:13 - VPN Client = ACTIVE
24/12/2013 12:51:13 - Check Available Connections = NOT ACTIVE
24/12/2013 12:51:13 - Windows 8 (6.2.9200 SP )
24/12/2013 12:51:13 - Language: English (Australia)
24/12/2013 12:51:13 -
24/12/2013 12:51:13 - Connected to ISP via LAN
24/12/2013 12:51:13 - Checking for presence of VPN client.
24/12/2013 12:51:13 - VPN client found. (C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpncli.exe)
24/12/2013 12:51:13 - The Cisco AnyConnect Secure Mobility Client application is in use.
24/12/2013 12:51:18 - Terminating Cisco AnyConnect Secure Mobility Client in progress ...
24/12/2013 12:51:18 -
24/12/2013 12:51:18 - Checking Cisco AnyConnect version.
24/12/2013 12:51:19 - Cisco AnyConnect Secure Mobility Client (version 3.1.04072) .
24/12/2013 12:51:19 - Copyright (c) 2004 - 2013 Cisco Systems, Inc. All Rights Reserved.
24/12/2013 12:51:19 - Config file directory:C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\
24/12/2013 12:51:19 -
24/12/2013 12:51:19 - Loading profile:C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Profile\ELS-IMelAde-TCP.xml
24/12/2013 12:51:19 -
24/12/2013 12:51:19 - Initializing the VPN connection.
24/12/2013 12:51:19 - Ready to connect.
24/12/2013 12:51:19 - Ready to connect.
24/12/2013 12:51:19 - Contacting ELS-IMelAde-TCP.
24/12/2013 12:51:23 - Authenticating user.
24/12/2013 12:51:23 - Connected to VPN concentrator.
24/12/2013 12:51:23 - Establishing VPN session...
24/12/2013 12:51:23 - Checking for profile updates...
24/12/2013 12:51:23 - Checking for product updates...
24/12/2013 12:51:23 - Checking for customization updates...
24/12/2013 12:51:23 - Performing any required updates...
24/12/2013 12:51:23 - Establishing VPN session...
24/12/2013 12:51:23 - Establishing VPN - Initiating connection...
24/12/2013 12:51:24 - Establishing VPN - Examining system...
24/12/2013 12:51:24 - Establishing VPN - Activating VPN adapter...
24/12/2013 12:51:24 - Establishing VPN - Configuring system...
24/12/2013 12:51:24 - Establishing VPN...
24/12/2013 12:51:24 - Connected to VPN concentrator.
24/12/2013 12:51:24 - Connected to ELS-IMelAde-TCP.
24/12/2013 12:51:24 - Connected to VPN concentrator.
24/12/2013 12:51:24 - Connection to VPN client return code = 0.
24/12/2013 12:51:24 - Connected to VPN concentrator.
24/12/2013 12:51:24 - Connecting : Connecting to 203.202.43.2.
24/12/2013 12:51:45 - Error in ConnectToDIS - Socket Error # 10060
Connection timed out.
24/12/2013 12:51:46 -
24/12/2013 12:51:46 - Disconnecting from the VPN concentrator.
24/12/2013 12:51:46 - Disconnect in progress, please wait...
24/12/2013 12:51:46 - Detaching AnyConnect, please wait...
24/12/2013 12:51:47 - Detached.
24/12/2013 12:51:47 - Disconnected from VPN concentrator.
24/12/2013 12:51:47 - *****************************************************
24/12/2013 12:51:47 -               END OF LODGEMENT PROCESS
24/12/2013 12:51:47 - *****************************************************
Issue history:
- Previously running Cisco VPN client on Windows 8 64 bit laptop (VPN working and able to transmit data over VPN)
- Upgrade to Windows 8.1 stopped the VPN client working
- Refreshed system back to Windows 8 and reinstalled all software
- Cisco VPN client would not install on system
- Cisco AnyConnect Secure Mobility Client installs and is able to connect to VPN host
- Cisco AnyConnect Secure Mobility Client downloads and installs software from VPN host
- Data transmission software returns error code #10060
Any assistance would be greatly appreciated.

anyone found the fix for this?

SL Server Permission Issues with Windows XP Clients

I'm running into some permissions issues with Snow Leopard Server. I know it's specific to SL Server because I have two Leopard servers and neither one is affected. All servers are set up the same way.
I'm using this SL server as a file server in the golden triangle approach: AD for Users, OD for Groups that supply AD User membership. I have one volume per OD group, and that group has read/write privileges to that volume via the default Server Admin read/write ACL. POSIX permissions are 770 on the top level directory, and ownership is set to the AD user who owns the volume, and the OD group the volume belongs to.
The client is XP SP3. When the client accesses a share on the SL server, their access is correctly granted and they can browse the share and read any files inside the share. They can copy files to the share from wherever. They can open, edit, and save files. However, they cannot rename or delete files within the share. They cannot rename folders, but can delete them. This affects all AD users regardless of the OD group they're in.
I have a few Windows 7 and Vista clients on the network, and these two OS's are not affected by this so the problem is limited to XP. If I create a user in OD, and auth to the sever from the XP client as that user, the problem goes away, so it's something to do with AD and SMB.
I do have a ticket in with Apple support, which was escalated to Engineering. Still waiting on that.
Things I have tried that have not worked/helped:
-Modify the ACL to Full Privileges
-Tried removing/re-adding user to OD group.
-Remove darwin_streams from vfs_objects in smb.conf
stream support = no
ea support = yes/no (tried both ways)
darwin_streams:brlm = no
-Added nt acl support = no to smb.conf
per http://bit.ly/6aYycW
-Animal sacrifice..... ??
Help?

I need to do more testing, but I think the fix is to add "acl check permissions = no" to the bottom of /etc/smb.conf:
; Site-specific parameters can be added below this comment.
[global]
acl check permissions = no

Website Owner having new issues with Clients and Windows 8

I own a website that has a home-programmed chat. We've been in business about 12 years without any issues with compatibility. The chat is programmed in C and runs in a standard browser.
Lately I've had a few users (3 or 4) that have upgraded their machines and can no longer run the chat.
Most users that use Windows 8, or 7, or Vista, or whatever, have no problems. They can use the latest versions of IE, Firefox, Chrome, whatever they choose.
However, these users with problems can use none of the above.
I've gone through standard programs that block a chat, like firewalls and other spyware preventions. Shutting these off doesn't resolve the problem. Conflicting programs doesn't seem to be an issue, either. They aren't touch screen so I don't believe it
is a problem with the video card.
So that brings me back to the OS. The common thread seems to be that they are HP computers, and they have a new install of Windows 8. I think that there might be a missing DLL or other C Library that HP's installation of Windows 8 might be lacking.
Any suggestions on if I'm on the right track, and more importantly, how do I fix this problem?

Hi，
Seems this is a web-based chatting program, I suggest you add the site to a compatibility view list, (launch IE, Tools\Compatibility View list) then check this issue again. Check the error message and infromation recorded in the event viewer to find out
the cause.
Make sure the computers have all the latest updates, especially for video and audio drivers.
Clear the cache\temporary internet files in IE, or test this issue in a no add-ons mode.
From your description, it also sounds like a "defect\bug" for the chatting-program on Windows 8 on HP computers, if so, it should be related with development. you may find more help in the developer forum
Internet Explorer Extension Development Forum
http://social.msdn.microsoft.com/Forums/ie/en-US/home?forum=ieextensiondevelopment
Yolanda Zhu
TechNet Community Support

Windows 7 Pro DNS issue with static IP

0
down vote
favorite
I have been unable to solve a DNS problem I am having as follows:
I have a Windows 7 Professional (64 bit) computer running VirtualBox with a couple of Windows XP guests (not sure if this bit is relevant). After heavy file copying/transfer on both of the Windows XP machines, both the guest machines AND the host loose anything
DNS related, so I cannot call anything by name, but by direct IP works fine. The only resolution is to reboot the (host) machine and it will then work OK for a while until it happens again. The only trigger to make it seem to happen quicker is to re-initiate
the heavy file transfer and this then causes the DNS resolution to stop working again.
The machine has a fixed IP address, so it isn't related to DHCP.
I've tried the machine connected wired and wireless, no difference.
The IP settings are manual and I have tried giving it the DNS settings of the router (normal settings) and I have also tried giving it Google's DNS servers (8.8.8.8 & 8.8.4.4). No difference.
It seems to happen (sooner) during heavy traffic.
Other Windows 7 machines in the network work fine (though they are Home version, not Pro).
ONLY DNS fails, direct IP works OK.
Reboot seems only solution at the moment.
I am now lost as to what to try to resolve this issue, I do not really want to reload Windows 7 as it is a relatively new install... I have read about issues with wired connections on my router (BT Home Hub 2.0) so tried a wireless connection, still the
same.
Here is my ipconfig /all (it shows the BT Home Hub router DNS settings, but it also failed with Google's 8.8.8.8 and 8.8.4.4 entered here and also with the routers 192.168.1.254 (default).
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\G>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : e1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 30-85-A9-AD-07-81
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::59f:484a:827f:42ba%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.87(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 238060969
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-2B-4D-30-85-A9-AD-07-81
DNS Servers . . . . . . . . . . . : 217.32.171.21
213.120.234.30
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-00-28-56
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8d2d:7418:381b:8dc0%15(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 336068647
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-2B-4D-30-85-A9-AD-07-81
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{486D4DCC-9CB7-417E-A796-596E0E6B1D54}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{67455999-75A5-436E-9EAC-12B093363132}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Users\G>
Any ideas where to look, or what other info to provide for any assistance?
Many thanks in advance.

Hi,
This has just happened again, here is the content of the netstat results as requested...
If I kill the VirtualBox virtual machines, it starts working again. It is as if there are no ports left, but I am not occupying that many? Surely Windows 7 can cope with this?
I feel I am missing something important, but cannot put my finger on it...
Further below, I have re-run the netstat command AFTER I have closed the VirtualBox machines and the system works OK.
netstat results DURING ISSUE:
Active Connections
Proto Local Address          Foreign Address        State           PID
TCP    0.0.0.0:21             0.0.0.0:0              LISTENING       1444
[FileZilla Server.exe]
TCP    0.0.0.0:25             0.0.0.0:0              LISTENING       1692
[MESMTPC.EXE]
TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
Can not obtain ownership information
TCP    0.0.0.0:110            0.0.0.0:0              LISTENING       1660
[MEPOPS.EXE]
TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       752
RpcSs
[svchost.exe]
TCP    0.0.0.0:143            0.0.0.0:0              LISTENING       1524
[MEIMAPS.exe]
TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
Can not obtain ownership information
TCP    0.0.0.0:1221           0.0.0.0:0              LISTENING       4796
[VirtualBox.exe]
TCP    0.0.0.0:2199           0.0.0.0:0              LISTENING       4820
[VirtualBox.exe]
TCP    0.0.0.0:3306           0.0.0.0:0              LISTENING       1756
[mysqld.exe]
TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING       1104
CryptSvc
[svchost.exe]
TCP    0.0.0.0:6901           0.0.0.0:0              LISTENING       4636
[WinVNC.exe]
TCP    0.0.0.0:6901           0.0.0.0:0              LISTENING       4636
[WinVNC.exe]
TCP    0.0.0.0:8300           0.0.0.0:0              LISTENING       3464
[sc_serv.exe]
TCP    0.0.0.0:8301           0.0.0.0:0              LISTENING       3464
[sc_serv.exe]
TCP    0.0.0.0:8360           0.0.0.0:0              LISTENING       3080
[sc_serv.exe]
TCP    0.0.0.0:8361           0.0.0.0:0              LISTENING       3080
[sc_serv.exe]
TCP    0.0.0.0:9022           0.0.0.0:0              LISTENING       4804
[VirtualBox.exe]
TCP    0.0.0.0:9023           0.0.0.0:0              LISTENING       4804
[VirtualBox.exe]
TCP    0.0.0.0:9080           0.0.0.0:0              LISTENING       4804
[VirtualBox.exe]
TCP    0.0.0.0:10001          0.0.0.0:0              LISTENING       4828
[VirtualBox.exe]
TCP    0.0.0.0:10002          0.0.0.0:0              LISTENING       4828
[VirtualBox.exe]
TCP    0.0.0.0:10003          0.0.0.0:0              LISTENING       4828
[VirtualBox.exe]
TCP    0.0.0.0:10011          0.0.0.0:0              LISTENING       4780
[VirtualBox.exe]
TCP    0.0.0.0:10012          0.0.0.0:0              LISTENING       4780
[VirtualBox.exe]
TCP    0.0.0.0:10013          0.0.0.0:0              LISTENING       4780
[VirtualBox.exe]
TCP    0.0.0.0:25566          0.0.0.0:0              LISTENING       3648
[TerrariaServer.exe]
TCP    0.0.0.0:30001          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30002          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30003          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30004          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30005          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30006          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30007          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30020          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30021          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30039          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30080          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30081          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30082          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30083          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30084          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30085          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30086          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30087          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30088          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30089          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30090          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30091          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30092          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30093          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30094          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30095          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30096          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30097          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30098          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30099          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30101          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30102          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30103          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30104          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30105          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30106          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30107          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30108          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30109          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30110          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30111          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30112          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30113          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30114          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30115          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30116          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30117          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30118          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30119          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30120          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30121          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30139          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30180          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30181          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30182          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30183          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30184          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30185          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30186          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30187          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30188          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30189          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30190          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30191          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30192          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30193          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30194          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30195          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30196          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30197          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30198          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30199          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30201          0.0.0.0:0              LISTENING       4796
[VirtualBox.exe]
TCP    0.0.0.0:30239          0.0.0.0:0              LISTENING       4796
[VirtualBox.exe]
TCP    0.0.0.0:33306          0.0.0.0:0              LISTENING       4796
[VirtualBox.exe]
TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING       440
[wininit.exe]
TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING       880
eventlog
[svchost.exe]
TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING       1000
Schedule
[svchost.exe]
TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING       508
[lsass.exe]
TCP    0.0.0.0:49157          0.0.0.0:0              LISTENING       500
[services.exe]
TCP    0.0.0.0:49158          0.0.0.0:0              LISTENING       3048
PolicyAgent
[svchost.exe]
TCP    127.0.0.1:8361         127.0.0.1:49364        ESTABLISHED     3080
[sc_serv.exe]
TCP    127.0.0.1:14147        0.0.0.0:0              LISTENING       1444
[FileZilla Server.exe]
TCP    127.0.0.1:14147        127.0.0.1:49162        ESTABLISHED     1444
[FileZilla Server.exe]
TCP    127.0.0.1:49162        127.0.0.1:14147        ESTABLISHED     3156
[FileZilla Server Interface.exe]
TCP    127.0.0.1:49212        127.0.0.1:49213        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49213        127.0.0.1:49212        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49214        127.0.0.1:49215        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49215        127.0.0.1:49214        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49216        127.0.0.1:49217        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49217        127.0.0.1:49216        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49218        127.0.0.1:49219        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49219        127.0.0.1:49218        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49220        127.0.0.1:49221        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49221        127.0.0.1:49220        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49222        127.0.0.1:49223        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49223        127.0.0.1:49222        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49224        127.0.0.1:49225        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49225        127.0.0.1:49224        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49226        127.0.0.1:49227        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49227        127.0.0.1:49226        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49364        127.0.0.1:8361         ESTABLISHED     3100
[Instore_Radioboss.exe]
TCP    192.168.1.87:139       0.0.0.0:0              LISTENING       4
Can not obtain ownership information
TCP    192.168.1.87:3389      217.156.134.12:22971   ESTABLISHED     1104
CryptSvc
[svchost.exe]
TCP    192.168.1.87:8360      81.148.248.221:1026    ESTABLISHED     3080
[sc_serv.exe]
TCP    192.168.1.87:25565     0.0.0.0:0              LISTENING       4288
[java.exe]
TCP    192.168.1.87:50644     37.139.0.151:8233      ESTABLISHED     4796
[VirtualBox.exe]
TCP    192.168.1.87:51019     81.27.96.46:21         TIME_WAIT       0
TCP    192.168.1.87:53126     192.168.1.86:445       ESTABLISHED     4
Can not obtain ownership information
TCP    192.168.1.87:60462     192.168.1.86:445       CLOSE_WAIT      4
Can not obtain ownership information
TCP    192.168.1.87:65029     37.139.0.151:8231      ESTABLISHED     4796
[VirtualBox.exe]
TCP    192.168.56.1:139       0.0.0.0:0              LISTENING       4
Can not obtain ownership information
TCP    [::]:21                [::]:0                 LISTENING
1444
[FileZilla Server.exe]
TCP    [::]:25                [::]:0                 LISTENING
1692
[MESMTPC.EXE]
TCP    [::]:80                [::]:0                 LISTENING
4
Can not obtain ownership information
TCP    [::]:135               [::]:0                 LISTENING
752
RpcSs
[svchost.exe]
TCP    [::]:445               [::]:0                 LISTENING
4
Can not obtain ownership information
TCP    [::]:3306              [::]:0                 LISTENING
1756
[mysqld.exe]
TCP    [::]:3389              [::]:0                 LISTENING
1104
CryptSvc
[svchost.exe]
TCP    [::]:30239             [::]:0                 LISTENING
4796
[VirtualBox.exe]
TCP    [::]:49152             [::]:0                 LISTENING
440
[wininit.exe]
TCP    [::]:49153             [::]:0                 LISTENING
880
eventlog
[svchost.exe]
TCP    [::]:49154             [::]:0                 LISTENING
1000
Schedule
[svchost.exe]
TCP    [::]:49156             [::]:0                 LISTENING
508
[lsass.exe]
TCP    [::]:49157             [::]:0                 LISTENING
500
[services.exe]
TCP    [::]:49158             [::]:0                 LISTENING
3048
PolicyAgent
[svchost.exe]
TCP    [::1]:14147            [::]:0                 LISTENING       1444
[FileZilla Server.exe]
UDP    0.0.0.0:123            *:*
964
W32Time
[svchost.exe]
UDP    0.0.0.0:500            *:*
1000
IKEEXT
[svchost.exe]
UDP    0.0.0.0:3702           *:*
964
EventSystem
[svchost.exe]
UDP    0.0.0.0:3702           *:*
964
EventSystem
[svchost.exe]
UDP    0.0.0.0:4500           *:*
1000
IKEEXT
[svchost.exe]
UDP    0.0.0.0:5355           *:*
1104
Dnscache
[svchost.exe]
UDP    0.0.0.0:53274          *:*
4780
[VirtualBox.exe]
UDP    0.0.0.0:53727          *:*
4788
[VirtualBox.exe]
UDP    0.0.0.0:54111          *:*
4828
[VirtualBox.exe]
UDP    0.0.0.0:54112          *:*
4828
[VirtualBox.exe]
UDP    0.0.0.0:54113          *:*
4780
[VirtualBox.exe]
UDP    0.0.0.0:55421          *:*
964
EventSystem
[svchost.exe]
UDP    0.0.0.0:58596          *:*
964
EventSystem
[svchost.exe]
UDP    0.0.0.0:59838          *:*
4812
[VirtualBox.exe]
UDP    0.0.0.0:62498          *:*
4796
[VirtualBox.exe]
UDP    127.0.0.1:1900         *:*
4172
SSDPSRV
[svchost.exe]
UDP    127.0.0.1:55045        *:*
4172
SSDPSRV
[svchost.exe]
UDP    192.168.1.87:137       *:*
4
Can not obtain ownership information
UDP    192.168.1.87:138       *:*
4
Can not obtain ownership information
UDP    192.168.1.87:1900      *:*
4172
SSDPSRV
[svchost.exe]
UDP    192.168.1.87:55043     *:*
4172
SSDPSRV
[svchost.exe]
UDP    192.168.56.1:137       *:*
4
Can not obtain ownership information
UDP    192.168.56.1:138       *:*
4
Can not obtain ownership information
UDP    192.168.56.1:1900      *:*
4172
SSDPSRV
[svchost.exe]
UDP    192.168.56.1:55044     *:*
4172
SSDPSRV
[svchost.exe]
UDP    [::]:123               *:*
964
W32Time
[svchost.exe]
UDP    [::]:500               *:*
1000
IKEEXT
[svchost.exe]
UDP    [::]:3702              *:*
964
EventSystem
[svchost.exe]
UDP    [::]:3702              *:*
964
EventSystem
[svchost.exe]
UDP    [::]:4500              *:*
1000
IKEEXT
[svchost.exe]
UDP    [::]:5355              *:*
1104
Dnscache
[svchost.exe]
UDP    [::]:55422             *:*
964
EventSystem
[svchost.exe]
UDP    [::]:58597             *:*
964
EventSystem
[svchost.exe]
UDP    [::1]:1900             *:*
4172
SSDPSRV
[svchost.exe]
UDP    [::1]:55042            *:*
4172
SSDPSRV
[svchost.exe]
UDP    [fe80::59f:484a:827f:42ba%11]:1900 *:*
4172
SSDPSRV
[svchost.exe]
UDP    [fe80::59f:484a:827f:42ba%11]:55040 *:*
4172
SSDPSRV
[svchost.exe]
UDP    [fe80::11a6:2283:bc40:c0cb%16]:1900 *:*
4172
SSDPSRV
[svchost.exe]
UDP    [fe80::11a6:2283:bc40:c0cb%16]:55041 *:*
4172
SSDPSRV
[svchost.exe]

10.2.8 client login issues with 10.3.9 server

Hi we have just updated our computer lab to 10.2.8 client computers and a 10.3.9 server but I am having issues with the client computer loging into the server I am using LDAPv3 and when I try to have a user login to the server from the client at the login screen I get the login window shake.I can login fine from a 10.3.9 client computer.Any advice would be appreciated.Thanks in advance

Check your 10.2.8 machines Directory Access and make sure LdapV2 is not checked and also that Ldap V3 is checked and configured correctly. I found that if I had both Ldapv2 and v3 on my 10.2.8 clients could not log in. 10.3 clients only have the option for Ldap V3, so it is not an issue.

I have installed the agent 10 or 15 times and one installation hasfailed, no error appeared during the installation but I am havinginconsistent issues with my ethernet card not working here and there. Werebooted and can log into Novell client but th

I have installed the agent 10 or 15 times and one installation has failed, no error appeared during the installation but I am having inconsistent issues with my ethernet card not working here and there. We rebooted and can log into Novell client but the login prompt did not appear for ESM client or the icon was not in the systray. Everything seems to work, besides at times (a couple times today) it terminates his ethernet card/connection. I would re-image his computer but he has several applications and it would take several hours, so I am hoping someone has an idea to fix this issue. So I was trying to figure out why he did not get the prompt to login and why it's not in the systray and it appears to not have completed the install? I checked the add/remove programs, its not listed within their, I also checked the registry and found nothing for endpoint within their, but the files are within c:\program files\novell\zenworks endpoint security.
I have also tried uninstalling it but that fails due to it "not being installed", and it will not reinstall over itself either.
I did notice that stuninstdrv.exe is running in task manager. Any help would be great...
Windows xp sp3
ESM 3.5.154
Thanks,
Andy

If you are searching the registry, check for the "Senforce" string. It should be at HKLM\Software\Senforce
Try running the install program for the ZSC with the following command line:
setup.exe /V"STUNINSTALL=1"
If you've specified an uninstall password, try this one instead:
setup.exe /V"STUNINSTALL=1 STUIP=password"" (please note the double quote at the end)
Let me know if that helped you.
Daniel
>>>
From: Andy_DeWees<[email protected] du>
To:novell.support.zenworks.endpoint-security-management
Date: 2/5/2009 12:52 PM
Subject: I have installed the agent 10 or 15 times and one installation hasfailed, no error appeared during the installation but I am havinginconsistent issues with my ethernet card not working here and there. Werebooted and can log into Novell client but the login prompt did not appearfor ESM client or the icon was not in the systray. Everything seems towork, besides at times (a couple times today) it terminates his ethernetcard/connection. I would re-image his computer but he has severalapplications and
I have installed the agent 10 or 15 times and one installation has failed, no error appeared during the installation but I am having inconsistent issues with my ethernet card not working here and there. We rebooted and can log into Novell client but the login prompt did not appear for ESM client or the icon was not in the systray. Everything seems to work, besides at times (a couple times today) it terminates his ethernet card/connection. I would re-image his computer but he has several applications and it would take several hours, so I am hoping someone has an idea to fix this issue. So I was trying to figure out why he did not get the prompt to login and why it's not in the systray and it appears to not have completed the install? I checked the add/remove programs, its not listed within their, I also checked the registry and found nothing for endpoint within their, but the files are within c:\program files\novell\zenworks endpoint security.
I have also tried uninstalling it but that fails due to it "not being installed", and it will not reinstall over itself either.
I did notice that stuninstdrv.exe is running in task manager. Any help would be great...
Windows xp sp3
ESM 3.5.154
Thanks,
Andy

FormCalc issues with Windows 7

Hi,
I am using FormCalc to check two date fields. The first one, the arrival date, should not be earlier than today's date. The second field, departure date, should not be earlier than the arrival date. The FormCalc is in the Exit event of the date field. It works perfectly fine in XP, but the validation is not working Windows 7.   The user does not get the pop up box at all and is able to submit the form with invalid dates. Does anyone know of an issue with FormCalc and Win 7??   It does not seems to be an issue with the Adobe Reader version. I tried with version 9.3.4 and XP and someone else with Adobe Reader 9.3.4 and Win 7 and the date validation did not work.
Here is my code:
Arrival Date:
form1.page1.main.travelInfo.arrDate::exit - (FormCalc, client)
if (Date2Num($.formattedValue, "MMMM D, YYYY") < Date()) then
    xfa.host.messageBox("Arrival Date must be later than the current date")
    $ = ""
endif
Daparture Date:
form1.page1.main.travelInfo.deptDate::exit - (FormCalc, client)
if (form1.page1.main.travelInfo.deptDate.rawValue < form1.page1.main.travelInfo.arrDate.rawValue) then
    xfa.host.messageBox("Departure Date must be later than the Arrival Date")
    $ = ""
endif
Thanks in advance!

radzmar - Thanks so much for your suggestion. I changed the code in the deptDate field to the above code, but the pop up box comes up no matter what date I choose, so it's not validating correctly.   The arrDate field works fine. Any thoughts?
Code from deptDate:
form1.page1.main.travelInfo.deptDate::exit - (FormCalc, client)
if
(Date2Num($.formattedValue, "MMMM D, YYYY") lt Date2Num(arrDate.formattedValue, "MMMM D, YYYY")) then
$host.messageBox("Departure Date must be later than the Arrival Date")
$
=
endif

Excel 2010 paper size issue with PCL6 drivers after KB2592687 installed on client

When I connect to the RDS server and open Excel with the PCL6 printer and select File / Print the paper size says Custom Paper Size and I can not change the paper size here, in the Page Layout tab or in the drivers properties pages. Using the PS driver there
is no issue. I've tried using several stock PCL6 drivers from Windows 7 and have the same issue such as the HP LaserJet P4014/4015 PCL6. Using the Lanier LP131n PCL6 or PS I had the issue with PS as well.
I do not have the drivers loaded on the server so it is using Remote Desktop Easy Print. If I do load the drivers and allow it to use them then there is no issue but I cannot configure the printers options without taking ownership of the printer so that
is not desirable.
If I do not install KB2592687 then there is no issue, but that is not an option as I am dealing with a customer who's IT manager refuses to remove this, even to test it, and says our printer driver has the issue and is not compliant with MS TS.
Could I be missing any configuration, hotfix, policy that could explain this issue or any other workaround? Or is there a change required to our printer driver for this?
Test setup:
I created a new Windows Server 2008 R2 Standard server with SP1, Added the RDS Role, Installed Office 2010 Professional with SP1 using the Terminal Services product key. No updates were installed. I have tested installing every possible update as well for
both Server and Office.
I then created a new Windows 7 Professional x86 with SP1 client, installed PCL6 & PS printers, installed KB2574819 and KB2592687. No other updates were installed. I have tested installing every possible update as well.

Hi,
Did you find any particular Event ID for your issue?
To troubleshoot this issue, have you tried changing the default printer and printing from other programs such as Word or any other?
The issue which you are facing might occurs because the Microsoft XPS Document Converter (MXDC) determines the paper size by using the FormID value on the server. As you commented that you are using Easy print driver first you can find incorrect paper size
if RD Easy Print printer driver first is enabled.
To work around this issue, use the forms that are defined by the system when you print. The paper sizes for these forms match on the server and on the client computer. Additionally, a printer driver can rename these forms. Please refer below article for more
information.
The client printer may print the documents by using an incorrect paper size if the "Use Remote Desktop Easy Print printer driver first" policy is enabled
Apart from this providing link to understand RD Easy print in Windows 7 & Server 2008 R2.
Hope it helps!
Thanks.

Labview 2012 Installer builder issues with Windows 7 64 bit

I have a clients project application program I am working on and am having a lot of trouble getting installed applications to work on Windows 7 properly. The Labview Installer sets the default installation directory to "c:\Program Files\" on Windows Xp and on Windows 7 64bit this defaults to "C:\Program Files (x86). When I install the application on Windows 7 and run it, because Windows 7 64 bit unreasonably protects this directory and every folder under it, if you try to write file to any subdirectory under it (like a reports directory), windows 7 will not let the file write to the directory and the file(s) disappear and you get permission errors. This has been difficult to address. Even logging in as administrator, I have difficulty changing the folder permissions. In addition, when I am in the file write process, if the default directory is coded to come up in the file Open/Save dialog, will not properly
go to and display these protected directories. So thinking that OK, I'll just chage the install directory to something direct to the C: drive and not the Program Files (x86) directory, so I have better control of the folder permissions. Now the Installer build gives errors. It built, but the install fails. Looks like National did not test this for Windows 7 very well. I have run into just about every issue possible with Windows 7 and Labview. Clearly Labview was not very well tested with Windows 7 6 bit. I do not have the Internet toolkit added to the application, only the VISA 5.2 driver. Anyone else having application issues with Labview and Windows 7 and have ideas how to work around this??
Attachments:
BuildErrors.txt ‏11 KB

It's no NI's fault and has nothing to do with 64 Bit either. It is something MS changed starting with Vista, namely tightening security of the whole system to a similar level as was usual on more professional OSes like Unix 20 years earlier. A user has not rights anymore to write into the location where applications are installed. This is for one reason to protect installed applications from being modified by malicious code.
Instead every application should write its runtime data in one of the user writable loacations such as the user's Documents directory for data files, or in the user's or the machine's configuration directory for configuration settings. For single installations you could always set the directory which your application got installed into to be user writable by changing the rights of that directory afterwards but for applications that get installed on normal user computers this is a VERY hacky and discouraged move. Same about installing your application into the root of your system drive. I think it was an oversight by MS to not protect that directory too from user modifications, but was most likely unavoidable to allow DOS application installations to still work.
LabVIEW has functions to retrieve a whole bunch of those preconfigured and user writeable locations and you really should change your application to make use of those locations, instead of trying to write into the installation directory or installing the application into the root location of the system drive, if you want to be compatible with Windows Vista/7/8.
Windows 7 also requires for a number of actions such as installing programs or drivers so called elevated rights. This means that even if you are logged in as administrator you have to explicitedly provide the admin password again to be able to perform the action. This can be done by starting the program as administrator, when this is available in the right click pop-up menu, and is also sometimes done automatically for applications that Windows determines to need those rights such as setup programs for installations.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Remote Desktop Client 8.1.3 Display Issue

We're running Microsoft Remote Desktop 2012R2 services including a Gateway/Connection Broker/Licensing server and Remote Desktop Session Hosts servers. Our clients include Windows systems, iPads and iPhones.
Since the upgrade to Microsoft Remote Desktop Client for IOS 8.1.3 (which fixed our gateway connection issues using the previous 8.1.x IOS clients), we're still unable to use our iPads with a published application that runs a time clock to check
children in/out of daycare centers.
When launching the published application, the display does not scale to full screen. A portion of the screen contains a black bar around the bottom and to the right of the window. The touch control needed is hidden by
the black bar. This issue did not exist in clients prior to 8.1.x nor does it exist in Windows clients.
Using the Pan Control does not resolve the issue. If you activate the Pan control, the application is so magnified that you only see about 1/4th of the upper left of the screen. Moving the window around or pinch to zoom in/out does not resolve
the issue.
Note that we have also published Microsoft Office 2010, Adobe Reader, Calculator and network share folders. None of these apps experience the issue with a black bar hiding a portion of the application window.
Any suggestions?

Hi Dharmesh - Yes, we did reinstall the RD 8.1.3 IOS client on our iPads a few times. And to answer your question, we are using a childcare software from the following company:
http://www.procaresoftware.com/
Microsoft Office 2010 as a published application appears to be functioning correctly with the iPads, although it hasn't been extensively tested. Most of our remote desktop Office users are on Windows 7 systems.
I've notified the Procare Software technical support team of this iPad issue and they forwarded the information on to their developers. They are releasing an updated version of their software some time in the next week. They have enhanced
the resizing / rotation support for tablets in the next upgrade release, but are unsure whether our iPad display issue will be resolved.
If the issue is not resolved by the upgrade, they suggest we seek a resolution from Microsoft. In the meantime, Procare stated that I could share this information with you. They're also copied on this forum to keep up with your comments.
Note: After we install the future upgrade of Procare Software, I'll report back here with the results.
Regards.

Issue with Windows mobile accessing to Controller web authenticate page

I have an issue with my customer that use Windows mobile that can't access the web authentication page in the WLC using IE. The error message that it display is "The page can not be found. Website can not be authenticated". When the browser is trying to load the "https://1.1.1.1/login.html". It is workable with opera browser on the same mobile phone. I have try to regenerated the certificate in the WLC but it does not help.
WLC model is 4404, firmware version :4.2. Any one have a solution to this?

In version 4.2 on the controller SSLv2 is disabled by default. IE by default doesn't do SSLv3. Either enable SSLv2 on the controller or SSLv3 on the client.

Facing issues with oracle client installation 32 bit 10.2.0.1

Hi ,
I am facing issues with oracle client installation 32 bit 10.2.0.1
Windows 2008 R2 enterprise edition 64 bit
Java 1.6 update 34
Below is the error recieved:
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x8079055
Function=[Unknown.]
Library=C:\Users\ADMINI~1\AppData\Local\Temp\2\OraInstall2013-08-22_02-41-00PM\jre\1.4.2\bin\client\jvm.dll
NOTE: We are unable to locate the function name symbol for the error
      just occurred. Please refer to release documentation for possible
      reason and solutions.
Current Java thread:
at oracle.sysman.oii.oiip.osd.win32.OiipwWin32NativeCalls.RegSetValue(Native Method)
at oracle.sysman.oii.oiip.osd.win32.OiipwWin32NativeCalls.RegSetValue(OiipwWin32NativeCalls.java:516)
at oracle.sysman.oii.oiip.osd.win32.OiipwWin32NativeCalls.RegSetValue(OiipwWin32NativeCalls.java:473)
at oracle.sysman.oii.oiip.oiipg.OiipgBootstrap.setInstallerKey(OiipgBootstrap.java:511)
at oracle.sysman.oii.oiip.oiipg.OiipgBootstrap.updateInventoryLoc(OiipgBootstrap.java:418)
at oracle.sysman.oii.oiic.OiicSessionInterfaceManager.doInvSetupOperations(OiicSessionInterfaceManager.java:401)
at oracle.sysman.oii.oiic.OiicInvSetupWCCE.doOperation(OiicInvSetupWCCE.java:217)
at oracle.sysman.oii.oiif.oiifb.OiifbCondIterator.iterate(OiifbCondIterator.java:171)
at oracle.sysman.oii.oiic.OiicPullSession.doOperation(OiicPullSession.java:1273)
at oracle.sysman.oii.oiic.OiicSessionWrapper.doOperation(OiicSessionWrapper.java:289)
at oracle.sysman.oii.oiic.OiicInstaller.run(OiicInstaller.java:547)
at oracle.sysman.oii.oiic.OiicInstaller.runInstaller(OiicInstaller.java:935)
at oracle.sysman.oii.oiic.OiicInstaller.main(OiicInstaller.java:872)
Dynamic libraries:
0x00400000 - 0x0040B000 C:\Users\ADMINI~1\AppData\Local\Temp\2\OraInstall2013-08-22_02-41-00PM\jre\1.4.2\bin\javaw.exe
0x77C60000 - 0x77DE0000 C:\Windows\SysWOW64\ntdll.dll
0x75AB0000 - 0x75BC0000 C:\Windows\syswow64\kernel32.dll
0x77420000 - 0x77467000 C:\Windows\syswow64\KERNELBASE.dll
0x77370000 - 0x77410000 C:\Windows\syswow64\ADVAPI32.dll
0x76610000 - 0x766BC000 C:\Windows\syswow64\msvcrt.dll
0x75DD0000 - 0x75DE9000 C:\Windows\SysWOW64\sechost.dll
0x776E0000 - 0x777D0000 C:\Windows\syswow64\RPCRT4.dll
0x757C0000 - 0x75820000 C:\Windows\syswow64\SspiCli.dll
0x757B0000 - 0x757BC000 C:\Windows\syswow64\CRYPTBASE.dll
0x77470000 - 0x77570000 C:\Windows\syswow64\USER32.dll
0x764F0000 - 0x76580000 C:\Windows\syswow64\GDI32.dll
0x77C30000 - 0x77C3A000 C:\Windows\syswow64\LPK.dll
0x75820000 - 0x758BD000 C:\Windows\syswow64\USP10.dll
0x74EA0000 - 0x74EEC000 C:\Windows\system32\apphelp.dll
0x6EF10000 - 0x6EF9D000 C:\Windows\AppPatch\AcLayers.DLL
0x76720000 - 0x7736A000 C:\Windows\syswow64\SHELL32.dll
0x761D0000 - 0x76227000 C:\Windows\syswow64\SHLWAPI.dll
0x76350000 - 0x764AC000 C:\Windows\syswow64\ole32.dll
0x75F30000 - 0x75FBF000 C:\Windows\syswow64\OLEAUT32.dll
0x74660000 - 0x74677000 C:\Windows\system32\USERENV.dll
0x74650000 - 0x7465B000 C:\Windows\system32\profapi.dll
0x74340000 - 0x74391000 C:\Windows\system32\WINSPOOL.DRV
0x74570000 - 0x74582000 C:\Windows\system32\MPR.dll
0x6E8B0000 - 0x6EAC8000 C:\Windows\AppPatch\AcGenral.DLL
0x6EFA0000 - 0x6F020000 C:\Windows\system32\UxTheme.dll
0x6F060000 - 0x6F092000 C:\Windows\system32\WINMM.dll
0x74840000 - 0x7484F000 C:\Windows\system32\samcli.dll
0x6F0D0000 - 0x6F0E4000 C:\Windows\system32\MSACM32.dll
0x74C80000 - 0x74C89000 C:\Windows\system32\VERSION.dll
0x6F340000 - 0x6F343000 C:\Windows\system32\sfc.dll
0x6F260000 - 0x6F26D000 C:\Windows\system32\sfc_os.DLL
0x6F040000 - 0x6F053000 C:\Windows\system32\dwmapi.dll
0x758C0000 - 0x75A5D000 C:\Windows\syswow64\SETUPAPI.dll
0x75C90000 - 0x75CB7000 C:\Windows\syswow64\CFGMGR32.dll
0x77570000 - 0x77582000 C:\Windows\syswow64\DEVOBJ.dll
0x75DF0000 - 0x75F27000 C:\Windows\syswow64\urlmon.dll
0x775A0000 - 0x77695000 C:\Windows\syswow64\WININET.dll
0x75FD0000 - 0x761CF000 C:\Windows\syswow64\iertutil.dll
0x76230000 - 0x7634E000 C:\Windows\syswow64\CRYPT32.dll
0x75FC0000 - 0x75FCC000 C:\Windows\syswow64\MSASN1.dll
0x6F0C0000 - 0x6F0C6000 C:\Windows\system32\SHUNIMPL.DLL
0x6F030000 - 0x6F03D000 C:\Windows\system32\SortServer2003Compat.dll
0x75CC0000 - 0x75D20000 C:\Windows\system32\IMM32.DLL
0x75BC0000 - 0x75C8C000 C:\Windows\syswow64\MSCTF.dll
0x08000000 - 0x08138000 C:\Users\ADMINI~1\AppData\Local\Temp\2\OraInstall2013-08-22_02-41-00PM\jre\1.4.2\bin\client\jvm.dll
0x10000000 - 0x10007000 C:\Users\ADMINI~1\AppData\Local\Temp\2\OraInstall2013-08-22_02-41-00PM\jre\1.4.2\bin\hpi.dll
0x003F0000 - 0x003FE000 C:\Users\ADMINI~1\AppData\Local\Temp\2\OraInstall2013-08-22_02-41-00PM\jre\1.4.2\bin\verify.dll
0x007B0000 - 0x007C9000 C:\Users\ADMINI~1\AppData\Local\Temp\2\OraInstall2013-08-22_02-41-00PM\jre\1.4.2\bin\java.dll
0x007D0000 - 0x007DE000 C:\Users\ADMINI~1\AppData\Local\Temp\2\OraInstall2013-08-22_02-41-00PM\jre\1.4.2\bin\zip.dll
0x051D0000 - 0x052E2000 C:\Users\Administrator\AppData\Local\Temp\2\OraInstall2013-08-22_02-41-00PM\jre\1.4.2\bin\awt.dll
0x052F0000 - 0x05341000 C:\Users\Administrator\AppData\Local\Temp\2\OraInstall2013-08-22_02-41-00PM\jre\1.4.2\bin\fontmanager.dll
0x6E7C0000 - 0x6E8A7000 C:\Windows\system32\ddraw.dll
0x6F020000 - 0x6F026000 C:\Windows\system32\DCIMAN32.dll
0x75DA0000 - 0x75DCD000 C:\Windows\syswow64\WINTRUST.dll
0x6E6F0000 - 0x6E7BC000 C:\Windows\system32\D3DIM700.DLL
0x05770000 - 0x05793000 C:\Users\Administrator\AppData\Local\Temp\2\OraInstall2013-08-22_02-41-00PM\jre\1.4.2\bin\JavaAccessBridge.dll
0x007E0000 - 0x007E5000 C:\Users\Administrator\AppData\Local\Temp\2\OraInstall2013-08-22_02-41-00PM\jre\1.4.2\bin\jawt.dll
0x007F0000 - 0x007F7000 C:\Users\Administrator\AppData\Local\Temp\2\OraInstall2013-08-22_02-41-00PM\jre\1.4.2\bin\JAWTAccessBridge.dll
0x06340000 - 0x06359000 C:\Users\Administrator\AppData\Local\Temp\2\OraInstall2013-08-22_02-41-00PM\oui\lib\win32\oraInstaller.dll
0x06470000 - 0x0648E000 C:\Users\Administrator\AppData\Local\Temp\2\OraInstall2013-08-22_02-41-00PM\jre\1.4.2\bin\jpeg.dll
0x776B0000 - 0x776DA000 C:\Windows\syswow64\imagehlp.dll
0x6E600000 - 0x6E6EB000 C:\Windows\syswow64\dbghelp.dll
0x776A0000 - 0x776A5000 C:\Windows\syswow64\PSAPI.DLL
Heap at VM Abort:
Heap
def new generation   total 704K, used 90K [0x10010000, 0x100d0000, 0x10770000)
eden space 640K, 13% used [0x10010000, 0x10026448, 0x100b0000)
from space 64K,   2% used [0x100c0000, 0x100c07a8, 0x100d0000)
to   space 64K,   0% used [0x100b0000, 0x100b0000, 0x100c0000)
tenured generation   total 8436K, used 5698K [0x10770000, 0x10fad000, 0x16010000)
   the space 8436K, 67% used [0x10770000, 0x10d00a40, 0x10d00c00, 0x10fad000)
compacting perm gen total 12288K, used 12049K [0x16010000, 0x16c10000, 0x1a010000)
   the space 12288K, 98% used [0x16010000, 0x16bd47a0, 0x16bd4800, 0x16c10000)
Local Time = Thu Aug 22 14:42:03 2013
Elapsed Time = 40
# HotSpot Virtual Machine Error : EXCEPTION_ACCESS_VIOLATION
# Error ID : 4F530E43505002EF
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Java VM: Java HotSpot(TM) Client VM (1.4.2_08-b03 mixed mode)
Thanks

10.2.0.1 is not supported/certified on Win 2008, so expect issues with the install and/or with using the software.
Why cannot you use a supported version - minimum is 10.2.0.4, which is only available to customers with an Extended Support contract
http://docs.oracle.com/cd/B19306_01/relnotes.102/b14264/toc.htm#BABGFAJI
HTH
Srini

NAC Windows Client 4.9.3.5 issues with windows 8

Similar Messages

Maybe you are looking for