Error 1747 : The Authentication Service is Unknown

netsh winsock reset

SRPClient::Connect: Error

Try stopping these services in this order:

Blackberry Controller
Blackberry Dispatcher
Blackberry Router

Starting the services in this Order:

Blackberry Controller
Blackberry Dispatcher
Blackberry Router

Linux: Delete / Remove User Account

To remove the user’s home directory pass the -r option to userdel, enter:
# userdel -r vivek

How to Modify the Default SMTP Banner

To perform the following procedures, the account you use must be delegated the following:  Exchange Organization Administrator role

To perform the following procedures on a computer that has the Edge Transport server role installed, you must log on by using an account that is a member of the local Administrators group on that computer.

Note:

You cannot modify the default SMTP banner by using the Exchange Management Console. To modify the default SMTP banner, you must use the Exchange Management Shell. For more information about how to use the Exchange Management Shell, see Using the Exchange Management Shell. 

 

Working with the SMTP Banner

You control the SMTP banner by using the Banner parameter in the Set-ReceiveConnector cmdlet or the New-ReceiveConnector cmdlet. The default value of the Banner parameter is empty. The empty default value of the Banner parameter is represented by the value $null. When the Banner parameter is not specified on a Receive connector, or the Banner parameter is specified with the value of $null, a remote SMTP messaging server that connects to that Receive connector receives the following response:

220 <Servername> Microsoft ESMTP MAIL service ready at <RegionalDay-Date-24HourTimeFormat> <RegionalTimeZoneOffset>

When you specify a value for the Banner parameter on a Receive connector, a remote SMTP messaging server that connects to that SMTP Receive connector receives the following response:

<220 RemainingBannerText>

Note:

The replacement SMTP banner text string must always start with “220 “. As defined in RFC 2821, the default “Service ready” SMTP response code is 220. 

You may want to modify the default SMTP banner for Internet-facing SMTP Receive connectors on an Edge Transport server so that the server name and messaging server software are not disclosed by the SMTP banner.

 

Modifying the Default SMTP Banner, To use the Exchange Management Shell to modify the default SMTP banner

Run the following command:

Set-ReceiveConnector <ConnectorIdentity> -Banner “<220 RemainingBannerText>”

For example, to modify the SMTP banner on an existing Receive connector that is named “From the Internet” so the SMTP banner displays “220 Contoso Corporation”, run the following command:

Set-ReceiveConnector “From the Internet” -Banner “220 Contoso Corporation”

PPTP VPN Error: 720 on Windows 7

When trying to connect from a Windows 7 workstation to a PPTP VPN being served by a Server 2003 machine running RRAS I received VPN Error: 720 “A connection to the remote computer might not be established. You might need to change the network settings for this connection.” This would happen after the “Verifying username and password” phase during the “Registering your computer on the network” phase.

Rebuild the TCP/IP stack by opening an elevated command prompt and running the following command:

netsh int ip reset

Using DLink PCI Desktop Adapter 528T in VMware ESXi 5.0

Following are the steps to install DLink PCI Desktop Adapter 528T NIC driver in VMware ESXi 5.0.

1. Download DLink-528T-1.x86_64 (Rename from doc to Rar and extract) driver, extract it, and upload the VIB file to ESXi Host’s datastore.

2. Login to ESXi host console using DCUI or remote tool such as Putty, etc.

3. Change the ESXi Host Image Acceptance level to Community Supported by running below command:

~ # esxcli software acceptance set –level=CommunitySupported

Note: This setting can also be configured from the vSphere Client, by selecting the ESXi Host and then navigating to Configuration Tab | Security Profile.

4. Verify whether ESXi Host can see the NIC by executing:

~ # lspci | grep Net

5. Now change to the datastore directory which contains the driver uploaded in the first step. For example:

~ # cd /vmfs/volumes/datastore1

6. Run the below command to install the driver.

~ # esxcli software vib install -v /vmfs/volumes/datastore1/DLink-528T-1.x86_64.vib

Note: If the system throws an error message after issuing the above command, then change to system user “su” and try the command again.

7. Finally, reboot the server for the changes to take affect.

~ # reboot

Avaya IP Phones Error Messages

Error Messages

The 4600 Series IP Telephones issue messages in English only. The IP Telephones also display messages from the switch, which outside the United States may issue messages in the local language.

Table 5-3. Possible Error Messages During Installation or Operation of 4600 Series IP Telephones

Error Message	Cause/Resolution
During Installation
Checksum error	CAUSE: Downloaded application file was not downloaded or saved correctly. RESOLUTION: The telephone automatically resets and attempts to re-initialize.
DHCP: CONFLICT * to program	CAUSE: At least one of the IP address offered by the DHCP server conflicts with another address. RESOLUTION: Review DHCP server administration to identify duplicate IP address(es)
Discovering…	CAUSE: The telephone is seeking a gatekeeper on the media server, using its administered gatekeeper list. RESOLUTION: Wait for a valid registration to occur, or press # to interrupt the search and re-initialize manual or DHCP/TFTP procedures.
File too large Cannot save file	CAUSE: The telephone does not have sufficient room to store the downloaded file. RESOLUTION: Verify the proper filename is administered in the TFTP script file, and that the proper application file is located in the appropriate location on the TFTP server.
Gateway Error	CAUSE: DEFINITY Release 8.4 does not have an H.323 station extension for this telephone. RESOLUTION: On the station administration screen, ensure the DCP set being aliased for this IP telephone has an H.323 station extension administered, in accordance with switch administration instructions.
Hardware failure	CAUSE: Hardware failure prevented downloading of application file, RESOLUTION: Replace telephone.
IP Address in use by another	CAUSE: The telephone has detected an IP address conflict. RESOLUTION: Verify administration to identify duplicate IP address(es).
No Ethernet	CAUSE: When first plugged in, the IP Telephone is unable to communicate with the Ethernet. RESOLUTION: Verify the connection to the Ethernet jack, verify the jack is Category 5, etc. Note that if the telephone is attached to a 30A switched hub, upon loss of Ethernet connectivity, the usual “No Ethernet” message is not displayed.
No file server address	CAUSE: The TFTP server IP address in the IP telephone’s memory is all zeroes. RESOLUTION: Depending on the specific requirements of your network, this may not be an error. If appropriate, either administer the DHCP server with the proper address of the TFTP server, or administer the telephone locally using the ADDR option as detailed in the 4600 Series IP Telephone Installation Guide.
System busy	CAUSE: Most likely, the number of IP endpoints on the Avaya media server is already at maximum, Less likely, network resource is unavailable. RESOLUTION: The telephone was attempting to access a network resource (DHCP server, TFTP server, or the Avaya media server) and was not successful. The resource being called upon should be checked for its availability. If it appears operational and properly linked to the network, verify addressing is accurate and a communication path exists in both directions between the telephone and the resource.
System Error	CAUSE: The Avaya media server has an unspecified problem. RESOLUTION: Consult your Avaya media server administration and troubleshooting documentation.
During Registration
Extension error	CAUSE: An invalid Avaya media server Registration extension has been entered. RESOLUTION: Re-enter the extension if mis-entered initially. If appropriate, verify proper extension with respect to switch administration.
Extension in use	CAUSE: The specified extension is already in use, according to the Avaya media server. RESOLUTION: Wait a few minutes, and try again. This will work for the case when the extension is correctly administered, but service was interrupted and the Avaya media server is not yet aware of that fact. Otherwise, verify proper extension with respect to switch administration.
Failed to set phone IP address	CAUSE: The 4600 Series Telephone was originally installed on one switch with Static Addressing, and has subsequently been installed on another switch with an active DHCP server assigning dynamic IP addresses. RESOLUTION: Reset the telephone.
Incompatible	CAUSE: This release of the Avaya media server does not support the current version of the IP Telephone. RESOLUTION: Upgrade to the current version of Avaya media server software.
Message light blinks on and off, and the telephone did not complete registration.	CAUSE: The telephone has a hardware fault. RESOLUTION: Replace the telephone.
Password Error	CAUSE: An invalid PBX Registration password has been entered. RESOLUTION: Re-enter the password if mis-entered initially. If appropriate, verify proper password with respect to switch administration.
Resource Error	CAUSE: The Avaya media server rejects the registration request. RESOLUTION: Verify your Avaya media server administration to ensure the telephone’s proper IP address, extension, and password are being used.
Timeout Error	CAUSE: Protocol timeout error. RESOLUTION: Retry. If failure continues, check network congestion, addresses, etc. to identify cause of timeout.
Undefined Error	CAUSE: An error has occurred without an identifiable cause. RESOLUTION: Conduct self-test, restart the telephone, and if no other cause becomes evident, replace the telephone.
Wrong Set Type	CAUSE: The Avaya media server does not recognize the set type. RESOLUTION: Ensure the Avaya media server is properly administered to expect the appropriate telephones for the IP address and extension.

Table 5-4. Possible Error Messages During 4620/4630/4630SW Backup/Restore

Error Message	Cause/Resolution
Current options and Speed Dial entries have not yet been backed up.	CAUSE: An attempt to save the current options and speed dial entries on the FTP server has not yet been made or is in progress. RESOLUTION: Wait for a message stating that backup was successful.
The FTP Server Name is not known. Please check the FTP Server IP Address.	CAUSE: Invalid or missing Server name. RESOLUTION: Verify the FTPSRVR address is the File Server to which backup data should be saved. Verify that the FTPDIR value is the correct directory path for that File Server.
The FTP Server has not yet responded, so backup has not yet succeeded.	CAUSE: The FTP Server has not responded to the attempt to backup/restore. RESOLUTION: Try again, verify the FTP server address, verify the FTP server is online, and/or verify the network connectivity.
The FTP Server has denied access. Please check FTP Setup parameters.	CAUSE: The FTP Server has reported that it did not store data. RESOLUTION: Verify the FTP server setup parameters, as indicated on the FTP Setup Parameters screen (see “FTP Setup” in Chapter 8 of the 4630/4630SW IP Telephone User’s Guide).
The FTP Server was unable to store the backup file.	CAUSE: The FTP Server has reported that it could not store the data. RESOLUTION: Verify administration and available capacity/filespace on the FTP Server.