If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Can't see Samba shares after build 10586
Right before I upgraded from build 10240 to build 10586, I copied a
number of files to a linux (samba) share. So I KNOW I could see them (the shares). After upgrading to build 10586 (~1 hr later), I could no longer see ANY shares that were not Microsoft. Absolutely no other changes made by me before or after the upgrade. I also received a couple of patches since then, but they apparently didn't address my issue. Has anyone else experienced this happening with their shares? |
Ads |
#2
|
|||
|
|||
Can't see Samba shares after build 10586
Dick posted this via
: Right before I upgraded from build 10240 to build 10586, I copied a number of files to a linux (samba) share. So I KNOW I could see them (the shares). After upgrading to build 10586 (~1 hr later), I could no longer see ANY shares that were not Microsoft. Absolutely no other changes made by me before or after the upgrade. I also received a couple of patches since then, but they apparently didn't address my issue. Has anyone else experienced this happening with their shares? No, but did you look in your C:\ windows.old folder? Why would anybody who is using Linux Samba share not have a separate partition for this [type of] software? My upgrade from from 10586.11 to 10586.14 completely omitted CCleaner and reset a couple of my default programs (.PDF, video). It also reset some of my privacy and monitoring preferences in the "Settings" interface, so I had to patrol all those and make a few re-adjustments... Microsoft should change their name to Mamasoft. (; -- I AM Bucky Breeder, (*(^; and, It's like Yogi Berra, RIP 9/22/2015, always used to say: "The future ain't what it used to be!" http://i.imgur.com/f193YWS.jpg?1 |
#3
|
|||
|
|||
Can't see Samba shares after build 10586
Bucky Breeder wrote:
Dick wrote: Right before I upgraded from build 10240 to build 10586, I copied a number of files to a linux (samba) share. After upgrading to build 10586 (~1 hr later), I could no longer see ANY shares that were not Microsoft. did you look in your C:\ windows.old folder? Why would anybody who is using Linux Samba share not have a separate partition for this [type of] software? I think he means now he's running 10586, he can't see shares on *another* box that happens to be running SAMBA, not that he's lost stuff locally? |
#4
|
|||
|
|||
Can't see Samba shares after build 10586
On 11/30/2015 12:22 PM, Andy Burns wrote:
Bucky Breeder wrote: Dick wrote: Right before I upgraded from build 10240 to build 10586, I copied a number of files to a linux (samba) share. After upgrading to build 10586 (~1 hr later), I could no longer see ANY shares that were not Microsoft. did you look in your C:\ windows.old folder? Why would anybody who is using Linux Samba share not have a separate partition for this [type of] software? I think he means now he's running 10586, he can't see shares on *another* box that happens to be running SAMBA, not that he's lost stuff locally? Andy, you are correct! I am talking about my ability to see shared folders on non-Microsoft computers connected to my local LAN. |
#5
|
|||
|
|||
Can't see Samba shares after build 10586
On 11/30/2015 12:37 PM, Dick wrote:
On 11/30/2015 12:22 PM, Andy Burns wrote: Bucky Breeder wrote: Dick wrote: Right before I upgraded from build 10240 to build 10586, I copied a number of files to a linux (samba) share. After upgrading to build 10586 (~1 hr later), I could no longer see ANY shares that were not Microsoft. did you look in your C:\ windows.old folder? Why would anybody who is using Linux Samba share not have a separate partition for this [type of] software? I think he means now he's running 10586, he can't see shares on *another* box that happens to be running SAMBA, not that he's lost stuff locally? Andy, you are correct! I am talking about my ability to see shared folders on non-Microsoft computers connected to my local LAN. As a further clarification, when I say 'I can't see the shares' I mean that they don't show up in file explorer when I select 'Network'. |
#6
|
|||
|
|||
Can't see Samba shares after build 10586
Andy Burns posted this via
: Bucky Breeder wrote: Dick wrote: Right before I upgraded from build 10240 to build 10586, I copied a number of files to a linux (samba) share. After upgrading to build 10586 (~1 hr later), I could no longer see ANY shares that were not Microsoft. did you look in your C:\ windows.old folder? Why would anybody who is using Linux Samba share not have a separate partition for this [type of] software? I think he means now he's running 10586, he can't see shares on *another* box that happens to be running SAMBA, not that he's lost stuff locally? Sooo, you are saying that "he" is having a networking problem since the update and not particularly a SAMBA issue? -- I AM Bucky Breeder, (*(^; and, It's like Yogi Berra, RIP 9/22/2015, always used to say: "The future ain't what it used to be!" http://i.imgur.com/f193YWS.jpg?1 |
#7
|
|||
|
|||
Can't see Samba shares after build 10586
Dick wrote:
Right before I upgraded from build 10240 to build 10586, I copied a number of files to a linux (samba) share. So I KNOW I could see them (the shares). After upgrading to build 10586 (~1 hr later), I could no longer see ANY shares that were not Microsoft. Absolutely no other changes made by me before or after the upgrade. I also received a couple of patches since then, but they apparently didn't address my issue. Has anyone else experienced this happening with their shares? Home group or workgroup=WORKGROUP setup ? Maybe you changed something during the initial usage of 10586 ? Paul |
#8
|
|||
|
|||
Can't see Samba shares after build 10586
Paul wrote:
Dick wrote: Right before I upgraded from build 10240 to build 10586, I copied a number of files to a linux (samba) share. So I KNOW I could see them (the shares). After upgrading to build 10586 (~1 hr later), I could no longer see ANY shares that were not Microsoft. Absolutely no other changes made by me before or after the upgrade. I also received a couple of patches since then, but they apparently didn't address my issue. Has anyone else experienced this happening with their shares? Home group or workgroup=WORKGROUP setup ? Maybe you changed something during the initial usage of 10586 ? Paul Nawww... he likely has to reset his netconfig. -- I AM Bucky Breeder, (*(^; and, It's like Yogi Berra, RIP 9/22/2015, always used to say: "The future ain't what it used to be!" http://i.imgur.com/f193YWS.jpg?1 |
#9
|
|||
|
|||
Can't see Samba shares after build 10586
On 11/30/2015 12:49 PM, Paul wrote:
Dick wrote: Right before I upgraded from build 10240 to build 10586, I copied a number of files to a linux (samba) share. So I KNOW I could see them (the shares). After upgrading to build 10586 (~1 hr later), I could no longer see ANY shares that were not Microsoft. Absolutely no other changes made by me before or after the upgrade. I also received a couple of patches since then, but they apparently didn't address my issue. Has anyone else experienced this happening with their shares? Home group or workgroup=WORKGROUP setup ? Maybe you changed something during the initial usage of 10586 ? Paul Paul, thanks for responding. As I indicated in the original post, I changed ABSOLUTELY NOTHING. Also, all my systems including the Samba machine have identical workgroup names. |
#10
|
|||
|
|||
Can't see Samba shares after build 10586
On 11/30/2015 1:47 PM, Dick wrote:
On 11/30/2015 12:49 PM, Paul wrote: Dick wrote: Right before I upgraded from build 10240 to build 10586, I copied a number of files to a linux (samba) share. So I KNOW I could see them (the shares). After upgrading to build 10586 (~1 hr later), I could no longer see ANY shares that were not Microsoft. Absolutely no other changes made by me before or after the upgrade. I also received a couple of patches since then, but they apparently didn't address my issue. Has anyone else experienced this happening with their shares? Home group or workgroup=WORKGROUP setup ? Maybe you changed something during the initial usage of 10586 ? Paul Paul, thanks for responding. As I indicated in the original post, I changed ABSOLUTELY NOTHING. Also, all my systems including the Samba machine have identical workgroup names. I do not use Homegroups. |
#11
|
|||
|
|||
Can't see Samba shares after build 10586
On Mon, 30 Nov 2015 13:47:56 -0500, Dick wrote:
Paul, thanks for responding. As I indicated in the original post, I changed ABSOLUTELY NOTHING. Also, all my systems including the Samba machine have identical workgroup names. Have you checked the workgroup name since the upgrade. There was a recent post where the workgroup name was found to be changed to WORKGROUP after an upgrade. -- Faster, cheaper, quieter than HS2 and built in 5 years; UKUltraspeed http://www.500kmh.com/ |
#12
|
|||
|
|||
Can't see Samba shares after build 10586
Dick wrote:
On 11/30/2015 1:47 PM, Dick wrote: On 11/30/2015 12:49 PM, Paul wrote: Dick wrote: Right before I upgraded from build 10240 to build 10586, I copied a number of files to a linux (samba) share. So I KNOW I could see them (the shares). After upgrading to build 10586 (~1 hr later), I could no longer see ANY shares that were not Microsoft. Absolutely no other changes made by me before or after the upgrade. I also received a couple of patches since then, but they apparently didn't address my issue. Has anyone else experienced this happening with their shares? Home group or workgroup=WORKGROUP setup ? Maybe you changed something during the initial usage of 10586 ? Paul Paul, thanks for responding. As I indicated in the original post, I changed ABSOLUTELY NOTHING. Also, all my systems including the Samba machine have identical workgroup names. I do not use Homegroups. There is SMB version. Which is not supposed to be a problem, except for the most decrepit hardware. https://social.technet.microsoft.com...nServerPreview http://blogs.technet.com/b/josebda/a...are-using.aspx There is user account and password as a gating item. Out of the box, some OSes don't even have File Sharing enabled. You have to indicate Home network, then go looking for the File Sharing setting. Attempting to create your first share on the machine, may expose the fact it isn't enabled. (While you would not expect these to be reset by an OS Upgrade 10586, stranger things have happened.) The LAN has a "Master Browser". Without consulting it, some OSes support direct IP, as in smb://127.0.0.1 format, so you can skip the browser or name determination step and go right to the desired machine. I used to do that for a time. Some older Linux machines, worked with an approach like that, to my WinXP machine. I've received some pretty strange responses on a protocol failure. Including refusing to wait for me to enter a password :-) And then claiming the password is wrong. That was in a mixed environment (an Apple Macintosh was involved). ******* In Win10, go to the Cortana search box, type "Powershell". Right click the program result and select "Run as administrator". Get-SmbConnection My Win10 is 10586 (Insider). I have a copy of WinXP with a share. The Get-SmbConnection claims it is running protoool version 1.5. I installed samba and system-config-samba on a fresh install of Ubuntu 1510. Had to do touch /etc/libuser.conf in order to make a file to keep system-config-samba happy. With that done, I could use system-config-samba to set up a share. (Win10 machine) Machine Version WinXP 1.5 Ubuntu1510 3.0 I can also see Master Browser elections flying around the net as well, in Wireshark. So they're deciding who is the boss in the fake (home LAN) domain. There is no sign of trouble here. I don't know what else to run, to shine light on the issue. In terms of troubleshooters, a troubleshooter would have to be written assuming it could get some sort of informative response from the other end. Single ended troubleshooting (a bunch of regsvc32 or a bunch of service restarts), probably isn't going to magically make it work. OK, so if I go to Win10 Control Panels, and "troubleshooters", then type "sharing" in the search box in the upper right hand corner, there are three troubleshooters listed. Two of the three will be useful to you. The third is for Homegroups. Troubleshooters sharing Incoming Connections Shared Folders HTH, Paul |
#13
|
|||
|
|||
Can't see Samba shares after build 10586
In message , Dick
writes On 11/30/2015 1:47 PM, Dick wrote: On 11/30/2015 12:49 PM, Paul wrote: Dick wrote: Right before I upgraded from build 10240 to build 10586, I copied a number of files to a linux (samba) share. So I KNOW I could see them (the shares). After upgrading to build 10586 (~1 hr later), I could no longer see ANY shares that were not Microsoft. Absolutely no other changes made by me before or after the upgrade. I also received a couple of patches since then, but they apparently didn't address my issue. Has anyone else experienced this happening with their shares? Home group or workgroup=WORKGROUP setup ? Maybe you changed something during the initial usage of 10586 ? Paul Paul, thanks for responding. As I indicated in the original post, I changed ABSOLUTELY NOTHING. Also, all my systems including the Samba machine have identical workgroup names. I do not use Homegroups. I think this may be the same problem that I raised in this ng under the title "Build 10586 and Networking". I, too have a couple of Linux machines on the workgroup using samba, and neither of my Build 10586 machines can see them or several of the older Windows machines. It worked on earlier builds. I don't use Homegroups. Scotties Lanscan can see nothing from the Build 10586 machine. -- Bill |
#14
|
|||
|
|||
Can't see Samba shares after build 10586
Paul wrote:
After upgrading to build 10586 (~1 hr later), I could no longer see ANY shares that were not Microsoft. One other thing. There was one report of a small issue with the workgroup name getting changed. Make sure the workgroup name being used, is the same everywhere. workgroup=WORKGROUP Paul |
#15
|
|||
|
|||
Can't see Samba shares after build 10586
Rodney Pont wrote:
On Mon, 30 Nov 2015 13:47:56 -0500, Dick wrote: Paul, thanks for responding. As I indicated in the original post, I changed ABSOLUTELY NOTHING. Also, all my systems including the Samba machine have identical workgroup names. Have you checked the workgroup name since the upgrade. There was a recent post where the workgroup name was found to be changed to WORKGROUP after an upgrade. Why would we ever need any other value :-) workgroup=WORKGROUP That's on a picture frame like my "Home Sweet Home" picture. Paul |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|