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.
Yeaaahhhh. This is definitely still falling under the NSFW Category. :D
Not porn per se. But definitely not something to have playing at work. ^^
For cool features: xWiki
For conveniance in setting up: if you got a synology, use the synology notes app.
Jesus, i saw that picture and thought
well murica and their anti pedestrian street designs
Then read your comment.
Checked the picture.
Zoomed in. there is text.
in disbelief
thats actually a german crossing.
Got angry and dumbfounded at the same time.
What piece of shit is this crossing?!
Towards whatever Communityplanners on meth that did this: Fix this shit!
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!
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!