petroid Posted October 14, 2005 Share Posted October 14, 2005 (edited) Those of you who have played with this build might have noticed that you cannot browse remote file shares. I then came up with the following (skip to bottom for the solution)... I found that I could not connect to a remote share. I decided to give Media Player a try anyway, and told it to aggregate music from my media server. Surprise, it actually worked after showing a request for a username and password. So now that's done, I thought I'd try to connect to the fileserver via it's UNC name. Success! I was now viewing the shares on the system. At that point it was painfully clear that the problem was with authentication. I rebooted and tried media player. None of the music worked. I tried the server's UNC path. No luck. It would seem that the reason Windows Explorer can't view fileshares is because it does not ask the user for his or her credentials. So to get around this you can use the NET command to open a connection manually. Simply open a command prompt (start > run > cmd) and type "net use \\[serverip]\[sharename] /user:[username] /persistent:yes" The sharename can be any share on the computer, for example Music. At this point it will request a password, and after that BAM! Windows Explorer should now show the shares on that remote computer. Those more advanced might like to either create a shortcut on the desktop, add it to their startup folder or even add the command as a logon script with the password already entered. Edited October 14, 2005 by petroid Link to comment Share on other sites More sharing options...
Mutiny32 Posted October 14, 2005 Share Posted October 14, 2005 Those of you who have played with this build might have noticed that you cannot browse remote file shares. I then came up with the following (skip to bottom for the solution)...I found that I could not connect to a remote share. I decided to give Media Player a try anyway, and told it to aggregate music from my media server. Surprise, it actually worked after showing a request for a username and password. So now that's done, I thought I'd try to connect to the fileserver via it's UNC name. Success! I was now viewing the shares on the system. At that point it was painfully clear that the problem was with authentication. I rebooted and tried media player. None of the music worked. I tried the server's UNC path. No luck. It would seem that the reason Windows Explorer can't view fileshares is because it does not ask the user for his or her credentials. So to get around this you can use the NET command to open a connection manually. Simply open a command prompt (start > run > cmd) and type "net use \\[serverip]\[sharename] /user:[username] /persistent:yes" The sharename can be any share on the computer, for example Music. At this point it will request a password, and after that BAM! Windows Explorer should now show the shares on that remote computer. Those more advanced might like to either create a shortcut on the desktop, add it to their startup folder or even add the command as a logon script with the password already entered. 586669142[/snapback] That's what I normally use anyway....but for the novice user, this is helpful. :) Link to comment Share on other sites More sharing options...
Brandon Live Veteran Posted October 14, 2005 Veteran Share Posted October 14, 2005 That's what I normally use anyway....but for the novice user, this is helpful. :) 586670966[/snapback] Exactly how many novice users do you think are going to be using an illegally leaked build of an interim less-than-beta-quality OS? Link to comment Share on other sites More sharing options...
Recommended Posts