 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Windows 7 mapped drives with Client Access</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/windows-7-mapped-drives/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/windows-7-mapped-drives/</link>
	<description></description>
	<lastBuildDate>Thu, 23 May 2013 15:11:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: stark99</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/windows-7-mapped-drives/#comment-73278</link>
		<dc:creator>stark99</dc:creator>
		<pubDate>Tue, 02 Feb 2010 11:56:23 +0000</pubDate>
		<guid isPermaLink="false">#comment-73278</guid>
		<description><![CDATA[I have the 64bit version of Windows 7 home premium. The install cd I have for client access 6.1 would not run because of compatibility problems. I can map a drive to any PC on our network just not the Iseries.

Thanks]]></description>
		<content:encoded><![CDATA[<p>I have the 64bit version of Windows 7 home premium. The install cd I have for client access 6.1 would not run because of compatibility problems. I can map a drive to any PC on our network just not the Iseries.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: woodengineer</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/windows-7-mapped-drives/#comment-73222</link>
		<dc:creator>woodengineer</dc:creator>
		<pubDate>Mon, 01 Feb 2010 17:09:25 +0000</pubDate>
		<guid isPermaLink="false">#comment-73222</guid>
		<description><![CDATA[According to IBM, Client Access 6.1 is required for Windows 7.  We are experimenting with that environmant now.  So far, so good.]]></description>
		<content:encoded><![CDATA[<p>According to IBM, Client Access 6.1 is required for Windows 7.  We are experimenting with that environmant now.  So far, so good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pjb0222</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/windows-7-mapped-drives/#comment-73217</link>
		<dc:creator>pjb0222</dc:creator>
		<pubDate>Mon, 01 Feb 2010 16:45:56 +0000</pubDate>
		<guid isPermaLink="false">#comment-73217</guid>
		<description><![CDATA[If your backend requires NTLM authentication, you will need to enable it on WIndows 7.  
You can go into GPO Edit and enable NTLM.  By default Windows 7 (and Vista) only enable NTLM v2.

MS Technet on NTLM in Windows 7 and Server 2008 detailing how to enable NTLM.
&lt;a href=&quot;http://technet.microsoft.com/en-us/library/dd566199(WS.10).aspx&quot;&gt;&lt;/a&gt;

Another item to check is when and how the drives are mapped.  If the user ID has local administrative access and you are using a login script, then there is a Registry modification you need to make on the Windows 7 (and Vista) systems.

Setting to allow drive mappings between admin and non-admin sessions
&lt;pre&gt;HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem&lt;/pre&gt;
EnableLinkedConnections =(dword)1]]></description>
		<content:encoded><![CDATA[<p>If your backend requires NTLM authentication, you will need to enable it on WIndows 7.<br />
You can go into GPO Edit and enable NTLM.  By default Windows 7 (and Vista) only enable NTLM v2.</p>
<p>MS Technet on NTLM in Windows 7 and Server 2008 detailing how to enable NTLM.<br />
<a href="http://technet.microsoft.com/en-us/library/dd566199(WS.10).aspx"></a></p>
<p>Another item to check is when and how the drives are mapped.  If the user ID has local administrative access and you are using a login script, then there is a Registry modification you need to make on the Windows 7 (and Vista) systems.</p>
<p>Setting to allow drive mappings between admin and non-admin sessions</p>
<pre>HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem</pre>
<p>EnableLinkedConnections =(dword)1</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tomliotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/windows-7-mapped-drives/#comment-73146</link>
		<dc:creator>tomliotta</dc:creator>
		<pubDate>Fri, 29 Jan 2010 23:43:59 +0000</pubDate>
		<guid isPermaLink="false">#comment-73146</guid>
		<description><![CDATA[If this is indeed &lt;i&gt;iseries os 5.1&lt;/i&gt; and &lt;i&gt;Windows 7&lt;/i&gt;, be aware that Microsoft began using some changed protocols for Windows networking in Windows XP. IBM began changing the *FILE server (and therefore NetServer) in i5/OS V5R4 to allow the newer MS protocols to work effectively.

Discussion is generally seen in the &lt;a href=&quot;http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzahl/rzahlwhatsnew.htm&quot;&gt;NetServer What&#039;s new for V5R4&lt;/a&gt; topic, as well as &lt;a href=&quot;http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzahl/rzahltrblshootns.htm&quot;&gt;Troubleshooting iSeries NetServer (V5R4)&lt;/a&gt; topic under Troubleshooting user profile connections and Troubleshooting file share problems,  as well as related troubleshooting topics for V5R4.

I don&#039;t have specific info for Windows 7. It might be necessary to determine what the connection protocols are and to see if it&#039;s possible to use older behavior in Windows 7.

That&#039;s all just secondary info and may have nothing to do with whatever the actual problem is. Still, I would try the same connection with a Windows 2000 PC (or possibly basic Linux and Samba) to ensure that general configuration is still proper for V5R1 before digging into what Windows 7 might be doing.

Tom]]></description>
		<content:encoded><![CDATA[<p>If this is indeed <i>iseries os 5.1</i> and <i>Windows 7</i>, be aware that Microsoft began using some changed protocols for Windows networking in Windows XP. IBM began changing the *FILE server (and therefore NetServer) in i5/OS V5R4 to allow the newer MS protocols to work effectively.</p>
<p>Discussion is generally seen in the <a href="http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzahl/rzahlwhatsnew.htm">NetServer What&#8217;s new for V5R4</a> topic, as well as <a href="http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzahl/rzahltrblshootns.htm">Troubleshooting iSeries NetServer (V5R4)</a> topic under Troubleshooting user profile connections and Troubleshooting file share problems,  as well as related troubleshooting topics for V5R4.</p>
<p>I don&#8217;t have specific info for Windows 7. It might be necessary to determine what the connection protocols are and to see if it&#8217;s possible to use older behavior in Windows 7.</p>
<p>That&#8217;s all just secondary info and may have nothing to do with whatever the actual problem is. Still, I would try the same connection with a Windows 2000 PC (or possibly basic Linux and Samba) to ensure that general configuration is still proper for V5R1 before digging into what Windows 7 might be doing.</p>
<p>Tom</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.013 seconds using memcached
Object Caching 310/313 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-23 15:37:41 -->