<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Server Sitters Tech Corner &#187; Windows Servers</title>
	<atom:link href="http://serversitters.com/technical/category/windows-servers/feed/" rel="self" type="application/rss+xml" />
	<link>http://serversitters.com/technical</link>
	<description>Outsourced Web Hosting Support</description>
	<lastBuildDate>Wed, 15 Dec 2010 12:03:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Sending e-mail with CDO</title>
		<link>http://serversitters.com/technical/windows-servers/sending-e-mail-with-cdo/</link>
		<comments>http://serversitters.com/technical/windows-servers/sending-e-mail-with-cdo/#comments</comments>
		<pubDate>Sun, 20 Dec 2009 00:48:51 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Windows Servers]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=122</guid>
		<description><![CDATA[CDONTs Microsoft has discontinued the use of CDONTs on Windows 2000, Windows XP and Windows 2003. If you have used CDONTs in your ASP applications, you should update the code and use the new CDO technology. Sending e-mail with CDO CDO (Collaboration Data Objects) is a Microsoft technology that is designed to simplify the creation [...]]]></description>
			<content:encoded><![CDATA[<p>CDONTs<br />
Microsoft has discontinued the use of CDONTs on Windows 2000, Windows XP and Windows 2003. If you have used CDONTs in your ASP applications, you should update the code and use the new CDO technology.</p>
<p>Sending e-mail with CDO<br />
CDO (Collaboration Data Objects) is a Microsoft technology that is designed to simplify the creation of messaging applications.<br />
CDO is a built-in component in ASP. The URL below will provide you with some good examples on how to use CDO:</p>
<p><a href="http://www.w3schools.com/asp/asp_send_email.asp">http://www.w3schools.com/asp/asp_send_email.asp</a> </p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/windows-servers/sending-e-mail-with-cdo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>port 25 telnet example</title>
		<link>http://serversitters.com/technical/windows-servers/port-25-telnet-example/</link>
		<comments>http://serversitters.com/technical/windows-servers/port-25-telnet-example/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 18:41:28 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Windows Servers]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=88</guid>
		<description><![CDATA[telnet yourdomain.com 25 helo yourdomain.com mail from: test@yourdomain.com rcpt to: test@yourdomain.com DATA TestMessage . This is an effective method for testing the connection to port 25 of a mail server to ensure it&#8217;s allowing connections.]]></description>
			<content:encoded><![CDATA[<p>telnet yourdomain.com 25<br />
helo yourdomain.com<br />
mail from: test@yourdomain.com<br />
rcpt to: test@yourdomain.com<br />
DATA<br />
TestMessage<br />
.</p>
<p>This is an effective method for testing the connection to port 25 of a mail server to ensure it&#8217;s allowing connections.</p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/windows-servers/port-25-telnet-example/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to run a trace route</title>
		<link>http://serversitters.com/technical/windows-servers/how-to-run-a-trace-route/</link>
		<comments>http://serversitters.com/technical/windows-servers/how-to-run-a-trace-route/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 18:36:16 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Windows Servers]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=84</guid>
		<description><![CDATA[In Windows Start &#8211;> Run Open: type in cmd Click OK At the prompt type in: tracert yourdomain.com Let the trace route complete and then copy it &#8211; Right Click &#8211;> Select All Press Enter and then include it in your reply to support]]></description>
			<content:encoded><![CDATA[<p>In Windows<br />
Start &#8211;> Run<br />
Open: type in cmd<br />
Click OK<br />
At the prompt type in:<br />
tracert yourdomain.com<br />
Let the trace route complete and then copy it &#8211; Right Click &#8211;> Select All<br />
Press Enter<br />
and then include it in your reply to support</p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/windows-servers/how-to-run-a-trace-route/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Change RDP port for security</title>
		<link>http://serversitters.com/technical/security/change-rdp-port-for-security/</link>
		<comments>http://serversitters.com/technical/security/change-rdp-port-for-security/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 17:03:04 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Windows Servers]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=75</guid>
		<description><![CDATA[Server: How do I change the Terminal Server (or RDP) listening port? By default, Terminal Server (For Windows 2000 and Windows Server 2003) and Remote Desktop Protocol (for Windows XP and Windows Server 2003) listens on TCP port 3389. To change the default port for all new connections created on the Terminal Server: 1. Run [...]]]></description>
			<content:encoded><![CDATA[<p>Server:<br />
How do I change the Terminal Server (or RDP) listening port?</p>
<p>By default, Terminal Server (For Windows 2000 and Windows Server 2003) and Remote Desktop Protocol (for Windows XP and Windows Server 2003) listens on TCP port 3389.</p>
<p>To change the default port for all new connections created on the Terminal Server:</p>
<p>   1. Run Regedit and go to this key:</p>
<p>    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Control\Terminal Server\WinStations\RDP-Tcp</p>
<p>   2. Find the &#8220;PortNumber&#8221; subkey and notice the value of 00000D3D, hex for (3389). Modify the port number in Hex and save the new value.</p>
<p>You can now connect to the new port by using the &#8220;old&#8221; Windows 2000 Terminal Server client. A better option is to use the XP RDP 5.1 client (Download RDP 5.1). Even better, use the newer Windows Server 2003 RDP 5.2 client (Download RDP 5.2).</p>
<p>You&#8217;ll need to configure your TS client to connect to the new port. Although changing the connection port on the RDP clients is quite easy, you CAN also change the connection port for the TS client. See Related Articles list for more info.</p>
<p>Client Side:<br />
just add the new port in the connection string when connecting via RDP i.e.<br />
win.yourservername.com:$NEWPORT</p>
<p>Default port is 3389</p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/security/change-rdp-port-for-security/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using SCP in Windows via SSH</title>
		<link>http://serversitters.com/technical/windows-servers/using-scp-in-windows-via-ssh/</link>
		<comments>http://serversitters.com/technical/windows-servers/using-scp-in-windows-via-ssh/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 17:01:38 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Windows Servers]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=73</guid>
		<description><![CDATA[In order to use SSH with SCP on a Windows server you must first install an SSH service. A great tool to use for this is CYGWIN. After you install this service you can then use a lot of useful SSH tools such as SCP. How to copy files from your backup Linux Server to [...]]]></description>
			<content:encoded><![CDATA[<p>In order to use SSH with SCP on a Windows server you must first install an SSH service.  A great tool to use for this is <a href="http://www.cygwin.com">CYGWIN</a>.</p>
<p>After you install this service you can then use a lot of useful SSH tools such as SCP.  </p>
<p><strong>How to copy files from your backup Linux Server to Windows using SCP:</strong><br />
You must login to the Windows server and start the cygwin SSH service</p>
<p>Login to the backup Linux server and run the following Command:<br />
scp $filename $Administrator@windows.yourservername.com:/</p>
<p>The file is then copied over to your windows server into the following folder:<br />
C:\cygwin</p>
<p>We usually suggesting turning off the service on the windows server once the restore is complete.  This is just a security precaution since the service is rarely used.<br />
Turn off the SSH service on the Winodws Server &#8211; service named Cygwin SSH</p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/windows-servers/using-scp-in-windows-via-ssh/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Enable Failed Logins in the Event Viewer</title>
		<link>http://serversitters.com/technical/windows-servers/enable-failed-logins-in-the-event-viewer/</link>
		<comments>http://serversitters.com/technical/windows-servers/enable-failed-logins-in-the-event-viewer/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 16:56:24 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Windows Servers]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=71</guid>
		<description><![CDATA[Log on as an administrator via RDP Click Start, click Run, type mmc /a (note the space between mmc and /a), and then click OK. On the File menu, click Add/Remove Snap-in, and then click Add. Under Snap-in, click Group Policy, and then click Add. In Select Group Policy Object, click Local Computer, click Finish, [...]]]></description>
			<content:encoded><![CDATA[<p>Log on as an administrator via RDP</p>
<p>Click Start, click Run, type mmc /a (note the space between mmc and /a), and<br />
then click OK. </p>
<p>On the File menu, click Add/Remove Snap-in, and then click Add.</p>
<p>Under Snap-in, click Group Policy, and then click Add.</p>
<p>In Select Group Policy Object, click Local Computer, click Finish, click<br />
Close, and then click OK.</p>
<p>At this point, you might want to save this console for further use. Note you<br />
can add multiple snap-in and manage multiple computers from this console.</p>
<p>On the left hand side, navigate to Local Computer Policy > Computer<br />
Configuration > Windows Settings > Security Settings > Local Policies ><br />
Audit Policy </p>
<p>On the right hand side, double-click &#8220;Audit Logon Events&#8221;</p>
<p>Check the boxes for Success and Failure, click OK</p>
<p>The failed login attempts will be found in the Event Viewer.  It will<br />
include the time it happened, the username they used, and the IP they tried<br />
from.</p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/windows-servers/enable-failed-logins-in-the-event-viewer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Windows winsock network and catalog log files</title>
		<link>http://serversitters.com/technical/windows-servers/windows-winsock-network-and-catalog-log-files/</link>
		<comments>http://serversitters.com/technical/windows-servers/windows-winsock-network-and-catalog-log-files/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 16:54:20 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Windows Servers]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=69</guid>
		<description><![CDATA[Reset network catalog and log file: netsh winsock reset catalog netsh int ip reset log.txt view the catalog: netsh winsock show catalog]]></description>
			<content:encoded><![CDATA[<p>Reset network catalog and log file:<br />
<code>netsh winsock reset catalog<br />
netsh int ip reset log.txt</code></p>
<p>view the catalog:<br />
<code>netsh winsock show catalog</code></p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/windows-servers/windows-winsock-network-and-catalog-log-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

