<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Issue Connecting to network paths in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Issue-Connecting-to-network-paths/m-p/452092#M43533</link>
    <description>&lt;P&gt;&lt;SPAN&gt;thanks for the response&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;How both the shares using same vserver were accessible from the same source server via different credentials from the migration date till mid of February 2024? Please note the lab team was using the named CIFS path for i2q and Tips shares.&lt;/LI&gt;&lt;LI&gt;Is there any way to set the primary and secondary on the share level?&lt;/LI&gt;&lt;/OL&gt;</description>
    <pubDate>Wed, 17 Apr 2024 02:26:27 GMT</pubDate>
    <dc:creator>Mohi1</dc:creator>
    <dc:date>2024-04-17T02:26:27Z</dc:date>
    <item>
      <title>Issue Connecting to network paths</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Issue-Connecting-to-network-paths/m-p/452058#M43527</link>
      <description>&lt;P&gt;we have 2 cifs shares on vserver&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Both were working&amp;nbsp; till date but since yesterday only one of the paths connect at one time with the respective credentials.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;we are getting below , if we try to connect to other share&amp;nbsp;&lt;/P&gt;&lt;P&gt;Error : The network Folder Specified is currently mapped using a different username and password&lt;/P&gt;&lt;P&gt;To connect using a different user name and password, first disconnect existing mapping to this network drive&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The issue may be due to trying to connect to the same server with different credentials, both share1 &amp;amp; share 2 paths were working till yesterday the issue occurred today. Kindly help resolve the same as it will impact our&amp;nbsp; scheduler.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am suspecting that earlier the one CIFS share was connecting through IP1 and Other CIFS share was connecting through IP2 or vice versa. Thus allowing both&amp;nbsp; shares to connect from same source server. Currently the connection is going to the same IP either IP1 or IP2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have tested the scenario through&amp;nbsp; and it worked when I connected one of them with IP1 and other with IP2 via respective service accounts&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please advise on the fix since as per norms, we should not use the Ip addresses directly. The naming convention should be used. Please advise.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:39:05 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Issue-Connecting-to-network-paths/m-p/452058#M43527</guid>
      <dc:creator>Mohi1</dc:creator>
      <dc:date>2025-06-04T09:39:05Z</dc:date>
    </item>
    <item>
      <title>Re: Issue Connecting to network paths</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Issue-Connecting-to-network-paths/m-p/452063#M43528</link>
      <description>&lt;P&gt;I dont see the ONTAP version here but you can try applying the solution in the below KB and see if it fixes the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.netapp.com/onprem/ontap/da/NAS/Multiple_connections_to_a_server_or_shared_resource_by_the_same_user_is_not_allowed_error_while_accessing_CIFS_share" target="_blank"&gt;https://kb.netapp.com/onprem/ontap/da/NAS/Multiple_connections_to_a_server_or_shared_resource_by_the_same_user_is_not_allowed_error_while_accessing_CIFS_share&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Apr 2024 13:33:47 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Issue-Connecting-to-network-paths/m-p/452063#M43528</guid>
      <dc:creator>ChLokesh</dc:creator>
      <dc:date>2024-04-16T13:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: Issue Connecting to network paths</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Issue-Connecting-to-network-paths/m-p/452092#M43533</link>
      <description>&lt;P&gt;&lt;SPAN&gt;thanks for the response&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;How both the shares using same vserver were accessible from the same source server via different credentials from the migration date till mid of February 2024? Please note the lab team was using the named CIFS path for i2q and Tips shares.&lt;/LI&gt;&lt;LI&gt;Is there any way to set the primary and secondary on the share level?&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Wed, 17 Apr 2024 02:26:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Issue-Connecting-to-network-paths/m-p/452092#M43533</guid>
      <dc:creator>Mohi1</dc:creator>
      <dc:date>2024-04-17T02:26:27Z</dc:date>
    </item>
  </channel>
</rss>

