New
#11
Net share will show all your shares and show c is shared as c$ you must open the cmd prompt THEN type or it will just flash up
Net share will show all your shares and show c is shared as c$ you must open the cmd prompt THEN type or it will just flash up
I have things to complete yet to catch up. I gather these are the standard responses for workgroup difficulties not unique to Windows 10. I see no advantage to move to Homegroup sharing.
I'll report back when I can make a copy I can look at while doing the procedure. I move slowly through this.
Not saying you shouldn't use Blackbird Privacy Suite, to each his own ...
I took a minute to look at the Blackbird Privacy Suite site and it can block/turn off stuff windows needs for networking like some services, ipv6, etc. Not sure what settings you've applied with it, but I would undo them before I wasted time on troubleshooting Win10 networking itself.
Last edited by Eagle51; 26 Sep 2018 at 01:59.
Yes undoing uninstalling Blackbird may be needed. Or learning how to use the 43 switches to bring
things in or out. I was attracted to the ability to get rid of Cortana and some other things. But going through the description I could not identify where a problem could crop up.
That NetBIOS problem is likely my best target for now and I will do the operation. My third
machine (can't remember if I ran BB on it but the .exe doesn't seem to be on there) has a backup drive and that one which I made some time ago shows NetBIOS active and is finding the other nodes of the homenet.
I'll report back when I have a result.
Hey loninappleton,
Yea, the netbios over tcp/ip issue can be very difficult to fix. If the adapter settings show it as default or enabled and ipconfig /all shows it as disabled ... you can check the registry to see if what it shows for NetbiosOptions. IF the registry shows NetbiosOptions is 0 or 1 ... then it usually requires an in-place upgrade/repair or clean install to actually fix it being disabled. Obviously that's your call and you could try to fix it manually, but it's a bit involved.
Note: Valid values for NebiosOptions ... Default is 0 | Enabled is 1 | Disabled is 2
Open PowerShell as Admin and run the following command ...
Get-ChildItem -Recurse -Path HKLM:SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces | Format-Table -AutoSize
Powershell is another thing I'm trying to get a handle on-- just rudamentary commands.
I'm on the list for getting a poershell book at the local library-- just to do the simple things you mention.
On that, for troubleshooting how can I compare what I have in the working HD with the problem
HD or HDs on the system? I've found the one example of NetBIOS on or off in some of these through
ipconfig.
Also, while I think of it, some setting in Win7 or 10 on here has 'diagnostics' turned off. I don't
know how or why-- another Microsoft mystery.
K, no problem.Powershell is another thing I'm trying to get a handle on-- just rudamentary commands. I'm on the list for getting a poershell book at the local library-- just to do the simple things you mention.
Yea, ipconfig is just an easy way to see what the adapter settings are. It's difficult to compare 2 systems for the netbios issue, as they will have different network adapters, instance ids, etc.On that, for troubleshooting how can I compare what I have in the working HD with the problem
HD or HDs on the system? I've found the one example of NetBIOS on or off in some of these through ipconfig.
Not sure on that, sorry.Also, while I think of it, some setting in Win7 or 10 on here has 'diagnostics' turned off. I don't
know how or why-- another Microsoft mystery.
If you want to try using the following PowerShell script ... On the PC where ipconfig /all shows Netbios as disabled. Do the following and I'll take a look to see what/if anything jumps out at me.
Note: IF your not comfortable doing the following, then don't :)
1. Click on Start > Scroll Down to Windows PowerShell and Click on it to Expand > Right Click on the 1st entry > Windows PowerShell > Run as Administrator
2. The PowerShell Window will open.
3. Copy/Paste the following into the PowerShell Window, make sure you hit enter after the last line.
4. The following script makes NO changes to your PC.
5. It reveals NO personal information, just your PC name.
6. It creates a .txt file on your Desktop (it assumes your Desktop Folder has not been moved)
7. Upload the .txt file in your post.
$(
write-output "CHECKING LINKAGE/INTERFACES $($env:computername) @ $(get-date -format g)"
write-output "==============="
write-output "ALL ADAPTERS"
write-output "==============="
Get-NetAdapter -IncludeHidden -Name "*" | Format-Table -AutoSize -Property "Name", "InterfaceDescription", "InstanceID"
write-output "==============="
write-output "NETBT INTERFACES"
write-output "==============="
Get-ChildItem -Recurse -Path HKLM:SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces | Format-Table -AutoSize
write-output "==============="
write-output "LANMAN SERVER LINKAGE"
write-output "==============="
Get-ItemProperty -Path HKLM:SYSTEM\CurrentControlSet\Services\LanmanServer\Linkage | Format-List -Property "Export","Bind","Route"
write-output "==============="
write-output "LANMAN WORKSTATION LINKAGE"
write-output "==============="
Get-ItemProperty -Path HKLM:SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Linkage | Format-List -Property "Export","Bind","Route"
write-output "==============="
write-output "NETBIOS LINKAGE"
write-output "==============="
Get-ItemProperty -Path HKLM:SYSTEM\CurrentControlSet\Services\NetBIOS\Linkage | Format-List -Property "Export","Bind","Route"
write-output "==============="
write-output "NETBT LINKAGE"
write-output "==============="
Get-ItemProperty -Path HKLM:SYSTEM\CurrentControlSet\Services\NetBT\Linkage | Format-List -Property "Export","Bind","Route"
write-output "==============="
write-output "TCPIP4 LINKAGE"
write-output "==============="
Get-ItemProperty -Path HKLM:SYSTEM\CurrentControlSet\Services\Tcpip\Linkage | Format-List -Property "Export","Bind","Route"
write-output "==============="
write-output "TCPIP6 LINKAGE"
write-output "==============="
Get-ItemProperty -Path HKLM:SYSTEM\CurrentControlSet\Services\Tcpip6\Linkage | Format-List -Property "Export","Bind","Route"
) > "$($env:userprofile)\Desktop\$env:computername-LINKAGE-INTERFACES.txt"
@Ioninappleton: haven't seen much (very little!) discussion of Blackbird here on the forums. Folks here are more familiar with tools like O&O Shutup10. If you encounter problems with Blackbird, and aren't completely committed to that offering (which I know nothing about), you might want to try the other aforementioned option as a possible alternative.
HTH,
--Ed--
Yes because I'm in a spot of not being sure just what was run or once run what it _did_ I may just wipe
the troublesome drive and go to backup which works and make a new backup.
I simply used all the defaults _when running_ Blackbird but I do not have a good trace back to the
action meaning the program may have been run form my thumb drive.
But I did do the instruction given on the problem drive to check Adapter settings which
were all the same as in the brief tutorial. I'll respond a bit to that directly.