LS Protocol Stack 14428

Hello,
I'm stuck on this issue. I got this error on Front-end server. Can someone help me on this.
TLS outgoing connection failures.
Over the past 28 minutes, Lync Server has experienced TLS outgoing connection failures 15 time(s). The error code of the last failure is 0x80090322(SEC_E_WRONG_PRINCIPAL) while trying to connect to the server "edgelync.xen.com.my" at address [192.168.4.2:5061],
and the display name in the peer certificate is "Unavailable".
Cause: Most often a problem with the peer certificate or perhaps the host name (DNS) record used to reach the peer server. Target principal name is incorrect means that the peer certificate does not contain the name that the local server used to connect. Certificate
root not trusted error means that the peer certificate was issued by a remote CA that is not trusted by the local machine.
Resolution:
Check that the address and port matches the FQDN used to connect, and that the peer certificate contains this FQDN somewhere in its subject or SAN fields. If the FQDN refers to a DNS load balanced pool then check that all addresses returned by DNS refer to
a server in the same pool. For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the local machine.
Front-end configuration:-
IP address : 10.1.1.225: 5061 ( lync.xen.com.my)
Edge Server configuraiton:- using single FQDN( one public IP)
Internal IP : 10.1.1.226 (edgelync.xen.com.my)
External IP:
- Access Edge : sip.xen.com.my : 192.168.4.2 (5061)
- Web Conference : sip.xen.com.my : 192.168.4.2 (444)
- A/v conference : sip.xen.com.my : 192.168.4.2 (443)

Hi Protocol stack,
Some suggestions for your reference.
1. Install the latest cumulative update for Lync Server 2013.
There’s a similar KB for Lync Server 2010.
https://support.microsoft.com/en-us/kb/2735324
2. Please check your DNS settings and routes. From the error message, I’m not aware why the FE connected to the Access Edge external interface.
3. Please try to re-import the Root certificate chain for Edge server.
Check out this article.
https://technet.microsoft.com/en-us/library/gg412750(v=ocs.15).aspx
Best regards,
Eric
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

PowerShell: Determine if Hide Instance or Force Encryption is enabled on the Protocol Stack

I'm trying to collect, across many multiple instances on many different servers, if the SQL instance has the "Hide Instance" or "Force Encryption" options enabled using PowerShell and SMO.
I appreciate that there is an indirect way of retrieving these values via the registry but I want to retrieve these settings through Powershell and SMO as I'm already using this for other aspects. Using the registry for these values seems strange when
so much else in the protocol stack is available. Maybe its just me...
Here is an example of code I am using to get the TCP ports:
[string]$server_name = "testserver1";
[string]$instance_name = "ins1";
[reflection.assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo")| out-null;
[reflection.assembly]::LoadWithPartialName("Microsoft.SqlServer.SqlWmiManagement")|out-Null;
[PsObject]$computer = New-Object Microsoft.SqlServer.Management.Smo.Wmi.ManagedComputer $server_name;
[string]$uri = "ManagedComputer[@Name='$server_name']/ServerInstance[@Name='$instance_name']/ServerProtocol[@Name='Tcp']/IPAddress[@Name='IPAll']"
[PsObject]$tcp = $computer.GetSmoObject($uri);
Write-Host $tcp.IpAddressProperties["TcpPort"].Value;
However, I am unable to work out or find any way of directly getting the values for the "Hide Instance" or "Force Encryption" using similar methods.

For those interested here is my code to retrieve these settings directly from the registry on the remote server:
[string]$server_name = "testserver1";
[string]$instance_name = "ins1";
[string]$key = "SOFTWARE\\Microsoft\\Microsoft SQL Server\\Instance Names\\SQL";
[PsObject]$registry = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey("LocalMachine", $server_name);
[PsObject]$registry_key = $registry.OpenSubKey($key);
[string]$reg_instance = $registry_key.GetValue($instance_name);
$key = "SOFTWARE\\Microsoft\\Microsoft SQL Server\\$reg_instance\\MSSQLServer\\SuperSocketNetLib";
$registry_key = $registry.OpenSubKey($key);
Write-Host "Hide Instance: " $registry_key.GetValue("HideInstance");
Write-Host "Force Encryption: " $registry_key.GetValue("ForceEncryption");
However, it would still be nice to get these settings directly through SMO if anyone knows?
Best regards all

TNS:listener could not find available handler with matching protocol stack

Hi,
I am getting the following stack trace in b2b.log file:
2009.01.06 at 14:34:35:869: Thread-108: BusinessLogicLayer - (ERROR) caught error: Error -: AIP-13002: SQL error getting the DataSource
2009.01.06 at 14:34:35:870: Thread-108: IP - (ERROR) java.sql.SQLException: Listener refused the connection with the following error:
ORA-12516, TNS:listener could not find available handler with matching protocol stack
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVICE_NAME=test)))
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:292)
     at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:327)
     at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:429)
     at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:150)
     at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:31)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:608)
     at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:217)
     at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:113)
     at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:76)
     at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:58)
     at oracle.jdbc.pool.OracleConnectionCacheImpl.getNewPoolOrXAConnection(OracleConnectionCacheImpl.java:493)
     at oracle.jdbc.pool.OracleConnectionCacheImpl.getPooledConnection(OracleConnectionCacheImpl.java:368)
     at oracle.jdbc.pool.OracleConnectionCacheImpl.getConnection(OracleConnectionCacheImpl.java:306)
     at oracle.jdbc.pool.OracleConnectionCacheImpl.getConnection(OracleConnectionCacheImpl.java:285)
     at oracle.tip.buslogic.common.DBConnectivity.getConnection(DBConnectivity.java:151)
     at oracle.tip.buslogic.common.ExecutionContextImpl.getService(ExecutionContextImpl.java:379)
     at oracle.tip.buslogic.common.ExecutionContextImpl.setRuntimeActiveandQuiescing(ExecutionContextImpl.java:799)
     at oracle.tip.adapter.b2b.data.B2BExecutionContext.setRuntimeActiveAndQuiescing(B2BExecutionContext.java:130)
     at oracle.tip.adapter.b2b.data.B2BExecutionContext.activate(B2BExecutionContext.java:98)
     at oracle.tip.adapter.b2b.data.DBContext.initialize(DBContext.java:90)
     at oracle.tip.adapter.b2b.data.DataContext.getNewDBContext(DataContext.java:365)
     at oracle.tip.adapter.b2b.data.DataContext.getDBContext(DataContext.java:346)
     at oracle.tip.adapter.b2b.transport.InterfaceListener.onMessage(InterfaceListener.java:232)
     at oracle.tip.transport.basic.FileSourceMonitor.processMessages(FileSourceMonitor.java:858)
     at oracle.tip.transport.basic.FileSourceMonitor.run(FileSourceMonitor.java:302)
When I ran the enquire script. I am getting the following exception:
IPEnqueue start...
Action Name = null
oracle.jms.AQjmsException: ORA-00600: internal error code, arguments: [kwqbgqc: bad state], [1], [1], [], [], [], [], []
ORA-06512: at "SYS.DBMS_AQIN", line 454
ORA-06512: at line 1
at oracle.jms.AQjmsProducer.enqueue(AQjmsProducer.java:1180)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1407)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1512)
at oracle.tip.adapter.b2b.data.IPEnqueue.main(IPEnqueue.java:201)
[Linked-exception]
java.sql.SQLException: ORA-00600: internal error code, arguments: [kwqbgqc: bad state], [1], [1], [], [], [], [], []
ORA-06512: at "SYS.DBMS_AQIN", line 454
ORA-06512: at line 1
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:124)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:315)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:281)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:638)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:183)
at oracle.jdbc.driver.T4CCallableStatement.execute_for_rows(T4CCallableStatement.java:872)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1085)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2983)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3025)
at oracle.jms.AQjmsProducer.enqueue(AQjmsProducer.java:1110)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1407)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1512)
at oracle.tip.adapter.b2b.data.IPEnqueue.main(IPEnqueue.java:201)
Error -: AIP-13121: Connection-related error. Please verify that the database server is running.: java.sql.SQLException: Closed Connection
at oracle.tip.buslogic.common.SessionDownException.isSessionDown(SessionDownException.java:96)
at oracle.tip.common.IPException.initIPException(IPException.java:179)
at oracle.tip.common.IPException.<init>(IPException.java:114)
at oracle.tip.repos.core.persistency.DCException.<init>(DCException.java:68)
at oracle.tip.repos.core.driver.CatalogDriver.disconnect(CatalogDriver.java:1666)
at oracle.tip.repos.core.persistency.PersistencyService.disconnect(PersistencyService.java:578)
at oracle.tip.buslogic.common.ExecutionContextImpl.disconnectService(ExecutionContextImpl.java:602)
at oracle.tip.buslogic.common.ExecutionContextManager.cleanContextResources(ExecutionContextManager.java:629)
at oracle.tip.buslogic.common.ExecutionContextManager.leaveContext(ExecutionContextManager.java:581)
at oracle.tip.buslogic.common.ExecutionContextManager.leaveContext(ExecutionContextManager.java:720)
at oracle.tip.adapter.b2b.data.IPEnqueue.main(IPEnqueue.java:245)
Caused by: java.sql.SQLException: Closed Connection
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:124)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:161)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:226)
at oracle.jdbc.driver.PhysicalConnection.rollback(PhysicalConnection.java:1041)
at oracle.jdbc.OracleConnectionWrapper.rollback(OracleConnectionWrapper.java:90)
at oracle.tip.repos.core.driver.CatalogDriver.disconnect(CatalogDriver.java:1662)
... 6 more
I tested the database and it was up. Any help is appreciated.

You may be interested in http://www.tek-tips.com/viewthread.cfm?qid=1368266&page=10

Exteral Users can't connect to the EDGE server

HI All for about a week and half now I've been seeing this error a lot on my event logs. All my external users are no longer able to connect to the DMZ EDGE server with 3 external IP's. They can only use LYNC if they access out VPN. Any suggestions on what
may be the issue???
Log Name:      Lync Server
Source:        LS Protocol Stack
Date:          4/24/2014 9:07:14 AM
Event ID:      14428
Task Category: (1001)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      LyncEdge.*********.net
Description:
TLS outgoing connection failures.
Over the past 16 minutes, Lync Server has experienced TLS outgoing connection failures 176 time(s). The error code of the last failure is 0x80090330(SEC_E_DECRYPT_FAILURE) while trying to connect to the server "**********.osis.is.local" at address
[10.111.111.8:5061], and the display name in the peer certificate is "Unavailable".
Cause: Most often a problem with the peer certificate or perhaps the host name (DNS) record used to reach the peer server. Target principal name is incorrect means that the peer certificate does not contain the name that the local server used to connect. Certificate
root not trusted error means that the peer certificate was issued by a remote CA that is not trusted by the local machine.
Resolution:
Check that the address and port matches the FQDN used to connect, and that the peer certificate contains this FQDN somewhere in its subject or SAN fields. If the FQDN refers to a DNS load balanced pool then check that all addresses returned by DNS refer to
a server in the same pool. For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the local machine.
Thanks Dave Wolf

Verify root certs exist in the Trusted Root Certification Store.
Also you can refer below links
http://www.shudnow.net/2011/02/01/lync-2010-edge-utilizing-windows-server-2008-r2-federation-tls-issues/
http://theucguru.blogspot.com/2012/03/lync-edge-ls-protocol-stack-14428.html
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical

How can I implement a new protocol over IP

Hi,
I want to implement a new protocol (my customized one) in solaris 8. This protocol will be something like UDP and will be using IP for communication.
So how can i use IP stream module for that?
thankx
prasenjit

I can give you some pointers regarding this. Although, I implemented protocol below IP.
- Look for information on ipsecah and ipsecesp. These are pseudo devices on top of IP for Solaris 8.0.
- Check how the protocol stack is built while booting.
- If you intend to implement a module, rather than a driver then things might be little easy. You can push your module on top of IP. See man for "sad" and "autopush" mechanism
- Sample drivers and modules from SUN are of great
help. I came to know about the sample drivers very late.
Otherwise, I would have saved some time.
- Unix System V network programming by Rago is a very good reference.
I hope this helps.
-Ashutosh

Many security events have been identified by the proxy stack.

On our Lync Edge servers I can see lots of warning events are getting generated every second. Any idea how to stop this events.
Log Name:      Lync Server
Source:        LS Protocol Stack
Date:          3/26/2014 5:40:43 AM
Event ID:      14425
Task Category: (1001)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      servername
Description:
Many security events have been identified by the proxy stack.
In the past 55 seconds, 30 security events have been identified by the proxy stack. A large number of security events could indicate that the server is under attack. The last event was:
$$begin_record
LogType: security
Text: The connection from a remote user client is refused because remote user access is disabled
Result-Code: 0xc3e93d6d SIPPROXY_E_CONNECTION_EXTERNAL_INTERNET_ACCESS_DISABLED
Peer-IP: 192.168.10.1:50224
Peer: 192.168.10.1:50224
$$end_record
Cause: The server may be under attack, or there might be a configuration problem that is causing errors.
Resolution:
Launch the Lync Server 2010 Logging Tool. Select the "SIPStack" component, the "Errors" level and the TF_SECURITY flag. Review the events reported to the trace log using the "Analyze Log Files" feature of the logging tool.

Hi,
What's your Edge NIC and certificate configuration? And the DNS SRV records?
It may happen because the Lync server does not pass the correct certification authority information back to the Lync client during the negotiation of the TLS connection.
You can refer to the part “Workaround” in the link below:
http://support.microsoft.com/kb/2464556
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

PC Suite does not detect my bluetooth stack of blu...

Hi can somebody help me?
I have done all advises and procedures regarding uninstalling and installing in the right order but no result.
= = = = = =
My info is:
Bluetoothstack : Bluesoleil 2.3.0.0 release 060728 stackversion: 05.04.11.20060622
PC Connectivity Solution:
Version 9.23.3.0
Nokia Connectivity Cable Driver:
Version 7.1.17.0
Operating system:
Microsoft Windows XP 32-bit Edition, Service Pack 3
Language: Nederlands
Language for non-Unicode programs: Nederlands
Detected Internet browsers:
- Microsoft Internet Explorer 8.0 (Default browser)
- Mozilla Firefox 3.5
Detected Bluetooth stacks:
= = = = =
My problem is that no bluetooth stacks are detected by PC Suite.
With bluesoleil I can make connection with my Phone 2720 Fold. And all works fine
But PC Suite does not see the bluetooth connection
How should solve this?
Many thanks in advance.
Regards,
Adam
Message Edited by AdamX01 on 06-Nov-2009 02:20 PM

I never got any Bluesoleil stack to ever work with any version of PC Suite. However, as of Windows XP SP2, the Microsoft Bluetooth protocol stack appears to detect "several" Bluesoleil Bluetooth compatible dongles and will use them. However, these will have limited functionality as Microsoft limits their Bluetooth support.

Transport Protocol

Hello all,
I am implementing a transport protocol that sends data from one source to another over multiple paths. The protocol is to work as follows:
When the protocol receives data, the data will be fragmented into TCP segments. Then TCP connections will be opened in the available paths to the destination and each segment will be
transmitted in one of the connections. The TCP connections are independent of each other.
Before the protocol can open TCP connections to the destination, it has to know the available paths provided by the network to the destination. This is where I have problems. Do you have any
idea how I can get this information? Also the destination has to know the path of each packet for retransmission purposes in case the packet gets lost.
Any help is appreciated.
Thanks
Mpho

Ummmm... if you're doing this with Sockets, the TCP/IP protocol stack does all of this work for you...
I think I haven't understood you question, sorry.

Protocols supported by SunOne

HI,
We are planning to built a clustering model with SunOne and use two application servers. These two server will be may be on a different network and only few protocol stack are allowed for communication between these. Is there any list of the supported protocols? Can SunOne communication with the other server in cluster using someother protocol other than tcp/ip?
Thanks,
Srivatsan.

Sir,
<suresh kumar> wrote in message news:[email protected]..
How can i connect to weblogic other than t3 protocol?
Does weblogic supports any other J2EE standard protocols??
I am using rmi protocol in my code to connect to weblogic. It is failing.It is not very likely that it is failing because of t3. It happens to be a pretty
stable thing. May be it is the way you are cooking it.
Do you have any stack traces or error messages that you could kindly share
with us?
Regards,
Slava Imeshev

What protocol does air play use

I have purchased a Marantz MCR603 which is airplay enbabled but airplay keeps dropping out. I have been advised by both Apple and Marantz that my BTHomhob (3.0, the latest) does not support airplay protocols. BT,as usual, have no idea what I'm talking about. Can anybody advise?

AirPlay is an Apple propriety protocol stack and is based on the RTSP network control protocol. An AirPlay device, such as your Marantz, would have to work with one or both of the following two services: ROAP used for audio streaming, and AirPlay for video/photo content.
ROAP uses TCP port 49152 and AirPLay uses TCP port 7000. Note: These ports would not need to be opened on your home router as all streaming is being done on the local network, but both the Marantz and the iTunes host device must be able to open these ports to communicate.

Camera link protocol implementation on FPGA

Hi,
I want to configure the Basler camera parameters like exposure time, frame rate, Gain value etc. through 7966R FlexRIO & 1483 Camlink adapter module. But on FPGA there is no option to configure these parameters through .icd file or MAX. So I have to implement the Camera Link protocol in FPGA to configure these parameters of camera.
I found that camera link has 4 controls lines (CC1 to CC4) but I am not able to find how these lines works to control the parameters of camera. If anyone knows how these control lines work then please tell me or share any document to describe their operation. Or any other information through which I can implement the algorithm on FPGA to control the parameters of camera.
Any help will be appreciate
Regards

I ran into multiple issues with the Serial Server running through the 1483/7966. I was never able to reliably get the serial server to operate through the MAX NI Vision CLSerNat function. It seems the 1483 is just not well supported in Max in any way. This prevents the use of Pylon as your serial command/status tool. Those work great with other frame grabbers like the 1433, but the 1483 leaves you having to implement the entire capability yourself.
So, I wound up having to write my own serial driver for the BBPI protocol and message processors for the various standard message types the Basler ACE cameras respond to.
Though I can't provide code, if you need to write your own protocol stack and have questions on the Basler interface, I'm worked through many of the issues.
One issue you may encounter is with the serial server itself. It operates in byte mode. I was never able to understand the reasons, but between a VI running on a host PC interacting through the stock serial server running on an FPGA (7966) through a RT target (PXI-1082) byte mode inserted very large inter-character delays. Often so large as to cause the Basler camera to claim a timeout and terminate the command. I had to modify the serial server to operate in a one-shot FIFO mode for transmit data as follows:
In the FPGA serial_interface.vi (For non byte-mode)
Increase the FIFO to 64 bytes to accomodate the largest Basler message
Add a "Transmit now" control to trigger a full FIFO output
Add a "Transmit length" control to control the number of bytes transmitted
In the upper level serial_server.vi
Modify the transmit loops to better detect bytes to transmit from the Ethernet interface and to direct the transmit data to the new WriteBytes vi
In the FPGA_UART.llb library
Add an FPGA_UART_WriteBytes.vi to handle the non byte-mode modification and to 'chunk' up transmit data into 64 byte (max) pieces. In the BBPI and Basler protocols, this has not been seen since all the messages are small.
With these modifications, I could then write a state machine to handle the basler BBPI protocol. States I chose for this were:
Idle
When a command is queued, it is fed to the serial server in its entirety. The serial interface sends it to the camera as a complete message with no inter-character gaps)
Wait for ACK
Every command must have an ACK/NACK
Go back to idle if sending a write or command message
Wait for BFS (Only if sending a read request)
Wait for FTF
Wait for the data lengthbyte
Wait for BFE (Goes back to idle once all bytes received)
It's up to you if you want to handle the checksum capability of the BBPI protocol. It's surprisingly tricky. I hsould have saved myself the headache and just worked entirely in non-checksumming mode.
Once I got that all working, I could then write message handlers for each of the basic Basler message types:
Enum
String
Bitfield
Scalar
etc..
followed by specific message handlers for each of the messages I wanted to deal with. My usual technique is to perform a mass serial configuration as soon as I fire up the FPGA. I haven't tried to use the trigger port signals (CC1 etc) but those can all be configured and controlled through the serial port once you get a message passing capability in place.

What is the reason to move LACP protocol from 802.3ad to 802.1ax

From the wikipedia, it gives the following reason
Move to 802.1 layer in 2008[edit]
David Law noted in 2006 that certain 802.1 layers (such as 802.1X security) were positioned in the protocol stack above Link Aggregation which was defined as an 802.3sublayer.[5] This discrepancy was resolved with formal transfer of the protocol to the 802.1 group with the publication of IEEE 802.1AX-2008 on 3 November 2008.[6]
I not so sure about the description above, if LACP belongs to 802.3 working group, 802.1x above the 802.3 stack, so it can treat the LAG ports as one port to do the access control, what's wrong with my description? It seems the 802.1x should stand below LACP from the wiki description, can someone explain why the relationship between them should like that?

Hi AP,
Do you mean that .... "Therefore, the user who run KB21N, should be aware of total cost initially available in cost center 4100 ... "
If the cost in cost center 4100 is less than $400, using KB21N to move cost more than $400 is not logic, right?
Comment please.

Lync 2013 federation failing for a specific domain

Hello,
We have recently migrated to Lync 2013 and noticed that one of the domains we federate with is unable to federate with us.
we are getting the following error:
Log Name: Lync Server Source: LS Protocol Stack Event ID: 14428 Task Category: (1001)
Level: Error Keywords: Classic User: N/A Computer: server.fqdn.com Description: TLS outgoing connection
failures.
Over the past 28 minutes, Lync Server has experienced TLS outgoing connection failures 4 time(s). The error code of the last failure is 0x80090325(SEC_E_UNTRUSTED_ROOT) while trying
to connect to the server "sip.example.com" at address [10.10.10.10:5061], and the display name in the peer certificate is "Unavailable". Cause: Most often a problem with the peer certificate or perhaps the host name (DNS) record used to
reach the peer server. Target principal name is incorrect means that the peer certificate does not contain the name that the local server used to connect. Certificate root not trusted error means that the peer certificate was issued by a remote CA that is
not trusted by the local machine. Resolution: Check that the address and port matches the FQDN used to connect, and that the peer certificate contains this FQDN somewhere in its subject or SAN fields. If the FQDN refers to a DNS load balanced pool then check
that all addresses returned by DNS refer to a server in the same pool. For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the local
machine.
Thanks

Thanks Michael.
That worked for one of two issues I'm seeing, I did use the same steps for the second issue but it didn't seem to work, I have imported the CA of the domain we would like to federate with to the trusted root certification authorities and the intermediate
certification authorities per the certificate issuer's website guidelines. I did learn that the federated partner is also using OCS 2007 R2, not sure if this may have to do with this.
Over the past 30 minutes, Lync Server has experienced TLS outgoing connection failures 1 time(s). The error code of the last failure is 0x80072746 while trying to connect to
the server "ocs.example.com" at address [10.10.10.10:5061], and the display name in the peer certificate is "ocs.example.com". Cause: Most often a problem with the peer certificate or perhaps the host name (DNS) record used to reach the peer server. Target
principal name is incorrect means that the peer certificate does not contain the name that the local server used to connect. Certificate root not trusted error means that the peer certificate was issued by a remote CA that is not trusted by the local machine.
Resolution: Check that the address and port matches the FQDN used to connect, and that the peer certificate contains this FQDN somewhere in its subject or SAN fields. If the FQDN refers to a DNS load balanced pool then check that all addresses returned by
DNS refer to a server in the same pool. For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the local machine.

E51 Improvements

My list of things I'd like changed/fixed:
No carriage return/new line facility in Mail / Text editing (unless there's a key combo for it ?). This is a real pain for me currently.
In SMS / Text editing the Reply To and Delete Text options should be above Call Sender (please!)
I changed the default right hand shortcut key (used to be Camera) to something else and now can't find where that option is again. Please put it with the other One-touch key options in Settings.
No shortcut available to go straight to my SMS / Text Inbox from a shortcut/one-touch key.
MSN (Live) chat (downloaded on phone) defaults to capitalising the first letter of every sentence. This is really annoying for normal chat and one-liners (lol, rtfm etc)
Needs better (more tactile) power and volume buttons.
The default earphones are horrendously uncomfortable, how about a decent set of in-ear options (Sennheiser etc) ?
Everything else is really cool, I particularly like the delete/backspace button and it's default action and confirmation on the d-pad to delete texts/messages !
Hopefully some of these can be fixed in future firmware updates or at least made optional if others disagree.
Thanks.Message Edited by hollom on 12-Dec-200703:23 PM

I have had my E51 a few days and the biggest annoyance is the selection of WLAN access points.
For SIP, I can define a set of access points (e.g. Home and Work) that are automatically selected when in coverage.
For other applications (e.g. Nokia Maps), If the application has been set to use access point "Work", and I try to use it at home, then it complains that there is no internet connection, or asks me to disconnect the access point, even though I have a good connection to my WLAN.
What I want is the ability to define a set of trusted (and free) access points, that the phone will automatically roam between without user intervention. This should be done below the application layer, so that all (including existing) applications can use the feature.
BTW, why doesn't Visual Radio allow me to select a WLAN access point?
E51 owner
GSM/3G Protocol stack designer

I am sorry nhylo this your answer I hope it will help you

MAC OS
iMac
There are several versions of the iMac computer. The first two versions (referred to as revision A and revision B) were colored Bondi Blue. The next version (referred to as revision C) was introduced in January 1999 and came in five different colors.
Revision A and B iMac computers support IrDA, but not IRTalk. Revision C iMac computers do not support infrared communication of any type.
PowerBook G3 Series (Lombard and Wallstreet)
PowerBook G3 Series computers are IrDA compliant.
PowerBook G3(Pismo or Firewire)
The PowerBook (FireWire) supports IrDA.
PowerBook G4 (Titanium) and PowerBook G4 (Gigabit Ethernet)
The PowerBook G4 and PowerBook G4 (Gigabit Ethernet) support IrDA.
BLUETOOTH
Bluetooth is a short range radio link meant to replace the necessity of cables to connect portable and/or fixed electronic devices. The Bluetooth protocol uses a combination of packet and circuit switching to transmit data through variable hop frequency. Connectivity across a network is provided according to time slot division. It provides point-to-point or point-to-multipoint connection, creating links for between 2-8 devices (including the initiating Master/host and its Slave/s) to form a piconet. Multiple piconets that are linked together form a scatternet. A Master in one piconet can be a Slave in another, and vice versa, to form an inter-connected network. Dial-Up Networking, Fax, Headset, LAN Access, and SIM (Subscriber Identity Module) Access functionality all use serial port communication profiles and virtually emulate RS232 (or similar) serial cable port protocols.Ê A Bluetooth management application is necessary in each device to facilitate the serial port emulation. Radio Frequency Communications (RFCOMM) is used to transport user data, modem control signals and configuration commands.
When using a cellular device equipped for Bluetooth communications to transmit data over a cellular network, the Bluetooth link must be established as an initial protocol layer and the cellular network link is negotiated in a second protocol sequence through the cellular device. For example, when attempting to connect a Pocket PC device to the GPRS data network using a cellular phone as a negotiator via a Bluetooth link. The connection is initiated and controlled by the Pocket PC device, but dependent on the SIM functionality available through the cellular phone to negotiate and establish the connection to the cellular network. In this capacity, known as a SIM Access Profile, the cellular phone functions as a Server (or ÒaccepterÓ) while the Pocket PC device acts as a Client (or ÒinitiatorÓ). A Client may have access to only one Server with a SIM at any given time of active connection. Designation of a Client versus Server role is independent of the deviceÕs discover/discoverable status.
To ensure secure communication between the Client and Server devices, several conditions must be met. The Client and Server must be successfully Bonded (otherwise known as Paired) before setting up a SIM Access Profile or configuring the settings of a GPRS/GSM network connection. The SIM bearer (cellular phone) must be properly enabled to initiate authentication. The link between the Client and Server will be encrypted using the Bluetooth baseband and will be at a minimum of 64 bits. Each incident of authentication will be identified with a unique Passkey between the devices that must be in mutual agreement at the time of connection.
Bluetooth transceivers operate in the 2.4 GHz ISM (Industrial Scientific Medical) band. In a majority of the countries in the world this band includes 2.400-2.4835 GHz. Please note that products that implement a reduced frequency band will not work with those that implement the full frequency band. These products that are reduced in frequency (perhaps distributed in different countries), are generally intended for use in a single market. As such, devices developed and/or purchased in Europe and Asia (for example) may not be compatible for use with devices from the United States.
For more general information about Bluetooth development and technology, go to www.bluetooth.com, the official Bluetooth website. Select the link to Bluetooth technology & you to find links to Using Bluetooth technology, Products, and How it works. In the Using Bluetooth technology section, there is a link to view information about connecting a Mobile Phone with a Personal Computer. Here you can view links that include all currently supported and available devices that are applicable to your needs. This will be useful to verify the compatibility of your devices. You can find specific information about the technical details and requirements of modem data transmission using cellular technology with Bluetooth by proceeding to the Developer Information section and viewing the SIM Access Profile and v.1.1 Profiles documentation.
For more info about using Bluetooth technology with Mac OS X and Apple products, go to www.apple.com/bluetooth.
GENERAL DIAGNOSTICS WITH BLUETOOTH
* Make sure that your Bluetooth devices are compatible.
* Your operating system should be current on all applicable software, driver, and firmware updates.
* Verify that the Bluetooth functionality in both devices is turned ÒOnÓ.
* Verify that the devices are currently bonded/ paired. This can often be difficult to assess with the Nokia 6310i. The phone may not show the devices as ÒActiveÓ, but the Bluetooth Manager will display that the devices are paired/bonded. Often the phone will display a Disconnected message. Disregard this message and continue with the instructions in the setup guide.
* Ensure that the Bluetooth Dialup Modem is selected in the Connections (for Pocket PC devices), System Preferences/ Network (in Mac OS X), or Dial-Up Networking properties (in Microsoft Windows OS).
* It may be necessary to attempt to connect multiple times to establish a GSM/GPRS connection. Do not be discouraged if you receive a connection error or receive a Disconnected message on your cellular phone. Due to interference or early product development, it may take several attempts to push the connection through all layers of the Bluetooth service and protocol stack. It is also possible, as is seen with the Nokia 6310i, for a Disconnect message to be given while transfer protocol layers of communication are still recognized and active. In this case, a temporary minor error (Òdata not availableÓ or Òcard not accessibleÓ) is the cause as the Client device attempts to initialize and access the SIM for data packet transfer.
* Verify that you are not in the presence of equipment that may be interfering on the same (or possibly overlapping) radio frequency as your Bluetooth communication. This includes medical equipment, wireless 802.11 connectivity devices, other Bluetooth enabled cellular phones, airport communications, amongst other factors.
* It may be necessary on some devices to alternate in the bonding/pairing process between setting the phone in Discover versus Discoverable mode, as is sometimes the case with the Sony Ericsson T68i.
* Verify that your devices are fully charged.
* Verify that you have GSM/GPRS coverage available at your location and that your wireless account is properly provisioned for data transmission with a modem over the network.
* Check that your connection is using the correct Dialing Location properties and profile. For a GPRS connection, this should follow the instructions to include the letter G in each of the three dialing location fields of the Dialing Patterns specifications as well as verification that the phone number to be dialed is *99# and that the Area Code and Country Code fields are not included in your connection.
Alternative methods of Pairing/Bonding for the Nokia 6310i and iPAQ 3800/3900 series device with Pocket PC 2002 Operating System
If you are experiencing problems due to interference, or if your signal strength is not very strong, modifying the serial port connection may allow you to connect to the GPRS network.
* Open the Bluetooth Manager application on your Pocket PC device.
* Verify that the Bluetooth on your handset is currently On. (You may want to check the power level on your devices.)
* If your Nokia 6310i is not seen as an available device, tap on Search and proceed to locate it and Save it to a group. Otherwise, tap on the Nokia 6310i icon.
* Tap on Actions.
* Select Set as Bluetooth Dialup Modem.
* Tap Actions again.
* Select Connect to COM 1.
* Press Accept on the phone to connect with the Pocket PC device.
* Enter a unique Passcode onto your handset.
* You will have 10 seconds to enter the same Passcode/PIN code onto your Pocket PC device.
* Your phone will notify you that you are connected. You can verify this by scrolling through the Bluetooth menu on your handset and selecting View active device.
* You will have 3 minutes to proceed before your Bluetooth session will time out.
* Proceed to connect using the usual methods outlined in the setup guide.
* You will be notified that the Serial style= style=Port style=connection was terminated . Tap OK and continue anyway. It may take several attempts to get the Bluetooth stack to respond.
* Press Accept to connect to the phone once more.
* The phone will now notify you that a GPRS connection is in progress.
The following method may also be useful if the bonding appears to be unstable and multiple attempts to connect through the Connection Settings fail:
* Open the Bluetooth Manager application on your Pocket PC device.
* On the phone, scroll to select Bluetooth from the main menu, then select Bluetooth and select Off.
* Turn your phone off, then on again to fully reset its Bluetooth protocol stack.
* On the Pocket PC device you should see the Nokia 6310i listed. Tap to select it.
* Tap on Actions.
* Select Remove bond with this device.
* Tap on Actions again.
* Select Remove this device.
* Tap Yes when asked if you want to remove it from all groups.
* Close all open windows on your Pocket PC device and tap on the Bluetooth icon on the lower left corner of your screen.
* Select Turn radio off.
* Soft reset your device according to manufacturerÕs instructions.
* Tap on the Bluetooth icon on the lower right corner of your screen again and select Turn radio on.
* Turn the phone back on, scroll to Bluetooth from the main menu, then select Bluetooth and select On.
* Open the Bluetooth Manager application.
* If you do not see your device listed, tap on Search.
* Tick the box to select your phone, choose a group and select Save.
* Tap OK.
* Tap on the Nokia 6310i icon.
* Tap on Actions.
* Select Create bond with this device.
* Enter a unique PIN code.
* Press Accept on the phone when prompted to Pair with the Pocket PC device.
* Enter the Passcode/PIN code. You will have 10 seconds to complete this task. (If you receive a Disconnected message on the phone, continue anyway.)
* Proceed to set up your connection as usual through your Connection Settings.
* If you are not connected the first time, tap Connect to try again immediately after you receive the Disconnected message on the phone. It may take several attempts to get the Bluetooth stack to respond.
* Press Accept on the phone to accept the connection.
* The phone will indicate that a GPRS connection is in progress.
The processes for troubleshooting Bluetooth in a Windows environment are very similar to those of Pocket PC devices.
* In the Bluetooth Manager application, proceed to click on the Nokia 6310i and select Unpair device, then proceed to turn the Bluetooth radio Off on the computer and on your phone. Reset both devices, then try again. This should clear any temporary problems in the Bluetooth service and protocol stacks.
* It may be necessary to attempt to establish your GSM/GPRRS connection multiple times before you will actually be able to transmit data over the cellular network.
* Verify adequate power level on each device.
* Resolve any issues that may exist with your cellular account or wireless coverage in your location.
* Other wireless electronic devices that operate in (or near) the Industrial, Scientific, and Medical bandwidth may provide significant interference. These include other cellular phones, 802.11 devices, medical equipment, airport communications, amongst other factors.
* You must select secure encryption to be used when creating the bond with your devices in the Bluetooth Manager.
USEFUL AT COMMANDS
When GPRS doesn't appear to be working, or you just want to check that all is well, hopefully the following will prove useful:
Check the phone
Verify that GPRS is currently available in your location and that your cellular account is properly enabled for data transmission over the network using your device as a modem.
If all appears well on the phone, head to HyperTerminal or your equivalent Terminal application and try some of the following style=to further query the status of your ability to communicate with the network:
at+cgatt?
If a value of '1' is returned, then we have GPRS attached. If the value is '0', then GPRS is currently deactivated (i.e. the service is either down or the user is not currently provisioned).
at+cgatt=? will return the supported values for the command
at+cgatt=1 will attempt to attach to the GPRS network
at+cgdcont?
This will allow you to check that the Access Point Name (APN) has been set correctly.
A typical response will look something like this:
+CGDCONT:1,"IP","proxy"
If the APN is set incorrectly for the AT&T Wireless GPRS service, enter the following:
at+cgdcont=1,"IP","proxy"
at+cops?
This will return the identity of the network operator.
at+cgreg?
This will return the network registration status.Ê One of the following values should be returned:
0 - not registered, not searching
1 - registered, home network
2 - not registered, searching
3 - registration denied by network
4 - unknown
Ê
Top
Ê

You welcome

LS Protocol Stack 14428

Similar Messages

Maybe you are looking for