Linux client - cannot connect to JServer

Server with database - Oracle 8.1.7 on Windows 2000
Client - Linux RedHat 7.2
When I trying to connect to JServer using sess_sh:
sess_sh -u arseniy -p mypasswd -s sess_iiop://199.58.1.113:2481:orcl
I get this error message:
javax.naming.CommunicationException: Unknown service: :session1 [Root exception is javax.naming.CommunicationException: Unknown service: 199.58.1.113:2481:orcl]
When I try to use DBAStudio, I get something like this:
VDJSERVER-1516: Failed to get a new JServer session.Unknown service::OEM0
The most incomprehensible thing is that if I reboot my client to Windows 2000, it works, in other words - the file LISTENER.ORA on the server seems to be correct.
So why I cannot work with JServer under Linux!?
Thank you in advance...

I uninstalled the
http://support.microsoft.com/kb/2574819
and it resumed working for me as well as I had exactly the same issue here.
there is a point though: removing this KB removes the UDP connection capability of RDP 8.0; arguably the most significant breakthrough the RDP 8 has to offer. shouldn't it be addresses and the problem handled in a better way?
if RDS Team claim that they've brought all the "adaptive network", "adaptive graphics" , "WAN enhancement" and etc to Windows 7 with the RDP 8 update(see links below), then shouldn't it be as available and as glitch-free as
it is with a windows 8 VM?
basically it is unacceptable to force the client to turn off the "automatic determine" feature ; either manually or through the RD-ConnectionBroker tweak of the following link (Jeroen Link):
http://support.microsoft.com/kb/2863663
because if it is a supported feature, it has to be supported without IFs and BUTs. this is definitely a bug that needs to be addresses.
RDP 8 for windows 7 links:
http://support.microsoft.com/kb/2592687
http://blogs.msdn.com/b/rds/archive/2012/10/09/remote-desktop-protocol-8-0-update-for-windows-7-sp1-enabling-a-great-wan-user-experience-for-windows-7-sp1-virtual-desktops.aspx
another thing I noticed : with RDP 8 features enabled, you don't get the event ID 2 as this link suggests anymore:
http://technet.microsoft.com/en-us/library/ff817587
maybe you'll get event 34 as this one says. but I am not quite sure:
http://social.technet.microsoft.com/wiki/contents/articles/16652.remotefx-vgpu-setup-and-configuration-guide-for-windows-server-2012.aspx
P.S. I am using 2012R2 Hyper-V and it does have this problem as well, so I don't think that compatibility roll up update will help.

Similar Messages

  • 8.8 Client cannot connect to Windows Server 2008 error -1102

    SAP Business On 8.8 on PL 18
    This is not the first time I have had this issue with Windows Server 2008.
    however everytime the resolution was diffrent. Now this site is causing trouble.
    The issue is the client cannot connect. We have the log on window, can see the company list. type on the password and we get a -1102 error.
    The client on the Server itself can log on. It is the cleints that cannot.
    I checked these below.
    1 SQL Native client is installed and ok.
    2. Licence server is configured and ok
    3. The user has admin access to locl PC
    4. The SAP user name and password are correct ( client on server can connect fine )
    5. The ports 1433, 30000 and 30001 are open on the server.
    6. Through SQL server configuration the named pipes and TCP are enabled.
    7. SQL server browser is running
    The only things I have not tried are
    The Firewall is running on the server and I have not yet stopped it. Will try that tomorrow.
    Do you have any other ideas please ?

    I have got this working but I am not confidant of the outcome  - yet  - I really need your expert advise here.
    This is what I did. In that order.
    1.     As Owen suggested I checked if there was a specified Port for the instance.  What I found was TCP Dynamic  ports were enabled (  SQL server config manager | network configuration | tcp properties ) and there was no TCP port specified.  Assuming ( ai may be wrong) that the system assigns a dynamic port to this instance  I set it up so the Dynamic port does not happen and manually specified the Port  1433. Restarted the SQL Service. ( still having the Port 1433 open in the firewall). This did not solve the issue.
    2.     With the above setting still on, switched off the firewall. Went to the PC client and SAP can log on now.  Now keeping the SAP client running, switched on the Firewall on the server. Log off SAP on PC client and log back in ( with firewall off ). SAP now can log on.
    3.     I had to do the above step for all PCs to get them working.
    4. Currently the firewall is on and clients can connect
    So what could be happening? I have no clue. It is apparent there is some setting that gets saved within the PCs ( may be user profile) after the first log on with the Firewall off  - to say its safe ?
    However I have no idea what will happen if the server is restarted u2013 this server we cannot restart any time we want as itu2019s a critical server and runs other things. 
    I would still like to get to the bottom of this to understand what is happening.
    I have a SAP message running too and will ask them this same question.

  • ODI Client cannot connect the datebase after the datebase IP changed

    ODI Client cannot connect the datebase after the datebase IP changed.
    1,the datebase on mac A,the mac changed ip
    2,on the client, tnsping db is ok.
    3,use pl/sql ,can connect on the db
    4,with odi,changed the repostry URL to the new db IP,throw the exception below
    java.sql.SQLException: Io Exception: The Network Adapter could not establish the connection
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:274)
         at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:328)
         at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:361)
         at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:151)
         at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:595)
         at com.sunopsis.sql.SnpsConnection.u(SnpsConnection.java)
         at com.sunopsis.sql.SnpsConnection.c(SnpsConnection.java)
         at com.sunopsis.sql.h.run(h.java)
    Is anything we need to config after change db machine IP?

    yeah,I got it.Everything is ok now.
    After change IP,we must open TopologyManager:change the JDBC connection of workrepository which must chose in Designer.
    when we open the Designer ,it will connect to db.then coonect to workrepository with original IP.So,we must rechange workrepository's JDBC first!

  • New-Pssession client cannot connect to the destination specified

    I've used the following cmdlets to connect powershell to our tenant for months and now I cannot open a possession with the same commands.
    I've searched on some of the error text show below without any great progress. We have a pair of Hybrid servers and we get the same result on either.
    Any suggestions are appreciated.
    Bruce
    Import-module msonline
    $O365Cred = Get-Credential
    $O365Session = New-PSSession –ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $O365Cred -Authentication Basic -AllowRedirection
    Import-PSSession $O365Session
    Connect-MsolService –Credential $O365Cred
    [email protected]
    working password at the MicrosoftOnline Portal
    $O365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $O365Cred -Authentication Basic –AllowRedirection
    WARNING: Your connection has been redirected to the following URI:
    https://pod51038psh.outlook.com/powershell-liveid?PSVersion=4.0
    New-PSSession : [pod51038psh.outlook.com] Connecting to remote server pod51038psh.outlook.com failed with the following error message : The client cannot connect to the destination specified
    in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service,
    run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic.
    + $O365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUr ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
    Import-PSSession $O365Session
    Import-PSSession : Cannot validate argument on parameter 'Session'. The argument is null. Provide a valid value for the argument, and then try running the command again.
    At line:1 char:18
    + Import-PSSession $O365Session
    +                 
    ~~~~~~~~~~~~
    + CategoryInfo         
    : InvalidData: (:) [Import-PSSession], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.ImportPSSessionCommand
    Connect-MsolService -Credential $O365Cred

    You are using the outdated URI string, which is known to cause problems. Should be: https://outlook.office365.com/powershell-liveid/
    Just follow the instructions in the TechNet article:
    https://technet.microsoft.com/en-us/library/jj984289(v=exchg.150).aspx

  • The client cannot connect to the server

    we just installed the boe but found that the client cannot connect to the server.
    server: windows server 2008
                 boe xi3
    client:    window xp sp3
    the server and client are in same dns
    all components are work in server but client.
    any idea on this?
    ps: i can ping the server name successful.
    thanks
    ada
    Edited by: Ada_Wei on Oct 29, 2010 10:12 AM

    Can you please try to stop and disable the Windows firewall service on your client machine?
    WHich client do you use and which error message do you get exactly?
    Regards,
    Stratos

  • Windows VNC clients cannot connect to Snow Leopard Server native VNC server

    I am resurfacing the following related comment made in another post that discusses the same issue I am having with VNC on Snow Leopard. This is still an issue and I cannot connect to our Xserve's Snow Leopard Server with a VNC client on Windows.
    I don't want to install another third party VNC server onto our SL Server, and am looking for a VNC client for windows that will connect to our SL Server.
    Does anyone have any solutions?
    == QUOTED TEXT BELOW ==
    Re: Newbie: Connect Windows -> OSX Server
    Posted: Nov 4, 2009 9:26 AM in response to: Antonio Rocco
    I would politely disagree. Yes, definitely, the Mac 'Screen Sharing' app works a treat, and Apple Remote Desktop.app works as well, but I am coming from a Window's PeeCee.
    For me, connecting to my 10.5(.8) Server via tightvnc gives 'Server did not offer supported security type!". Using RealVNC to this machine states "No matching security types Do you wish to reconnect to ... ?" a telnet to this AppleVNCServer service (port 5900), shows RFB 003.889 *, or Remote Frame Buffer Major 3, minor 889.
    Also, connecting to multiple 10.6(.1) Clients with Tightvnc correctly asks for a password but then hangs at "Status: Security type requested". Using RealVNC opens, connects, asks for authentication, and exits. Telneting to this AppleVNCServer service (port 5900), also shows RFB 003.889 *.
    The Current Version of the protocol is supposed to be 3.8, that is Major version 3, minor version 8. Not 80 or 800 but Eight). http://www.realvnc.com/docs/rfbproto.pdf and I believe that tightvnc only supports up to version 3.7.
    On each station I have installed the 'old' OSXVnc.app as a service (to a unique port). OSXVnc utilizes protocol 3.3 and I can control them successfully, but that is of my own doing because of this issue.
    Now JollysFastVNC works a treat to any machine I have EVER tried to connect to. I have not tried COTVNC or any of the others (too slow for me, when they wer e around)
    Also, I just noticed that RealVNC states that their free and personal version will not connect to Mac OSX (x86 and PPC) but the Enterprise one will. I just Dl'ed the Enterprise Viewer and it gave essentially the same thing ('protocol is not valid' message, even after it asks for a password). Anyway, I am not here to hijack this thread, just trying to keep the info flowing and open.
    Maybe I am the only one with these problems but the bottom line is I cannot use Real or Tight, or UltraVNC to administer my server or clients as long as AppleVNCServer gives out the 003.889 protocol version.
    Peter
    * The ProtocolVersion message consists of 12 bytes interpreted as a string of ASCII characters in the format "RFB xxx.yyy\n" where xxx and yyy are the major and
    minor version numbers, padded with zeros.

    Searching on the net brought me to the same solution that Mr. Hoffman found as well, I was a bit skeptical at first but since he recommended it, and all my other attempts failed, it was a last resort and I have some additional notes of my own for a successful solution. Read the two links below first before doing anything, as they contribute to the solution in tandem.
    http://forums.macrumors.com/showpost.php?p=7221295&postcount=20
    http://forums.macrumors.com/showpost.php?p=9081641&postcount=28
    I should probably just create an entirely new post with all of the steps that worked for me, but it's rather straightforward nonetheless.

  • Win XP Client Cannot Connect to Mac OS X 10.4.4 Server but Win 2000 Can

    Anyone run into this problem? Just basic Apple/Windows stand alone, no domain or interaction with other Windows Servers. User can log on fine with Windows 2000 client, but same user cannot connect with Windows XP client on same network.
    Any workarounds out there?
    Mac G4 MDD, 1GB RAM, 80MB main drive, 400GB data Mac OS X (10.4.4)

    I had trouble with a WinXP client a while back, and
    only vaguely rememeber things I did to fix it. I'm
    thinking it's the Win system, not the Mac. On the win
    machine, try deselecting the box "Enable IEEE 802.1x
    authen. for this network" in the Properties >
    Authentication tab for your network
    interface.
    Thank you for the suggestion. It worked!

  • 6.1 Client cannot connect 6.5 Server?

    We have two versions of Essbase Server. One is 6.1 and the other is 6.5. We want to connect both server using only one set of client software. I cannot connect to 6.1 server using 6.5 client software, it said version problem or something like this. When I connect 6.5 Server using 6.1 client software, I cannot connect the server at all, it said tcp/ip problem. I can ping or telnet to the server OS. Is it possible for me to connect both 6.1 and 6.5 server using the same client software?

    Generally, client software is "forwards compatible" meaning an older client can usually connect to an older server. The reverse is not true, unless you are on Essbase 6.2 or greater (the Essbase 6.5 API can talk down to a 6.2 server, but not any older).When clients are looking to upgrade, I tell them that - but in the same sentence recommend keeping client software on the same version/patch as the Essbase server. Issues like the one you are having illustrate the types of issues you can encounter - and Hyperion will just tell you to use the proper client version.That aside - one thing to check for - Essbase 6.5 allows a DBA to change the listening port of the server. The default is 1423, which the 6.1 client will try to connect to. Make sure the 6.5 server listening port has not been changed (you have to set up the parameters, so it won't just happen for no reason).Regards,Jade------------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

  • External Clients cannot connect to Exchange Server

    Hello all:
    My external clients using outlook cannot connect to Exchange Server 2013.  We have on-presmise version updated to Cu3 and after the Cu3 update we lost connectivity with Outlook clients.  Many of the settings in IIS were changed after the Cu3 update,
    I noticed after my http->https redirect was not applied anymore to the default website.  Here is my Get-OutlookAnywhere results:
    RunspaceId                         : 6379fab1-f692-484f-8118-99e48330d4c4
    ServerName                         : EXCHSERV
    SSLOffloading                      : True
    ExternalHostname                   : mail.domain.com
    InternalHostname                   : mail.domain.com
    ExternalClientAuthenticationMethod : Negotiate
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic}
    XropUrl                            :
    ExternalClientsRequireSsl          : True
    InternalClientsRequireSsl          : True
    MetabasePath                       : IIS://EXCHSERV.domain.com/W3SVC/1/ROOT/Rpc
    Path                               : D:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
    ExtendedProtectionTokenChecking    : None
    ExtendedProtectionFlags            : {}
    ExtendedProtectionSPNList          : {}
    AdminDisplayVersion                : Version 15.0 (Build 775.38)
    Server                             : EXCHSERV
    AdminDisplayName                   :
    ExchangeVersion                    : 0.20 (15.0.0.0)
    Name                               : Rpc (Default Web Site)
    DistinguishedName                  : CN=Rpc (Default Web
                                         Site),CN=HTTP,CN=Protocols,CN=EXCHSERV,CN=Servers,CN=Exchange Administrative
                                         Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=domain,CN=Microsoft
                                         Exchange,CN=Services,CN=Configuration,DC=domain,DC=com
    Identity                           : EXCHSERV\Rpc (Default Web Site)
    Guid                               : 596ed7a1-ceec-4a36-9cbc-617ac5214463
    ObjectCategory                     : domain.com/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
    ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
    WhenChanged                        : 12/23/2013 2:20:41 AM
    WhenCreated                        : 11/25/2013 2:51:36 PM
    WhenChangedUTC                     : 12/23/2013 7:20:41 AM
    WhenCreatedUTC                     : 11/25/2013 7:51:36 PM
    OrganizationId                     :
    OriginatingServer                  : DOMAINCONTROLLER.domain.com
    IsValid                            : True
    ObjectState                        : Changed
    Thanks in advance

    Hi,
    According to your description, users cannot connect to Exchange server 2013 both internal and external.
    Please run Test E-mail AutoConfiguration in Outlook to check your autodiscover service. Also
    reset your Exchange virtual directory to connect correctly. If the issue still continues after all configurations are setting properly, collect some Event logs would be helpful.
    If there is any question, please post the results here for further analysis.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Clients cannot connect using afp running lion 10.7.1, worked ok before upgrade from 10.7 to 10.7.1

    I am running a macminiserver on ahome newtwork.  Original running snow leopard and then upgraded to 10.7 lion on all machine and everything was working fine.  Clients coul connected to shared drives on the server using afp.  However, after upgrading to 10.7.1 on the server and client machines, they can no lnger connect to the drives using afp, however you can connect using smb.
    I ahve tried stopping and starting the afp server, rebuilding permissions on the server - still cannot connect using afp.
    Any ideas?

    Be sure the correct Lion afp port is open on your router, even if you are using an Airport (port 548 tcp). Just do a search on "Mac OS X Lion ports".
    Also, if this is outside of the network, use the full server name in the Finder's Connect to Server, afp://server.com; when it prompts for a username, enter your first name and last name (not your short name) and then you also need to enter your password. If you don't have a fqdn, then you can use the static ip for "server.com"
    It should work, working for me inside and outside of the network. Admittedly, I don't think you need the port on the router for internal use, but you can test both ways.
    When working outside of the network a vpn is not required.

  • 10.5 clients cannot connect via AFP to 10.4.11 server

    Server : xServe running 10.4.11
    Login with AFP is successful with
    Clients:
    all 10.6.x
    all 10.4.x
    Login fails ( or more accurately never produces a login dialog window,
    just get a "Connecting to afp://x.x.x.x" message with barber pole
    progress bar ) with any 10.5.x client ( workstation or server )
    There is another 10.4.11 server in this network that allows 10.4, 10.6
    and 10.5 clients to connect without issues.
    Any ideas?
    Thanks

    The server uses both OD accounts and Local, but mainly the logins are local accounts on the server. Cannot login with either one - but it is definitely limited to just clients logging in from 10.5 workstations or servers... The same accounts can login fine from 10.4 or 10.6 machines. Seems to be a config problem limited to this 10.4.11 server. But have no idea what it could be. I have another 10.4.11 server that does not have this issue.

  • Macbook clients cannot connect to Windows Server 2008 RRAS with L2TP/IPSec

    Hi everyone,
    I had installed "Remote and Routing Access" or a VPN server on Windows Server 2008. The connection type set up is L2TP/IPSec. All the Windows clients can connect to the L2TP/IPSec VPN server without problem but Macbook users are facing problem.
    The Macbook users got the error message "The L2TP-VPN server did not respond. Try reconnecting. If the problem continues, verify your settings and contact your Administrator."
    I think it is something related to the pre-shared key encryption but I am not sure. The Macbook users could connect if the connection type is changed to PPTP on server and clients side. I searched for similar problems and solutions online but no luck, I couldn't find solution that helps. I found this is a common problem faced by many macbook users.
    Does anyone have a solution or suggestion for this, please? I appreciate all the helps and suggestion given.
    Thanks,
    CK

    Hi,
    Thanks for the question, however, this forum is for Remote Desktop Clients related questions.
    Regarding the issue, as Windows clients can connect with no problem, I suspect that it is a Mac side issue and I would like to suggest you contact Apple support for help.
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • Clients cannot connect to WSUS Server

    Hi there,
    I have a Server 2012 with the WSUS feature installed. I successfully synchronised with Microsoft to download the updates. After that, I managed to add two clients (Win 8 and 8.1 respectively) into WSUS. 
    The next day, both clients lost connection with WSUS and returns 80072EE2 and 80248440 errors. 
    Could someone help me with this?
    Regards,
    Vinod

    Hi Vinod,
    The 80072EE2 means  ERROR_INTERNET_TIMEOUT.
    Please check if the client can access the WSUS server on TCP port 8530.
    Also, please check if client has configured to update from WSUS server. We can verify this by check the registry below,
    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
    Here is the screenshot of lab server,
    Besides, if it is possible, please post the windowsupdate.log of the client here. It may give some hints.
    Best Regards.
    Steven Lee
    TechNet Community Support

  • Windows Client cannot connect to wireless LAN through EAP-TLS

    I have a Cisco Aironet Access point which cannot be authenticated by a remote RADIUS server to connect to wireless lan through EAP-TLS. These is the debug output from the AAA process.
    *Mar  7 10:56:56.337: dot11_auth_dot1x_start: in the dot11_auth_dot1x_start
    *Mar  7 10:56:56.369: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:56:56.385: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:56:56.385: dot11_auth_parse_client_pak: id is not matching req-id:1re
    sp-id:2, waiting for response
    *Mar  7 10:56:56.401: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:56:56.717: dot11_auth_dot1x_parse_aaa_resp: Received server response:
    GET_CHALLENGE_RESPONSE
    *Mar  7 10:56:56.717: dot11_auth_dot1x_parse_aaa_resp: found eap pak in server r
    esponse
    *Mar  7 10:56:56.785: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:56:57.097: dot11_auth_dot1x_parse_aaa_resp: Received server response:
    GET_CHALLENGE_RESPONSE
    *Mar  7 10:56:57.097: dot11_auth_dot1x_parse_aaa_resp: found eap pak in server r
    esponse
    *Mar  7 10:56:57.101: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:56:57.393: dot11_auth_dot1x_parse_aaa_resp: Received server response:
    GET_CHALLENGE_RESPONSE
    *Mar  7 10:56:57.393: dot11_auth_dot1x_parse_aaa_resp: found eap pak in server r
    esponse
    *Mar  7 10:56:57.397: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:56:57.673: dot11_auth_dot1x_parse_aaa_resp: Received server response:
    GET_CHALLENGE_RESPONSE
    *Mar  7 10:56:57.673: dot11_auth_dot1x_parse_aaa_resp: found eap pak in server r
    esponse
    *Mar  7 10:56:57.677: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:56:57.953: dot11_auth_dot1x_parse_aaa_resp: Received server response:
    GET_CHALLENGE_RESPONSE
    *Mar  7 10:56:57.953: dot11_auth_dot1x_parse_aaa_resp: found eap pak in server r
    esponse
    *Mar  7 10:56:57.957: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:56:58.317: dot11_auth_dot1x_parse_aaa_resp: Received server response:
    GET_CHALLENGE_RESPONSE
    *Mar  7 10:56:58.317: dot11_auth_dot1x_parse_aaa_resp: found eap pak in server r
    esponse
    *Mar  7 10:56:58.321: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:56:58.685: dot11_auth_dot1x_parse_aaa_resp: Received server response:
    GET_CHALLENGE_RESPONSE
    *Mar  7 10:56:58.685: dot11_auth_dot1x_parse_aaa_resp: found eap pak in server r
    esponse
    *Mar  7 10:56:58.685: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:56:58.993: dot11_auth_dot1x_parse_aaa_resp: Received server response:
    GET_CHALLENGE_RESPONSE
    *Mar  7 10:56:58.993: dot11_auth_dot1x_parse_aaa_resp: found eap pak in server r
    esponse
    *Mar  7 10:56:59.041: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:57:01.077: Client 0811.9650.8cb0 failed: reached maximum retries
    *Mar  7 10:57:08.997: %RADIUS-4-RADIUS_DEAD: RADIUS server 165.72.12.12:1812,181
    3 is not responding.
    *Mar  7 10:57:08.997: %RADIUS-4-RADIUS_ALIVE: RADIUS server 165.72.12.12:1812,18
    13 is being marked alive.
    *Mar  7 10:57:14.481: dot11_auth_dot1x_start: in the dot11_auth_dot1x_start
    *Mar  7 10:57:14.521: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:57:44.521: %DOT11-7-AUTH_FAILED: Station 0811.9650.8cb0 Authenticatio
    n failed
    *Mar  7 10:57:44.801: dot11_auth_dot1x_start: in the dot11_auth_dot1x_start
    *Mar  7 10:57:44.829: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:58:14.829: %DOT11-7-AUTH_FAILED: Station 0811.9650.8cb0 Authenticatio
    n failed
    *Mar  7 10:58:15.105: dot11_auth_dot1x_start: in the dot11_auth_dot1x_start
    *Mar  7 10:58:15.141: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:58:45.141: %DOT11-7-AUTH_FAILED: Station 0811.9650.8cb0 Authenticatio
    n failed
    *Mar  7 10:58:45.425: dot11_auth_dot1x_start: in the dot11_auth_dot1x_start
    *Mar  7 10:58:45.449: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:59:15.449: %DOT11-7-AUTH_FAILED: Station 0811.9650.8cb0 Authenticatio
    n failed
    *Mar  7 10:59:15.729: dot11_auth_dot1x_start: in the dot11_auth_dot1x_start
    *Mar  7 10:59:15.753: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:59:45.753: %DOT11-7-AUTH_FAILED: Station 0811.9650.8cb0 Authenticatio
    n failed
    *Mar  7 10:59:46.009: dot11_auth_dot1x_start: in the dot11_auth_dot1x_start
    *Mar  7 10:59:46.037: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:59:50.077: Client 0811.9650.8cb0 failed: reached maximum retries
    *Mar  7 10:59:50.349: dot11_auth_dot1x_start: in the dot11_auth_dot1x_start
    *Mar  7 10:59:50.373: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 10:59:55.077: Client 0811.9650.8cb0 failed: reached maximum retries
    *Mar  7 10:59:55.341: dot11_auth_dot1x_start: in the dot11_auth_dot1x_start
    *Mar  7 10:59:55.361: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 11:00:00.077: Client 0811.9650.8cb0 failed: reached maximum retries
    *Mar  7 11:00:00.333: dot11_auth_dot1x_start: in the dot11_auth_dot1x_start
    *Mar  7 11:00:00.357: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 11:00:05.077: Client 0811.9650.8cb0 failed: reached maximum retries
    *Mar  7 11:00:05.341: dot11_auth_dot1x_start: in the dot11_auth_dot1x_start
    *Mar  7 11:00:05.365: dot11_auth_parse_client_pak: Received EAPOL packet from 08
    11.9650.8cb0
    *Mar  7 11:00:10.077: Client 0811.9650.8cb0 failed: reached maximum retries

    Kindly get verified the configuration and the compatibility if there is a mismatch. Please find the link below for more information on EAP-TLS functions in Access points and clients.
    http://www.cisco.com/en/US/products/sw/secursw/ps2086/products_white_paper09186a008009256b.shtml#wp39110

  • Outlook clients cannot connect Exchange 2013 cutover from 2010

    Hello,
    My company has been running an Exchange 2013/2010 coexistence. Currently, Exch 2013 (2mbx and 1 CAS) utilizes "mail2.domain.com" for the name space. Exch 2010 (1MBX 1 CAS) uses "mail.domain.com"
    We recently attempted to cutover external and internal DNS to point "mail.domain.com" and "autodiscover.domain.com" to the Exch 2013 server. 
    We changed all virtual directories on 2013 to use "https://mail.domain.com/owa" (ECP, EWS, etc. were changed too) for the internal and external URL. The Exch 2010 virtual directories internal URL are set to "https://internalFQDN.domain.com/owa"
    the external URLs are $null
    Both CAS servers were setup to use Outlook Anywhere since this is how 2013 proxies to 2010. The internal URLs for both were set to "mail.domain.com" IIS authentication Methods (Basic, NTLM). ClientAuthenicsationMethod: NTLM.
    For both servers the autodiscoverserviceinternaluri was set to: https://autodiscover.domain.com/autodiscover/autodiscover.xml
    The 2013 server has two SSL certificates installed. One is a wildcard cert for "*.domain.com" and the other includes our SANs (mail.domain.com, mail2.domain.com, webmail.domain.com, autodiscover.domain.com) it also includes the FQDN for the 2010
    and 2013 CAS servers.
    I'm speaking in the past tense because we had to roll back. The problem was no Outlook user could connect. This goes for mailboxes hosted on the Exchange 2013 and 2010 servers. The error was: "Cannot
    open your default e-mail folder" to "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete".
    Everything else worked fine during the cutover. OWA 2013 login page proxied 2010 logins properly, Outlook 2011 could connect with EWS fine, Active-Sync worked without issues too.
    It was only the Outlook 2010 and 2013 clients that could not connect.
    We rolled back and everything is working as it was before with the separate namespace. That leads me to think it's something with Outlook Anywhere (RPC/HTTPS)
    but the settings seem correct unless I'm missing something. Any help is appreciated.
    Thanks!

    Hard to say. I've had to change the router to point to the old server as mail wasnt getting in. But OWA did seem ok, although I couldn't send messages... I could only see the inbox and contacts etc.

Maybe you are looking for