netsh winsock reset
Try stopping these services in this order:
Starting the services in this Order:
To remove the user’s home directory pass the -r option to userdel, enter:
# userdel -r vivek
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.
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:
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”
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
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