network-shares interview questions

Top network-shares frequently asked interview questions

How to make Windows 7 remember credentials for a Samba network drive?

I have a Samba share on my Ubuntu server which I map as a network drive on my Windows 7 Professional computer.

After every reboot it shows the drive as disconnected and to access it I have to renter my password even though every time I enter the password I check the 'Remember my credentials' box.

Is there way to have Windows 7 remember the credentials on a reboot/shutdown or is it just to remember them per session?

Source: (StackOverflow)

Why is it bad to map network drives in Windows?

There has been some spirited discussion within our IT department about mapping network drives. In particular, it has been said that mapping network drives is a bad thing and that adding DFS paths or network shares to your (Windows Explorer/Libraries) favorites is a far better solution.

Why is this the case?

Personally I find the convenience of z:\folder to be better than \\server\path\folder', particularly with cmd line and scripting (of course I'm not talking about hard-coded links, naturally!).

I have tried searching for pros and cons of mapped network drives, but I haven't seen anything other than 'should the network go down, the drive will be unavailable'. But this is a limitation of any network-accessed storage.

I have also been told that mapped network drives poll the network when the network resource is unavailable, however I haven’t found more information on this. Do network drives poll the network any more than a Windows Explorer library/favourite? Wouldn't this still be an issue with other network access mechanisms (that is, mapped Favourites) whenever Windows tries to enumerate the file system (for example, when a file/folder picker dialog is opened)?

Source: (StackOverflow)

Action can't be completed - open in another program

I have two screens with two Explorer windows open. Both are showing different subfolders in the same network path.

I pick a folder on the left window that I'd like to move to the right window, I drag it across, and an alert pops up:

The action can't be completed because the folder or a file in it is open in another program.

This is probably just the file indexer or the thumbnail database or whatever. I don't care, I want to do it anyway. This happens literally every time I want to move or rename a file or folder on a network drive.

How do I fix this?

Source: (StackOverflow)

How do I connect to a network share via the Windows Command Prompt?

Is there any way to connect to a network share via cmd.exe?

Source: (StackOverflow)

How can I Map a Network Drive with Password so it stays mapped after a reboot?

I mapped a network drive to a location that needs a password. Now whenever my computer starts up, it tells me that it could not connect to that network drive because a password is needed.

How do I make set my computer to remember the password for that mapped network drive?

My PC is running Windows XP Professional

Source: (StackOverflow)

list network shares from command prompt

Is it possible to browse a network for shares from the Windows command prompt?

I want to map a drive to a network share (pushd), but I can't remember the exact name of the machine or share. Is there a way to browse the network to find the shares via the command prompt?

Background: my Windows install was corrupted after an update and nothing's working now. I haven't backed up in a month, and I'm trying to do one final backup before I wipe it clean.

Source: (StackOverflow)

Windows 10 computer can't connect to any other computer on the network

Just upgraded my laptop to Windows 10. Everything seemed fine until I tried to connect to my Win7 desktop. Manually typing the name doesn't work (gives me Unspecified Error (0x80004005)), and when I open the Network section in Windows Explorer it is not listed there. What is listed is two of the other computers on the network, neither of which it will let me connect to (same Unspecified Error). All my computers (including the desktop) are functioning and on the network. They can all see each other, and if I turn on a share from my Win10 laptop then it can be connected to by the desktop. But for some reason, the Win10 machine can see only a few of the machines on the network and cannot connect to any of them, seen or unseen.

I thought at first it was the firewall, but no settings helped and even disabling it did nothing. I have made sure that all relevant computers have discovery turned on but that didn't change anything either. I can ping my desktop, both by IP and by name, but even after pinging I can't browse the drives or even see most of the PCs. By the way, this is impacting being able to connect to explicitly shared drives and to the implicit administrative shares (C$, etc.).


I realized that since I could ping the desktop that I could try connecting via IP address. That worked, and mysteriously fixed the problem of connecting by name. The Win10 laptop still won't "see" most of the network devices, but it now seems to be able to at least connect to them by name. No idea what's going on with it. I would still hope someone can weigh in with a proper fix for the network discovery (or whatever it is that's broken).

Source: (StackOverflow)

How to logon to a non-domain computer from one in a domain

I've met a rather annoying problem that should be very simple, but I can't seem to figure it out. I have a work laptop that is part of a domain, so my username is foobar\bob. I also have my home computer with no domain, just the username bob. I'm trying to connect to a share on my home computer from my work computer. It's asking me for my username and password, which is bob, but when I type in bob it assumes I mean foobar\bob, which of course doesn't work. I've tried to use hostname\bob, but that doesn't seem to work either...

What can I do here?

Both computers are running Windows 7.

Source: (StackOverflow)

How can I share a printer on Windows 7 x64 with Windows XP x86?

I'm trying to share a printer that's on Windows 7 64-bit with Windows XP 32-bit.

I've tried:

  • Using the Add Printer Wizard on XP
    • Selecting network printer
    • Browsing for the printer and selecting it from the list
    • Attempting to browse manually for the drivers, I receive the error `Windows cannot locate a suitable printer driver. Contact your administrator for help locating and installing a suitable driver.

I would prefer to load the drivers on the Windows 7 PC, much like a print server. I've tried:

  • Opening the printer properties
  • Clicking the Sharing tab
  • Clicking Additional Drivers...
  • Checking the x86 box
    • Attempting to add Windows XP x86 drivers, which generates the error The specified location does not contain the driver for the requested processor architecture

For what it's worth, this is an HP P4014n and I can't run a network cable. I'm using the universal print drivers PCL6.

How does printer sharing work with 64-bit Windows 7 acting as a server for Windows XP 32-bit?

  • What drivers do I need to install under the Additional drivers... dialog?
    • Are they XP drivers or Windows 7 drivers? Why?
    • Do driver versions have to match? Why?
  • Why does adding as a network printer and installing the XP drivers not work?
  • Why does adding a local printer and installing whatever drivers I want work?

Source: (StackOverflow)

Ubuntu + latest samba version, symlinks no longer work on share mounted in windows

I just apt-getted (apt-got?) the latest software for my Ubuntu 9.10 linux box, and I noticed that samba was the included in the update.

After the install, the symlinks in my home directory no longer work when mounted as a drive in my linux box. They worked literally seconds before I did the update. All my normal directories work just fine. Viewing the directory listing on the command line, all the files, dirs & links have the exact same permissions, yet this is the error I get:

Location is not available
L:\LinkDir is not accessible.
Access is denied.

I looked on the forums, and i saw this option for the smb.conf

follow symlinks = yes
wide symlinks = yes
unix extensions = no

I put those in, but they had no effect. Has anyone had this problem yet?

Source: (StackOverflow)

Mac OS can't connect to SMB shares after sleep

I used to access my local Windows 2008 file server's SMB shares on my recent (3 weeks old) MacBook Pro without problems. However, for a few days now, it fails to (re-)connect to the server after it woke up from sleep mode.

Finder just shows "connecting..." and hangs indefinitely. The same thing happens when I try it from the command line (mount -t smbfs). This happens via both WiFi and cable, I also tried turning networking off and back on. The only thing that helps is a reboot.

Any hints?

Edit to clarify: It's the Mac that's being put to sleep, not the server. I also found out that if I disconnect the shares before I put it to sleep, it will be able to reconnect after waking up.

Another Edit:

I did some more investigation and sniffed the network traffic. The Mac sends NetBIOS name queries and a status request (NBSTAT) to the server, the server responds, everything seems fine. After that, the Mac should open a SMB connection, but it doesn't do anything. No more packets follow.

I then found out that the real problem lies deeper. It seems it doesn't open a new connection because it thinks the old one, which has of course timed out on the server side, is still active. However, any program that tries to access its mount point or just the /Volumes directory hangs and can't even be killed. umount /Volumes/share - hangs. ls /Volumes - hangs. kill -9 any of these - doesn't help. Also, opening a file open dialog in any application causes it to hang as well!

The only thing that helps is a hard reboot. It seems to me there's something fundamentally wrong in OSX's SMB implementation if a timed out connection can trigger something like this.

Source: (StackOverflow)

How Do I Map a Drive Network Share Using the Linux Terminal?

Still getting used to Linux, and the GUI is great. I have Ubuntu 10 and I can go to Network and see the Windows network. Then double clicking this gets me to the drives that are shared. Then when I go back to the terminal and use:

cd ~/.gvfs

I can see the mapped drives. But it would be nice if I could this without all the mouse clicking. So how do I map network drives in the terminal, something akin to net use for Windows.

EDIT: Not sure what happened, but this is what I did to get it to work. I created the directory for the share in /media and then ran:

sudo mount -t cifs -o username=nicorellius //server/share/ /media/share

and it said command couldn't be found. So i thought I would go ahead and use smbfs so I ran:

sudo apt-get install smbfs

I tried the command suggested with smbfs instead of cifs and that didn't work either. So I tried again and then the next time I ran:

sudo mount -t cifs -o username=nicorellius //server/share/ /media/share

it worked and I could navigate to the directory with cd.

Source: (StackOverflow)

Turn off windows 7 message "could not reconnect to all network drives"

How do I turn off the little popup bubble in systray that says "could not reconnect to all network drives" ?

I am aware that a particular drive is only accessible at certain times so I dont need an annoying little popup message evertime I reboot.

Ive seen similar popup messages get hidden through means of registry editor, but google turned up no answers for this one.

Source: (StackOverflow)

Why is Notepad++ so slow when dealing with files stored on a network share?

Recently Notepad++ seems to be very slow when dealing with files that are located on a network share.

I am editing small files (e.g. web.config) and it is slow to:

  • Initially open a file on a network share.
  • Switch tabs back to a file on a network share.
  • Switch back to notepad++ after using another application.

My guess is when switching tabs back to a network file it tries to check if someone else has modified the file (I could live with turning this off and it could check on save).

I am on a "fast" local network and have only noticed this problem recently.

My local PC is Windows 7 Enterprise and the servers are Windows Server 2003 and 2008.

Source: (StackOverflow)

OS X: How to avoid having to re-connect to network share after NAS was turned off?

I use Mac OS 10.6 to connect to a NAS drive using the afp protocol (Finder -> Go -> Connect To Server). I have set up the NAS to automatically power off during the day, and power on in the evening. Now what happens is this: each time the NAS powers off, the network share disappears. After the NAS has turned on again, I have to manually re-connect to the network share.

My girlfriend uses Windows 7 to connect to the same share. For her, when the NAS is off, the network drive is still visible in "My Computer", albeit with a "not connected" marker. When the NAS is on, she simply opens the network drive and Windows notices that it is available again.

Is there a way to make Mac OS behave in a comparable way to Windows here? I want Mac OS to automatically reconnect to the drive when it is available again (or at least when I try to access it).

I know I can turn the connection into a login item, but I rarely re-login. I want this to work automatically, while already being logged in.

Source: (StackOverflow)