Solved Started as Win 7 Issue.. Now Job Searching?
-
@notverypunny said in Started as Win 7 Issue.. Now Job Searching?:
So... did the original issue actually ever get resolved?
No, we never found the slightest place to start on it. We have extremely little information and the company in question has been working on this for a long time and never was able to find an answer and blocks the only real troubleshooting step that we have to work with. If we had access to the machine, we might be able to make headway, but even that is a stretch. Digging into logs, using wireshark, who knows. But with th ehigh level information provided, and a history that suggests that isn't an easily fixed (or maybe possible to fix) issue, we've got really nothing to work with.
-
Going to lock and split while there is some time.
-
@scottalanmiller said in Started as Win 7 Issue.. Now Job Searching?:
@Dashrender said in Started as Win 7 Issue.. Now Job Searching?:
Frankly - this seems like a good time to create a new SKU - an upgrade SKU, i.e. we don't upgrade you to new OSes as part of the typical paid monthly maintenance. You can purchase a time by time upgrade to the OS when desired.
Define upgrade vs patching. It can be done, kind of, but I'd like to see you try to put it in writing.
Answer to this sub topic is here...
https://mangolassi.it/topic/20306/can-windows-7-still-upgrade-to-windows-10
-
@scottalanmiller said in Started as Win 7 Issue.. Now Job Searching?:
@notverypunny said in Started as Win 7 Issue.. Now Job Searching?:
So... did the original issue actually ever get resolved?
No, we never found the slightest place to start on it. We have extremely little information and the company in question has been working on this for a long time and never was able to find an answer and blocks the only real troubleshooting step that we have to work with. If we had access to the machine, we might be able to make headway, but even that is a stretch. Digging into logs, using wireshark, who knows. But with th ehigh level information provided, and a history that suggests that isn't an easily fixed (or maybe possible to fix) issue, we've got really nothing to work with.
Alright, so let's set aside the disagreements about how the company runs their show and the clusterfuck around Win10 upgrades and at least give the man some things to check... And FFS if we can find him a job where his talents are put to better use....
IIRC there are multiple terminals connecting to this "server" and there's only 1 terminal that can't connect to the smb share.
Given this scenario:
- is the share pw protected or otherwise protected with authentication?
- is the underlying ntfs ACL'd?
- hoping that the answer to both of the above is yes, is the client properly configured with UN / PW?
- is the FW on the server configured to only allow access from specific IPs / ranges?
- I can't find the docs right now, but wasn't there an issue somewhat recently where users in the admin group are blocked access to file shares?
- try accessing the shares by IP
- can the admin shares be reached by name or IP
- hell, can the server be pinged from the client
Like @scottalanmiller said, there's not a whole hell of a lot to go on, but the above should start to point towards Windows file sharing vs networking vs general M$ dickery
-
@notverypunny said in Started as Win 7 Issue.. Now Job Searching?:
IIRC there are multiple terminals connecting to this "server" and there's only 1 terminal that can't connect to the smb share.
I think it was one, then they found a second. And there some historically. So if I read it all correctly, it's two currently, and multiple in the past and it's a known, unfixable issue (unfixable meaning after dealing with it for a long time, they gave up.)
-
@WrCombs said in Started as Win 7 Issue.. Now Job Searching?:
Next was print and file sharing - where When I turn it on, save back out and go back it reverts back to being off.
Reboot and try again - No luck same issue .This seems to be the most root of the issues. Why is it turning itself back off? That can't be firewall or protocol related. Something is messing with the setting.
-
OK, deja vu all over again?
Didn't we have another long-ass thread about the same (or similar) issue and it was something about the server-side app being called 2x and messing with the terminals' access to the server-side resources?
-
@scottalanmiller said in Started as Win 7 Issue.. Now Job Searching?:
What's driving this behaviour?
People believing the the 2016 push was the one and only time to get it without cost.
-
@notverypunny said in Started as Win 7 Issue.. Now Job Searching?:
Didn't we have another long-ass thread about the same (or similar) issue and it was something about the server-side app being called 2x and messing with the terminals' access to the server-side resources?
Not sure, sounds a little familiar, but not much.
-
-
@notverypunny said in Started as Win 7 Issue.. Now Job Searching?:
Since that was the same OP, I'm guessing that that is not the issue with this one.
-
@scottalanmiller said in Started as Win 7 Issue.. Now Job Searching?:
@notverypunny said in Started as Win 7 Issue.. Now Job Searching?:
Since that was the same OP, I'm guessing that that is not the issue with this one.
I would hope so, but we're all human and the issue seems very similar. I think he had another one where it was something about 2 instances of the server app like I mentioned in an earlier post but I couldn't find that one.
Makes me glad that I'm not doing 1st level support anymore
And even then, our 1st level guys have more discretion than this, both our internal IT team and the (currently) small team for external support.
