<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Browsing on Michael’s Domain</title><link>https://jeltsch.org/en/tags/browsing/</link><description>Recent content in Browsing on Michael’s Domain</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2002 - 2026 Michael Jeltsch.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:18:18 +0300</lastBuildDate><atom:link href="https://jeltsch.org/en/tags/browsing/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows NT, network browsing, mounting and disconnecting from network drives (command netuse)</title><link>https://jeltsch.org/en/windows_nt_network_browsing_mounting_and_disconnecting_from_network_drives_command_netuse/</link><pubDate>Thu, 05 Apr 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/windows_nt_network_browsing_mounting_and_disconnecting_from_network_drives_command_netuse/</guid><description>&lt;p&gt;Network browsing in Windows is a mystery. Sometimes some computers simply don&amp;rsquo;t show up when browsing a network. This seems to be especially true for Linux servers. Under newer versions of the Windows OS (2000, XP), you can connect to a server (if you know its IP adress) via the mount network drive command even though the network browser cannot see that server. Windows NT doesn&amp;rsquo;t have that option. The only possibility is to use the &amp;ldquo;net use&amp;rdquo; command from the command line. This is uncomfortable, although one can make .bat files for frequently used connections. The command is: &lt;code&gt;net use * \\ip-adress\username&lt;/code&gt; The asterisk assings the share to the next available drive letter (of course you can assign manually to e.g. H:). To delete this specific network drive type: &lt;code&gt;net use H: /delete&lt;/code&gt; Actually, even if you can browse and connect without needing the command line, you need the command line always when you want to disconnect a share from an NT server. Funnily Windows NT has no other way but to type &lt;code&gt;netuse * /delete&lt;/code&gt; In some discussion threads it was mentioned, that one should switch on WINS support in the Linux server&amp;rsquo;s smb.conf file &lt;code&gt;wins support = Yes&lt;/code&gt;. If you connect to Linux, make sure that Samba is running and that the user to whose home folder you want to connect to has an entry &amp;amp; password in the smb database (this is NOT preconfigured even in Suse 9.2): &lt;code&gt;as root: smbpasswd -a username&lt;/code&gt; It didn&amp;rsquo;t help me, though. MacOS X computers (10.3) show up now without problems (older MacOS X versions also had problems). Maybe I should compare the smb.conf files or just copy it over to my Suse 9.1.&lt;/p&gt;</description></item></channel></rss>