folder sharing issue



  • I can now path to 192.168.128.100\c$



  • Have since tried to uninstall the nic and make registry changes (there were a lot that were out of wack apparently) but with no luck still.

    edit Upon this and changing registry keys I was able to get it to communicate and work properly.



  • @WrCombs said in folder sharing issue:

    I can now path to 192.168.128.100\c$

    but when i path to 192.168.128.100
    I get the same error i was before.



  • @WrCombs said in folder sharing issue:

    @WrCombs said in folder sharing issue:

    I can now path to 192.168.128.100\c$

    but when i path to 192.168.128.100
    I get the same error i was before.

    192.168.128.100 is not a SMB or CIFS path. . . so of course it would error. You don't share out an IP address, but resources hosted at that address, IE C$.



  • @DustinB3403 said in folder sharing issue:

    @WrCombs said in folder sharing issue:

    @WrCombs said in folder sharing issue:

    I can now path to 192.168.128.100\c$

    but when i path to 192.168.128.100
    I get the same error i was before.

    192.168.128.100 is not a SMB or CIFS path. . . so of course it would error. You don't share out an IP address, but resources hosted at that address, IE C$.

    I mapped the Bootdrv of the server on the terminals.
    😃 I did it I fixed it.
    it was a registry setting.
    Im not fucking with it anymore.
    its working.



  • @WrCombs said in folder sharing issue:

    @DustinB3403 said in folder sharing issue:

    @WrCombs said in folder sharing issue:

    @WrCombs said in folder sharing issue:

    I can now path to 192.168.128.100\c$

    but when i path to 192.168.128.100
    I get the same error i was before.

    192.168.128.100 is not a SMB or CIFS path. . . so of course it would error. You don't share out an IP address, but resources hosted at that address, IE C$.

    I mapped the Bootdrv of the server on the terminals.
    😃 I did it I fixed it.
    it was a registry setting.
    Im not fucking with it anymore.
    its working.

    Cool cool, so now just charge that customer for 24 hours of horsing around and wash your hands of this job until it blows up again. . .



  • @DustinB3403 said in folder sharing issue:

    @WrCombs said in folder sharing issue:

    @DustinB3403 said in folder sharing issue:

    @WrCombs said in folder sharing issue:

    @WrCombs said in folder sharing issue:

    I can now path to 192.168.128.100\c$

    but when i path to 192.168.128.100
    I get the same error i was before.

    192.168.128.100 is not a SMB or CIFS path. . . so of course it would error. You don't share out an IP address, but resources hosted at that address, IE C$.

    I mapped the Bootdrv of the server on the terminals.
    😃 I did it I fixed it.
    it was a registry setting.
    Im not fucking with it anymore.
    its working.

    Cool cool, so now just charge that customer for 24 hours of horsing around and wash your hands of this job until it blows up again. . .

    you done?



  • @WrCombs said in folder sharing issue:

    @DustinB3403 said in folder sharing issue:

    @WrCombs said in folder sharing issue:

    @DustinB3403 said in folder sharing issue:

    @WrCombs said in folder sharing issue:

    @WrCombs said in folder sharing issue:

    I can now path to 192.168.128.100\c$

    but when i path to 192.168.128.100
    I get the same error i was before.

    192.168.128.100 is not a SMB or CIFS path. . . so of course it would error. You don't share out an IP address, but resources hosted at that address, IE C$.

    I mapped the Bootdrv of the server on the terminals.
    😃 I did it I fixed it.
    it was a registry setting.
    Im not fucking with it anymore.
    its working.

    Cool cool, so now just charge that customer for 24 hours of horsing around and wash your hands of this job until it blows up again. . .

    you done?

    Is your boss? They're the person who's making you do things the difficult and costly way.



  • giphy (6).gif



  • @WrCombs said in folder sharing issue:

    Have since tried to uninstall the nic and make registry changes (there were a lot that were out of wack apparently) but with no luck still.

    edit Upon this and changing registry keys I was able to get it to communicate and work properly.

    @scottalanmiller seemed confused in the ML wrap up video SO I thought I'd elaborate on what resolved my issue.... well Kind of. ... All I know is one of these fixed it - .

    • HKLM\system\current control set\services\CSC\ start = 0

    • HKLM\System\Current Control Set\Services\NetBT\Parameters\UseNewSMB set to 0

    • Uninstalling reinstalling NIC



  • @WrCombs said in folder sharing issue:

    @scottalanmiller seemed confused in the ML wrap up video SO I thought I'd elaborate on what resolved my issue.... well Kind of. ... All I know is one of these fixed it - .

    HKLM\system\current control set\services\CSC\ start = 0

    HKLM\System\Current Control Set\Services\NetBT\Parameters\UseNewSMB set to 0

    Uninstalling reinstalling NIC

    So you didn't attempt each of these individually, but instead made all of the changes at once and refused to test with a reboot between the changes?

    Also doesn't this mean after spending over a day horsing around with this over VNC that you or a coworker made a site visit?

    Also also does this mean the client paid for over a days worth of remote troubleshooting and a site-visit on top of it all?



  • @DustinB3403 said in folder sharing issue:

    @WrCombs said in folder sharing issue:

    @scottalanmiller seemed confused in the ML wrap up video SO I thought I'd elaborate on what resolved my issue.... well Kind of. ... All I know is one of these fixed it - .

    HKLM\system\current control set\services\CSC\ start = 0

    HKLM\System\Current Control Set\Services\NetBT\Parameters\UseNewSMB set to 0

    Uninstalling reinstalling NIC

    So you didn't attempt each of these individually, but instead made all of the changes at once and refused to test with a reboot between the changes?

    Also doesn't this mean after spending over a day horsing around with this over VNC that you or a coworker made a site visit?

    Also also does this mean the client paid for over a days worth of remote troubleshooting and a site-visit on top of it all?

    Seriously.
    More ridicule from Mr Dustin.. FFS

    1. I made the changes as I was given them .
    2. NO we didnt go on site, rather I finally got an answer that was (good enough for my Boss.
    3. He paid for the time it took me to fix the issue/do research on this issue (only paid for 4 hours per my boss. - Virus removal, and then the fix of the issue.)


  • @WrCombs said in folder sharing issue:

    More ridicule from Mr Dustin.. FFS

    I'm not ridiculing, I'm asking an honest question. With break fix issues like this it's much better to make 1 change at a time, test and proceed.

    Because, one change, may break something else and it's easier to know what was changed and what broke when that change was made.

    1. I told you to reset the NIC around post 8 or 9 on this topic, what does the NIC status show now?
    2. Cool, how did you reset the NIC without being on site, did the client provide a remote set of hands?
    3. So the client did pay, which is fine, I'd argue the Virus removal bit but wasn't involved on that. You know where the rest of the community stands with the quarantine, rescan approach you were forced to take.


  • @DustinB3403 said in folder sharing issue:

    @WrCombs said in folder sharing issue:

    More ridicule from Mr Dustin.. FFS

    I'm not ridiculing, I'm asking an honest question. With break fix issues like this it's much better to make 1 change at a time, test and proceed.

    Because, one change, may break something else and it's easier to know what was changed and what broke when that change was made.

    1. I told you to reset the NIC around post 8 or 9 on this topic, what does the NIC status show now?
    2. Cool, how did you reset the NIC without being on site, did the client provide a remote set of hands?
    3. So the client did pay, which is fine, I'd argue the Virus removal bit but wasn't involved on that. You know where the rest of the community stands with the quarantine, rescan approach you were forced to take.

    1 & 2. Device manager > network adapters> uninstall > reboot > automatically picked it back up upon reboot then changed the settings for the NIC.

    1. Although the virus removal wasn't part of the initial problem - it still needed to be done and since they don't hold a contract with us then It was all "Billable"


  • @WrCombs said in folder sharing issue:

    1 & 2. Device manager > network adapters> uninstall > reboot > automatically picked it back up upon reboot then changed the settings for the NIC.

    Nice, that's what I was hoping it would do, but I've dealt with NICs not coming back up after this process. Always made it easier to just be there and watch it.



  • @DustinB3403 said in folder sharing issue:

    @WrCombs said in folder sharing issue:

    1 & 2. Device manager > network adapters> uninstall > reboot > automatically picked it back up upon reboot then changed the settings for the NIC.

    Nice, that's what I was hoping it would do, but I've dealt with NICs not coming back up after this process. Always made it easier to just be there and watch it.

    I've heard of that issue - it was a calculated risk I was willing to take to get it working.. ya know?