Linux Domain Controller
-
Gah!
Not sure what I did yesterday but now I cant contact any mirrors or ping anything!
Come on Linux be my friend!
-
@Sparkum said:
Gah!
Not sure what I did yesterday but now I cant contact any mirrors or ping anything!
Come on Linux be my friend!
nslookup or dig is going to be your friend here. Check your DNS settings. Something is not resolving.
-
Is there any chance this isnt on me?
When I first booted initially I got this as well.
And I dont beleve I've changed networks settings to date?
Just changed DNS (temporarily) to google's DNS and same results.
Also keep loosing connection to the console this morning.
-
Yep was definitely on their end, I wasnt able to get into the console for about 20 minutes. Was about to submit a ticket and there was a related article, which seemed exactly like my problem. Waiting a little more and everything works now (as origional settings)
-
I've never been able to full saturate gigabit links with OpenVPN. But I have with IPSEC and Tinc and that was using Core 2 duo era cpu's. Cisco stuff in $3k range couldn't do it.
-
@thecreativeone91 said:
Cisco stuff in $3k range couldn't do it.
That's like the lowest bar in the industry.
-
So how should I have my DNS settings,
If I leave them as CloudatCost default I cant ping anything, if I change them to what they would be once I get them added to the domain, nothing, if I change them to google's DNS I can see the outside world.
I assume this is not a good idea though? Or is there no real downside?
Would I have it set as google's DNS until I can get OpenVPN up and going?
-
@Sparkum said:
So how should I have my DNS settings,
If I leave them as CloudatCost default I cant ping anything, if I change them to what they would be once I get them added to the domain, nothing, if I change them to google's DNS I can see the outside world.
I assume this is not a good idea though? Or is there no real downside?
Would I have it set as google's DNS until I can get OpenVPN up and going?
I would use the DHCP set ones until you get the VPN setup. Then you will want DNS lookups on the Domain over the VPN. Not sure why C@C's DNS isn't working for you. I haven't had issues with it.
-
@thecreativeone91
I didnt at first, and then all of a sudden nothing worked. (Hadnt touched any network settings yet until that point)
-
Wondering if anyone had any advice on this as well (for OpenVPN)
I thought I had the setup go so smooth last night, worked through a few errors but cant seem to get around this one.
thanks
-
You have a hostname conflict. What is the hostname of the system officially uname -n and what are the entries in /etc/hosts?
-
-
Well you are missing the host entry for your server as a starting point. Let's at least get that fixed. The entry should be...
[ip address] dc.pricehouse.ca dc -
If anything this experience has taught me I know nothing about Linux haha.
Havent looked into this one yet (going to start right now) but my kid is ""Maybe"" asleep so incase I get taken away wanted it up here
-
Strange when I went to sit back down I ended up getting a different error message..
-
Went through the how to again and found 2 mistakes that I rectified.
New error message
-- Unit openvpn@server.service has begun starting up.
Apr 07 14:57:00 dc.pricehouse.ca openvpn[10639]: Options error: Unrecognized option or missing parameter(s) in server.conf:85: dh2048.pem (2.3.6)
Apr 07 14:57:00 dc.pricehouse.ca openvpn[10639]: Use --help for more information.
Apr 07 14:57:00 dc.pricehouse.ca systemd[1]: openvpn@server.service: control process exited, code=exited status=1
Apr 07 14:57:00 dc.pricehouse.ca systemd[1]: Failed to start OpenVPN Robust And Highly Flexible Tunneling Application On server.
-- Subject: Unit openvpn@server.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel-- Unit openvpn@server.service has failed.
-- The result is failed.
Apr 07 14:57:00 dc.pricehouse.ca systemd[1]: Unit openvpn@server.service entered failed state.
Apr 07 14:57:06 dc.pricehouse.ca smbd[10645]: [2015/04/07 14:57:06.576726, 0] ../source3/printing/print_cups.c:151(cups_connect)
Apr 07 14:57:06 dc.pricehouse.ca smbd[10645]: Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected
Apr 07 14:57:06 dc.pricehouse.ca smbd[1416]: [2015/04/07 14:57:06.580788, 0] ../source3/printing/print_cups.c:528(cups_async_callback)
Apr 07 14:57:06 dc.pricehouse.ca smbd[1416]: failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL -
Apr 07 14:57:00 dc.pricehouse.ca openvpn[10639]: Options error: Unrecognized option or missing parameter(s) in server.conf:85: dh2048.pem (2.3.6)
You have an error with in the server.conf file on line 85.
Edit: Tried to put this in a code block but it won't let me odd...
-
If I'm counting right line 85 is
dh2048.pem
-
When in vi just use this command to jump to line 85...
:85 -
Alright yep it was that was suppose to be
dh dh2048.pem
So I believe I'm getting closer.
Apr 07 16:16:22 dc.pricehouse.ca systemd[1]: Unit openvpn@server.service entered failed state.
Apr 07 16:16:26 dc.pricehouse.ca unix_chkpwd[11489]: password check failed for user (root)
Apr 07 16:16:26 dc.pricehouse.ca sshd[11480]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.255.190.158 user=root
Apr 07 16:16:26 dc.pricehouse.ca sshd[11480]: pam_succeed_if(sshd:auth): requirement "uid >= 1000" not met by user "root"
