Found in here on the linked pages down in the list. https://wiki.dbzer0.com/piracy/megathread/
https://shakil-shahadat.github.io/awesome-piracy/#usenet
Didnt take that much time to search. Maybe the megathread itself also has some additional pages about the usenet.
Well not so much the adress of the AD server.
It should be the domain name of your domain that you have created.
As in Joh.Doe@CompanyWork.internal
The part behind the @ is the domain the user is registered to and even though the AD server might be named prod-ad-001 the text should be the domain you are trying to auth towards and the share you are accessing to should obvioisly have a connection the the AD to forward the credentials and ask if Auth is positive.
In FSTAB:
//192.168.188.52/media /home/shareuser/shared/ cifs vers=3.0,credentials=/home/shareuser/.smbcred,uid=1000,gid=1000,iocharset=utf8 0 0
In .smbcred are the credentials. The content of the file:
username=shareuser
password=shicjwvfiak domain=192.168.188.52
Should work.
Instead of the IP put the FQDN of your Share holding Server and make sure DNS is properly working.
I would guess, a monitoring system like CheckMK or Icinga?
You could check what has been alarming even if the check is green again, by the time you look into it.
Nah, probably not. All routers you can buy today will route and by default have their firewall active. Make sure, auto-updates are activated on your router.
Check your server OS'ses and the Software running on them for updates on a regular basis - since they are partially made available to the public and are potential attack vectors.
Though if you only port-forwarded a couple ports that dont include the RDP port or something wildly stupid, you should be safe.
Follow some best practises as:
Don't let yourself fool by the guys telling ya to setup a full fledged firewall system when you obviously don't even know basic networking. You would be overwhelmed by the configurationpossibilities.
If you want to dangle your foot in some cold water - try em out and put some machines behind them to learn what behaves how. But dont make em your only protection against the public internet when you don't know basic networking stuff.
Happy Sailin' matey!
I fear I gotta move to a different instance. I'm also a lefty but gawd damn I will never try to justify the stuff some dudes on this instance do.
I'm not sure but I think the second one looks just a tiny bit different, so it should have worked.
Could you install a basic secondary graphics card and fully forward it to the VM? That should make you capable of using its HDMI Ports - and this way you should also have no HDMI DRM Bullshit errors from apps like Netflix and Disney.
I guess the best way for that, is to crosscheck with the maiantained list on the megathread of this community.
Nice!
Happy, that you found my comment :D
I've also searched for such a solution for a longggg time. When i finally found it though... holy moly i was happy about that
Just for the sake of testing maybe try it with a oneliner:
sudo mount -t cifs -o user=testuser,domain=testdomain //192.168.1.100/share /mntEither way using the logs is the best way to check for discepancies. Also check in on the logs on the fileserver. Though idk what to advice to trace the logon stuff and trace whats making it fail.
Just for the case that you dont know where to look in windows: eventviewer is the place to go. Which predifined filter though - simply google that.
Wishing ya the best of luck mate!