[SOLVED] NetworkManager and DNS

Hello,
Is there any way to set and make permanent DNS adress with NetworkManager? I'd like to use OpenDNS so I edited /etc/resolv.conf and it works till next system restart. What am I supposed to do to make DNS adress permanent?:/
EDIT: Something gone wrong.
EDIT: Solved, it's new NetworkManager 0.7.
Last edited by MilosC (2009-03-08 02:10:32)

My all time favorite way to do this is to put your isp (or OpenDNS addresses, etc) into your router via it's own configuration page.  I've never had to mess around with resolv.conf, dhclient etc this way for over 5 years and let the box pick it up from your router.
After making the change in the router, restart networking, or reboot.

Similar Messages

  • [SOLVED] NetworkManager and UMTS/3G

    I have a problem with NetworkManager and its Applet (the GNOME one)
    In Ubuntu 10.04 it works fine with NM and in Archlinux it works flawless with wvdial but not with NetworkManager
    It just tells me that i dont have any UMTS/3G devices (which is just nonsense)
    Is that a bug in NetworkManager or am i doing something wrong?
    //Edit: Oh damm i just forget the optional dependency "modemmanager"... solved
    Last edited by Vamp898 (2010-06-14 00:43:24)

    Your edit got me one step further, now I see that device also in networkmanager here finally. Thank you!
    If someone tries to click onto "configure" for "mobile broadband" and its greyed out: Click "configure" for wired, leave that window open and just click "configure" in the main networkmanager window again. Then the network connections box from gnome 2 comes up and allows to configure 3G entries. (not a gnome bug, but a feature;)

  • [SOLVED] Networkmanager and special ascii characters kde issue

    cannot connect to ssid with french characters like 'é' and other chars in networkmanager kde
    it work fine in gnome but in kde the networkmanager dont recognize non english letters
    have any one a way to use Hex value instead of ascii in ssid
    Last edited by jambi (2014-07-14 00:03:43)

    You need to configure the profile manually in
    /etc//etc/NetworkManager/system-connections/
    then create a file named
    (null) 1
    [connection]
    id=(null) 1
    type=802-11-wireless
    [802-11-wireless]
    ssid="SSID IN HEX"
    mode=infrastructure
    mac-address=xx:xx:xx:xx:xx
    security=802-11-wireless-security
    [802-11-wireless-security]
    key-mgmt='wireless security'
    auth-alg=open
    psk=password
    you can convert from ascii to hex using terminal
    echo 'ssid' | xxd -u -p
    connectioneditor in kde need more handling functions to be added . i hope in next release they build a robust connectioneditor
    Last edited by kortez (2014-07-07 21:15:45)

  • [SOLVED] networkmanager.service and accounts-daemon.service take slow

    Hello everyone!
    I have noticed that my laptop booting is slow, then I read the wiki and google around but there seems no answer for me.
    It seems that this all because of the NetworkManager, so I post it here.
    This is my basic information:
    $ uname -a [3:03:07]
    Linux hp 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux
    And
    $ systemd-analyze [3:04:25]
    Startup finished in 3.363s (firmware) + 1.382s (loader) + 2.824s (kernel) + 24.506s (userspace) = 32.077s
    And
    $ systemd-analyze blame [3:04:12]
    13.456s NetworkManager.service
    11.414s accounts-daemon.service
    3.289s libvirtd.service
    2.205s gdm.service
    1.094s polkit.service
    1.048s systemd-vconsole-setup.service
    981ms wpa_supplicant.service
    958ms alsa-restore.service
    852ms boot.mount
    636ms systemd-remount-fs.service
    634ms sys-kernel-debug.mount
    609ms dev-hugepages.mount
    569ms sys-kernel-config.mount
    520ms dev-mqueue.mount
    508ms systemd-tmpfiles-setup-dev.service
    506ms tmp.mount
    476ms systemd-udev-trigger.service
    420ms systemd-journal-flush.service
    358ms kmod-static-nodes.service
    268ms systemd-timesyncd.service
    260ms colord.service
    240ms systemd-backlight@backlight:intel_backlight.service
    236ms systemd-update-utmp.service
    And
    $ systemd-analyze critical-chain [3:07:05]
    graphical.target @24.506s
    └─multi-user.target @24.506s
    └─libvirtd.service @21.216s +3.289s
    └─network.target @21.142s
    └─NetworkManager.service @7.685s +13.456s
    └─basic.target @7.684s
    └─timers.target @7.683s
    └─systemd-tmpfiles-clean.timer @7.683s
    └─sysinit.target @7.652s
    └─swap.target @7.652s
    └─dev-disk-by\x2duuid-7006949a\x2d4625\x2d4d7e\x2db101\x2dbe714c525296.swap @7.458s +191ms
    └─dev-disk-by\x2duuid-7006949a\x2d4625\x2d4d7e\x2db101\x2dbe714c525296.device @7.457s
    And
    $ journalctl _SYSTEMD_UNIT=accounts-daemon.service
    8月 24 02:49:20 hp accounts-daemon[264]: started daemon version 0.6.37
    And
    $ journalctl _SYSTEMD_UNIT=NetworkManager.service [3:04:39]
    8月 24 02:49:12 hp NetworkManager[258]: <info> NetworkManager (version 0.9.10.1) is starting...
    8月 24 02:49:12 hp NetworkManager[258]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
    8月 24 02:49:12 hp NetworkManager[258]: <info> WEXT support is enabled
    8月 24 02:49:12 hp NetworkManager[258]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
    8月 24 02:49:20 hp NetworkManager[258]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the Netw
    8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_5D05CE
    8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_5D05CE 1
    8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_1244B0 1
    8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_1244B0
    8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/9
    8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/UCWiFi-77777
    8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/130
    8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/yangmafu
    8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/Hotspot
    8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_281E42
    8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/NewStar
    8月 24 02:49:21 hp NetworkManager[258]: <info> monitoring kernel firmware directory '/usr/lib/firmware'.
    8月 24 02:49:21 hp NetworkManager[258]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:07:00
    8月 24 02:49:21 hp NetworkManager[258]: <info> WiFi hardware radio set enabled
    8月 24 02:49:21 hp NetworkManager[258]: <info> WWAN hardware radio set enabled
    8月 24 02:49:21 hp NetworkManager[258]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-adsl.so
    8月 24 02:49:21 hp NetworkManager[258]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wifi.so
    8月 24 02:49:21 hp NetworkManager[258]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wwan.so
    8月 24 02:49:21 hp NetworkManager[258]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so
    8月 24 02:49:21 hp NetworkManager[258]: <info> WiFi enabled by radio killswitch; enabled by state file
    8月 24 02:49:21 hp NetworkManager[258]: <info> WWAN enabled by radio killswitch; enabled by state file
    8月 24 02:49:21 hp NetworkManager[258]: <info> WiMAX enabled by radio killswitch; enabled by state file
    8月 24 02:49:21 hp NetworkManager[258]: <info> Networking is enabled by state file
    8月 24 02:49:21 hp NetworkManager[258]: <info> (lo): link connected
    8月 24 02:49:21 hp NetworkManager[258]: <info> (lo): carrier is ON
    8月 24 02:49:21 hp NetworkManager[258]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
    8月 24 02:49:21 hp NetworkManager[258]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
    8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): carrier is OFF
    8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): new Ethernet device (driver: 'r8169' ifindex: 2)
    8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): exported as /org/freedesktop/NetworkManager/Devices/1
    8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): preparing device
    8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): created default wired connection 'Wired connection 1'
    8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): using nl80211 for WiFi device control
    8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): driver supports Access Point (AP) mode
    8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): new 802.11 WiFi device (driver: 'rt2800pci' ifindex: 3)
    8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): exported as /org/freedesktop/NetworkManager/Devices/2
    8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): preparing device
    8月 24 02:49:23 hp NetworkManager[258]: <info> wpa_supplicant started
    8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1) supports 4 scan SSIDs
    8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: starting -> ready
    8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): device state change: unavailable -> disconnected (reason 'supplicant-available')
    8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: ready -> disconnected
    8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1) supports 4 scan SSIDs
    8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: disconnected -> inactive
    8月 24 02:49:25 hp NetworkManager[258]: <info> Auto-activating connection 'NewStar'.
    8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) scheduled...
    8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) started...
    8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    8月 24 02:49:25 hp NetworkManager[258]: <info> NetworkManager state is now CONNECTING
    8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) scheduled...
    8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) complete.
    8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) starting...
    8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): device state change: prepare -> config (reason 'none') [40 50 0]
    8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1/wireless): connection 'NewStar' has security, and secrets exist. No ne
    8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): exported as /org/freedesktop/NetworkManager/Devices/1
    8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): preparing device
    8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): created default wired connection 'Wired connection 1'
    8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): using nl80211 for WiFi device control
    8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): driver supports Access Point (AP) mode
    8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): new 802.11 WiFi device (driver: 'rt2800pci' ifindex: 3)
    8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): exported as /org/freedesktop/NetworkManager/Devices/2
    8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): preparing device
    8月 24 02:49:23 hp NetworkManager[258]: <info> wpa_supplicant started
    8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1) supports 4 scan SSIDs
    8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: starting -> ready
    8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): device state change: unavailable -> disconnected (reason 'supplicant-available')
    8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: ready -> disconnected
    8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1) supports 4 scan SSIDs
    8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: disconnected -> inactive
    8月 24 02:49:25 hp NetworkManager[258]: <info> Auto-activating connection 'NewStar'.
    8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) starting connection 'NewStar'
    8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) scheduled...
    8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) started...
    8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    8月 24 02:49:25 hp NetworkManager[258]: <info> NetworkManager state is now CONNECTING
    8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) scheduled...
    8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) complete.
    8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) starting...
    8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): device state change: prepare -> config (reason 'none') [40 50 0]
    8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1/wireless): connection 'NewStar' has security, and secrets exist. No ne
    8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'ssid' value 'NewStar'
    8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'scan_ssid' value '1'
    8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'auth_alg' value 'OPEN'
    8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'psk' value '<omitted>'
    8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) complete.
    8月 24 02:49:25 hp NetworkManager[258]: <info> Config: set interface ap_scan to 1
    8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: inactive -> authenticating
    8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: authenticating -> associating
    8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: associating -> associated
    8月 24 02:49:26 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: associated -> 4-way handshake
    8月 24 02:49:26 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: 4-way handshake -> completed
    8月 24 02:49:26 hp NetworkManager[258]: <info> Activation (wlo1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wir
    8月 24 02:49:26 hp NetworkManager[258]: <info> Activation (wlo1) Stage 3 of 5 (IP Configure Start) scheduled.
    8月 24 02:49:26 hp NetworkManager[258]: <info> Activation (wlo1) Stage 3 of 5 (IP Configure Start) started...
    8月 24 02:49:26 hp NetworkManager[258]: <info> (wlo1): device state change: config -> ip-config (reason 'none') [50 70 0]
    8月 24 02:49:26 hp NetworkManager[258]: <info> Activation (wlo1) Beginning DHCPv4 transaction (timeout in 45 seconds)
    8月 24 02:49:27 hp NetworkManager[258]: <info> dhcpcd started with pid 346
    8月 24 02:49:27 hp NetworkManager[258]: <info> Activation (wlo1) Stage 3 of 5 (IP Configure Start) complete.
    8月 24 02:49:27 hp dhcpcd[346]: version 6.4.3 starting
    8月 24 02:49:27 hp NetworkManager[258]: <info> (wlo1): DHCPv4 state changed nbi -> preinit
    8月 24 02:49:27 hp dhcpcd[346]: DUID 00:01:00:01:1b:84:72:e9:b8:76:3f:39:7c:5b
    8月 24 02:49:27 hp dhcpcd[346]: wlo1: IAID 3f:39:7c:5b
    8月 24 02:49:27 hp dhcpcd[346]: wlo1: soliciting an IPv6 router
    8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: version 6.4.3 starting
    8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: DUID 00:01:00:01:1b:84:72:e9:b8:76:3f:39:7c:5b
    8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: wlo1: IAID 3f:39:7c:5b
    8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: wlo1: soliciting an IPv6 router
    8月 24 02:49:28 hp dhcpcd[346]: wlo1: rebinding lease of 192.168.1.100
    8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: wlo1: rebinding lease of 192.168.1.100
    8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): carrier is OFF
    8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): new Bridge device (driver: 'bridge' ifindex: 4)
    8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): exported as /org/freedesktop/NetworkManager/Devices/3
    8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): preparing device
    8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
    8月 24 02:49:32 hp dhcpcd[346]: wlo1: leased 192.168.1.100 for 7200 seconds
    8月 24 02:49:32 hp dhcpcd[346]: wlo1: adding route to 192.168.1.0/24
    8月 24 02:49:32 hp NetworkManager[258]: dhcpcd[346]: wlo1: leased 192.168.1.100 for 7200 seconds
    8月 24 02:49:32 hp NetworkManager[258]: dhcpcd[346]: wlo1: adding route to 192.168.1.0/24
    8月 24 02:49:33 hp NetworkManager[258]: <info> (wlo1): DHCPv4 state changed preinit -> reboot
    8月 24 02:49:33 hp NetworkManager[258]: <info> address 192.168.1.100
    8月 24 02:49:33 hp NetworkManager[258]: <info> plen 24 (255.255.255.0)
    8月 24 02:49:33 hp NetworkManager[258]: <info> gateway 192.168.1.1
    8月 24 02:49:33 hp NetworkManager[258]: <info> server identifier 192.168.1.1
    8月 24 02:49:33 hp NetworkManager[258]: <info> lease time 7200
    8月 24 02:49:33 hp NetworkManager[258]: <info> nameserver '192.168.1.1'
    8月 24 02:49:33 hp NetworkManager[258]: nm_ip4_config_add_nameserver: assertion 'new != 0' failed
    8月 24 02:49:33 hp NetworkManager[258]: <info> nameserver '0.0.0.0'
    8月 24 02:49:33 hp NetworkManager[258]: <info> Activation (wlo1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    8月 24 02:49:33 hp NetworkManager[258]: <info> Activation (wlo1) Stage 5 of 5 (IPv4 Commit) started...
    8月 24 02:49:33 hp NetworkManager[258]: <info> (wlo1): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    8月 24 02:49:33 hp NetworkManager[258]: <info> Activation (wlo1) Stage 5 of 5 (IPv4 Commit) complete.
    8月 24 02:49:33 hp NetworkManager[258]: <info> (wlo1): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    8月 24 02:49:33 hp NetworkManager[258]: <info> (wlo1): device state change: secondaries -> activated (reason 'none') [90 100 0]
    8月 24 02:49:33 hp NetworkManager[258]: <info> NetworkManager state is now CONNECTED_LOCAL
    8月 24 02:49:34 hp NetworkManager[258]: <info> NetworkManager state is now CONNECTED_GLOBAL
    8月 24 02:49:34 hp NetworkManager[258]: <info> Policy set 'NewStar' (wlo1) as default for IPv4 routing and DNS.
    8月 24 02:49:34 hp NetworkManager[258]: <info> Writing DNS information to /usr/bin/resolvconf
    8月 24 02:49:35 hp NetworkManager[258]: <info> Activation (wlo1) successful, device activated.
    8月 24 02:49:35 hp NetworkManager[258]: <info> startup complete
    8月 24 02:49:40 hp dhcpcd[346]: wlo1: no IPv6 Routers available
    8月 24 02:49:40 hp NetworkManager[258]: dhcpcd[346]: wlo1: no IPv6 Routers available
    Last edited by callofdutyops (2014-08-26 14:48:22)

    ooo wrote:
    callofdutyops wrote:But I wonder whether there's some improvement?
    Do you mean why there's an improvement after removing the journal files?
    first of all, I hope that you know what systemd journal is, and what files you just deleted.
    systemd journal stores all system logs in database files in /var/log/journal/
    every time you boot up your system, journald will log the entire boot process and stores in its database (and continue logging of course).
    over time the journal will get huge (unless you limit its size) and fragmented, which could slow down reading and writing from the it greatly.
    so, if writing the log during the boot process slows down greatly, it will certainly have an detrimental effect on overall boot speed.
    I hope that makes sense
    I think I saw this mentioned on some systemd TODO list, so developers should aware of this and possibly trying to figure out some workaround.
    In the meantime limiting journal size is probably a good idea.
    If you happened to be using btrfs, disabling COW for files in /var/log/journal and 'autodefrag' mount option may also help some.
    also defragmenting the files in /var/log/journal if your file system supports it
    First of all, thanks to your very clear explanation!
    English is not my mother tongue, so I think I express me in a wrong way.Sorry for this!
    What I exactly want to mean is that is it possible to make booting more faster?

  • [SOLVED] NetworkManager dumped core

    Symptoms: WiFi randomly drops out.
    More specifically: NetworkManager core dumps and network-manager-applet stops (Gnome 3.8)
    If anyone has suggestions, I'd be grateful. I'm at a loss, other than disabling NetworkManager and enabling netctl. Details follow below.
    Thanks so much!
    uname -r
    3.9.0-2-ARCH
    uname -m
    x86_64
    lspci -v
    Network controller: Intel Corporation Centrino Advanced-N 6205
    rfkill list
    0: tpacpi_bluetooth_sw: Bluetooth
    Soft blocked: no
    Hard blocked: no
    1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
    2: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
    iwconfig
    enp0s25 no wireless extensions.
    wlp3s0 IEEE 802.11abgn ESSID:"The Way 5GHz"
    Mode:Managed Frequency:5.18 GHz Access Point: 00:26:F2:F2:E7:D5
    Bit Rate=65 Mb/s Tx-Power=15 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=54/70 Signal level=-56 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:230 Invalid misc:113 Missed beacon:0
    lo no wireless extensions.
    journalctl -u NetworkManager --since=today
    -- Reboot --
    May 04 14:04:19 arch systemd[1]: Starting Network Manager...
    May 04 14:04:20 arch NetworkManager[284]: <info> NetworkManager (version 0.9.8.0) is starting...
    May 04 14:04:20 arch NetworkManager[284]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
    May 04 14:04:20 arch NetworkManager[284]: <info> WEXT support is enabled
    May 04 14:04:21 arch NetworkManager[284]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager ma
    May 04 14:04:21 arch NetworkManager[284]: keyfile: parsing Auto The Way 5GHz ...
    May 04 14:04:21 arch NetworkManager[284]: keyfile: read connection 'Auto The Way 5GHz'
    May 04 14:04:21 arch NetworkManager[284]: <info> monitoring kernel firmware directory '/lib/firmware'.
    May 04 14:04:21 arch NetworkManager[284]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/
    May 04 14:04:21 arch NetworkManager[284]: <info> WiFi hardware radio set enabled
    May 04 14:04:21 arch systemd[1]: Started Network Manager.
    May 04 14:04:21 arch NetworkManager[284]: <info> WiFi enabled by radio killswitch; enabled by state file
    May 04 14:04:21 arch NetworkManager[284]: <info> WWAN enabled by radio killswitch; enabled by state file
    May 04 14:04:21 arch NetworkManager[284]: <info> WiMAX enabled by radio killswitch; enabled by state file
    May 04 14:04:21 arch NetworkManager[284]: <info> Networking is enabled by state file
    May 04 14:04:21 arch NetworkManager[284]: <warn> failed to allocate link cache: (-10) Operation not supported
    May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): carrier is OFF
    May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): new Ethernet device (driver: 'e1000e' ifindex: 3)
    May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): exported as /org/freedesktop/NetworkManager/Devices/0
    May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): bringing up device.
    May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): preparing device.
    May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): deactivating device (reason 'managed') [2]
    May 04 14:04:21 arch NetworkManager[284]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:19.0/net/enp0
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): using nl80211 for WiFi device control
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): driver supports Access Point (AP) mode
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 2)
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): exported as /org/freedesktop/NetworkManager/Devices/1
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): bringing up device.
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): preparing device.
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): deactivating device (reason 'managed') [2]
    May 04 14:04:21 arch NetworkManager[284]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
    May 04 14:04:21 arch NetworkManager[284]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
    May 04 14:04:21 arch NetworkManager[284]: <warn> error poking ModemManager: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop
    May 04 14:04:21 arch NetworkManager[284]: <info> wpa_supplicant started
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0) supports 5 scan SSIDs
    May 04 14:04:21 arch NetworkManager[284]: <warn> Trying to remove a non-existant call id.
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: starting -> ready
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: ready -> disconnected
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0) supports 5 scan SSIDs
    May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: disconnected -> inactive
    May 04 14:04:25 arch NetworkManager[284]: <info> Auto-activating connection 'Auto The Way 5GHz'.
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) starting connection 'Auto The Way 5GHz'
    May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled...
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started...
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled...
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete.
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting...
    May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0/wireless): connection 'Auto The Way 5GHz' has security, and secrets exist. No new
    May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'ssid' value 'The Way 5GHz'
    May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'scan_ssid' value '1'
    May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'auth_alg' value 'OPEN'
    May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'psk' value '<omitted>'
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete.
    May 04 14:04:25 arch NetworkManager[284]: <info> Config: set interface ap_scan to 1
    May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: inactive -> scanning
    May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: scanning -> authenticating
    May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: authenticating -> associating
    May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: associating -> associated
    May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: associated -> completed
    May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless netwo
    May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) scheduled.
    May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) started...
    May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0]
    May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    May 04 14:04:28 arch NetworkManager[284]: <info> dhcpcd started with pid 447
    May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Beginning IP6 addrconf.
    May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) complete.
    May 04 14:04:28 arch dhcpcd[447]: version 5.6.8 starting
    May 04 14:04:28 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
    May 04 14:04:28 arch dhcpcd[447]: [color=#FF0000]wlp3s0: sendmsg: Cannot assign requested address[/color]
    May 04 14:04:28 arch dhcpcd[447]: wlp3s0: rebinding lease of 192.168.10.59
    May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): DHCPv4 state changed nbi -> preinit
    May 04 14:04:28 arch dhcpcd[447]: wlp3s0: acknowledged 192.168.10.59 from 192.168.10.1
    May 04 14:04:28 arch dhcpcd[447]: wlp3s0: checking for 192.168.10.59
    May 04 14:04:32 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
    May 04 14:04:33 arch dhcpcd[447]: wlp3s0: leased 192.168.10.59 for 86400 seconds
    May 04 14:04:33 arch NetworkManager[284]: <info> (wlp3s0): DHCPv4 state changed preinit -> bound
    May 04 14:04:33 arch NetworkManager[284]: <info> address 192.168.10.59
    May 04 14:04:33 arch NetworkManager[284]: <info> prefix 24 (255.255.255.0)
    May 04 14:04:33 arch NetworkManager[284]: <info> gateway 192.168.10.1
    May 04 14:04:33 arch NetworkManager[284]: <info> nameserver '192.168.10.1'
    May 04 14:04:33 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    May 04 14:04:33 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) started...
    May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
    May 04 14:04:34 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) complete.
    May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    May 04 14:04:34 arch NetworkManager[284]: <info> Policy set 'Auto The Way 5GHz' (wlp3s0) as default for IPv4 routing and DNS.
    May 04 14:04:34 arch NetworkManager[284]: <info> Writing DNS information to /usr/sbin/resolvconf
    May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): roamed from BSSID 90:27:E4:5E:98:24 (The Way 5GHz) to 00:26:F2:F2:E7:D5 (The Way 5GHz)
    May 04 14:04:34 arch NetworkManager[284]: <info> Activation (wlp3s0) successful, device activated.
    May 04 14:04:36 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
    May 04 14:04:40 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
    May 04 14:04:40 arch dhcpcd[447]: wlp3s0: no IPv6 Routers available
    May 04 21:04:49 arch NetworkManager[284]: <info> (wlp3s0): IP6 addrconf timed out or failed.
    May 04 21:04:49 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    May 04 21:04:49 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    May 04 21:04:50 arch systemd[1]: NetworkManager.service: main process exited, code=dumped, status=6/ABRT
    May 04 21:04:50 arch systemd[1]: MESSAGE=Unit NetworkManager.service entered failed state.
    May 04 21:04:50 arch systemd-coredump[1036]: [color=#FF0000]Process 284 (NetworkManager) dumped core.[/color]
    journalctl -u wpa_supplicant --since=today
    -- Reboot --
    May 04 14:04:21 arch systemd[1]: Starting WPA supplicant...
    See dmesg at Pastebin
    [edited May 7, 2013]
    I'm marking this topic SOLVED, though more accurately, I should say that I've worked around the problem.
    I achieved a stable wireless connection by changing APs, which leads me to believe that the underlying problem is upstream. Specifically, the problem is most likely that NetworkManager is not compatible with all APs. In my case, when I connect to a Netgear NDR3700v1 running dd-wrt, NetworkManager and nn-applet crashed randomly and frequently. However, after changing to an Apple Airport AP, I achieved a stable connection without crashes.
    Bottomline: if you experience wireless connection troubles with NetworkManager and nm-applet, the problem may be that NetworkManager is not "compatible" with your AP hardware.
    Last edited by hcra (2013-05-07 20:50:36)

    b1tgl0w wrote:Is it normal for crond to run as the root user?
    Completely normal. I'd be asking the question "was I hacked" if I found cron NOT running as root.
    I'd say your computer just crashed.

  • [SOLVED] NetworkManager kills wireless speed

    When I connect my work wifi network using NetworkManager, the speed unstable -- with it being less than 1KB/s more often than not. The connection speed seems to be fine when I disable NetworkManager and use a simple iwconfig essid key command and dhcpcd. My laptop is dual-boot, and the speed is fine in Windows as well.
    NetworkManager seems to be setting my resolv.conf correctly.
    Signal strength is not an issue.
    Wireless chip is Intel 6000 series AGN using iwlagn driver.
    Rather baffling problem to me. Ideas?
    Last edited by Hamsterkill (2012-03-16 21:47:18)

    I don't have access to router configuration at my job, unfortunately.
    I did try manually configuring my IP, DNS and Gateway for the connection, though. When I did that, the connection speed seemed more stable -- never cutting out completely. Tx aggregation didn't get enabled in dmesg. However, wireless speed was still only 1-1.5Mbps in speedtests whereas I get a full 20Mbps when I use the iwconfig+dhcpcd method.
    EDIT: It also seemed to have attached to a much farther access point for the network than normal when I did that way, so I just manually configured the BSSID as well and tried to run a speedtest. I got a nice speed initially, (15Mbps) but it cut the connection quickly and wouldn't even run the upload test. So I looked at dmesg and Tx aggregation was enabled on the connection again.
    Last edited by Hamsterkill (2012-03-16 21:20:46)

  • [SOLVED] NetworkManager not letting me connect to the internet.

    Hello everyone,
    I normally connect to my WiFi using wifi-menu each start-up, but since I'm coming from Ubuntu in this laptop, and want the NetworkManager integration in GNOME, as well as automatically connecting to my preferred network on startup, I decided to install NetworkManager and network-manager-applet, as well as networkmanager-openvpn and networkmanager-pptp for vpn support.
    Unfortunately, enabling the NetworkManager service and starting the NetworkManager service (first disabling the netctl@wlo1\x2dCasa.service and wpa_supplicant.service) disconnects me from WiFi, and connecting to my network asks for the password (WPA2 Personal), after 50 seconds it asks for the password again, and goes on forever, unless one presses "Cancel" and it disconnects.
    I'm new to Arch Linux (not to Linux in general, as I actually used Ubuntu since 2009, and have some command-line experience), so if this seems like an easy task, or a rookie mistake, please bear with me.
    Is any more info required? Log files?
    -Jonathan
    Last edited by Jonathan Precise (2015-04-04 13:36:19)

    Yes, you are indeed right Xabre, I stopped netctl@wlo1\x2dCasa.service, but not wpa_supplicant.service, and enabled that last one. Now NetworkManager runs perfect!
    EDIT: I'm imagining that's how you mark this thread as solved? Or is there another method?
    -Jonathan
    Last edited by Jonathan Precise (2015-04-04 13:37:19)

  • ITouch loses router and DNS addresses?

    I have had my iTouch for about a week and it connected to my wireless network for the first three days flawlessly. Since that time, it will only connect sporadically and I have noticed that when it doesn't connect, it is because the router and DNS addresses have disappeared in the wireless window in Settings. I can get them back occasionally by renewing lease in this window, but more often than not, renewing lease does not reestablish these addresses.
    I reset the iTouch through itunes, but this did not solve the problem.
    Additional information. The iTouch has the full signal (maximum number of bars). I am using an airport extreme as my base station. I have three macs that I connect to the wireless network through the base station. I have a few airport expresses that are connected to audio equipment or video game units. All of these continue to work well and have no problem connecting to the wireless network.
    Your help/thoughts would be most appreciated.
    Message was edited by: tritium11

    Is your router broadcasting its SSID? If not, try enabling that because the Touch often has a hard time remembering a network if it is hidden. Hiding your SSID is very minimal security, so there's really no point to hiding it.

  • Changing host and DNS on OAS9i please help ASAP

    I am working on a win2000 Advanced server with Oracle 8i enterprise edition and OAS9i.
    I have a running webserver that I want to change its name and DNS to become a subdomain (i.e it was http://www.xxxxxx.net to become http://zzzz.yyyyyy.com).
    I have changed the computer's name and DNS, and I have made changes to all files *.ora *.cfg and *.conf related to the server naming(ex. httpd.conf, formsweb.cfg, listener.ora, tnsnames.ora,etc) in both homes(ora81 and ora806).
    The apache, forms & reports servers plus windows services are all running after the change, but I am not able to enter my web application. I get an exception after entering the username and password.
    The exception is a FRM92100:
    Java Exception
    sun.applet.AppletSecurityException:checkconnect.networkhost2 and many lines that follow.but I think this is the location of the main exception.
    Does anyone have an idea how to solve this problem?
    Thank You.Please reply to me ASAP.

    Dear Mr.Parekh,
    I looked at the notes, but unfortunately I am using OAS 9i release 1 (1.0.2.2).
    I didn't try to implement what the notes said since there may be an incompatibility problem with versions.
    Looking again for your help.
    Thank You.
    Michel

  • [SOLVED] NetworkManager can't use DHCP

    I just installed a fresh Arch Linux on whatever network modem is onboard the Gigabyte 990FXA-UD3 motherboard. The ethernet port works out-of-the-box using dhcpcd on the installer ISO and on my actual installation of Arch. Using KDE, I followed NetworkManager's setup guide in the wiki, but if I try to connect to anything, it instantly fails once I click on it. Then I tried clicking on Manage Connections and making a new Wired connection. It still failed. Then I tried changing that connection from DHCP to manual IPv4 and DNS numbers, and it worked just fine. I've done a lot of Googling, but nothing in the wiki or forums is fixing this issue for me.
    Last edited by Cadeyrn (2013-06-25 22:24:32)

    I'm confused, did someone prevent you from updating the Wiki?
    Yes, I tried, but I admittedly lack the skills to debate technically, with someone who obviously possesses the skills.
    https://wiki.archlinux.org/index.php?title=NetworkManager&action=history
    (cur | prev) 07:09, 3 September 2013 Lahwaacz (Talk | contribs) . . (28,477 bytes) (-253) . . (Undo revision 274198 by Jeff story (talk) completely covered by the note above removed text)
    (cur | prev) 23:18, 2 September 2013 Jeff story (Talk | contribs) . . (28,730 bytes) (+253) . . (clarify and instruct to disable and stop dhcpcd.service)
    Honestly though, at this point, your question is no longer important.
    What would be cool though is for someone with the expertise on this subject to take notice, figure out exactly what is lacking in the wiki and be willing to contribute the info for the good of the community, which I believe should include the Arch newbs or non coders / programmers.
    Then be able to persuade Scimmia and Lahwaacz that in fact, something needs "fixed", even though from their perspective (Linux guru?) there is nothing wrong or missing.
    EDIT: Added second name to clarify situation.
    Last edited by jeff story (2013-12-30 03:53:51)

  • Having Problems With GNOME3, NetworkManager, and nm-applet

    So interesting problem.  nm-applet does not connect to wireless networks, both secure and insecure(tried both).  When I click on a network to connect to, it does not display the "connecting" icon or anything, it simply does nothing.  To debug, I killed NetworkManager and then started it with:
    sudo NetworkManager --no-daemon
    This is some of the output I received:
    NetworkManager[3333]: <info> (eth1): device state change: activated -> disconnected (reason 'user-requested') [100 30 39]
    NetworkManager[3333]: <info> (eth1): deactivating device (reason: 39).
    dhcpcd[3338]: received SIGTERM, stopping
    dhcpcd[3338]: eth1: removing interface
    NetworkManager[3333]: <info> (eth1): canceled DHCP transaction, DHCP client pid 3338
    NetworkManager[3333]: <warn> (pid 3338) unhandled DHCP event for interface eth1
    NetworkManager[3333]: <info> Activation (ra0) starting connection 'Auto scrapheap'
    NetworkManager[3333]: <info> (ra0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    NetworkManager[3333]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled...
    NetworkManager[3333]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) started...
    NetworkManager[3333]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) scheduled...
    NetworkManager[3333]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) complete.
    NetworkManager[3333]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) starting...
    NetworkManager[3333]: <info> (ra0): device state change: prepare -> config (reason 'none') [40 50 0]
    NetworkManager[3333]: <info> Activation (ra0/wireless): access point 'Auto scrapheap' has security, but secrets are required.
    NetworkManager[3333]: <info> (ra0): device state change: config -> need-auth (reason 'none') [50 60 0]
    NetworkManager[3333]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) complete.
    NetworkManager[3333]: <warn> No agents were available for this request.
    NetworkManager[3333]: <info> (ra0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
    NetworkManager[3333]: <warn> Activation (ra0) failed for access point (scrapheap)
    NetworkManager[3333]: <info> Marking connection 'Auto scrapheap' invalid.
    NetworkManager[3333]: <warn> Activation (ra0) failed.
    NetworkManager[3333]: <info> (ra0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    NetworkManager[3333]: <info> (ra0): deactivating device (reason: 0).
    NetworkManager[3333]: <info> Activation (ra0) starting connection 'Auto AFK - Fucking Bitches'
    NetworkManager[3333]: <info> (ra0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    NetworkManager[3333]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled...
    NetworkManager[3333]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) started...
    NetworkManager[3333]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) scheduled...
    NetworkManager[3333]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) complete.
    NetworkManager[3333]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) starting...
    NetworkManager[3333]: <info> (ra0): device state change: prepare -> config (reason 'none') [40 50 0]
    NetworkManager[3333]: <info> Activation (ra0/wireless): access point 'Auto AFK - Fucking Bitches' has security, but secrets are required.
    NetworkManager[3333]: <info> (ra0): device state change: config -> need-auth (reason 'none') [50 60 0]
    NetworkManager[3333]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) complete.
    NetworkManager[3333]: <warn> No agents were available for this request.
    NetworkManager[3333]: <info> (ra0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
    NetworkManager[3333]: <warn> Activation (ra0) failed for access point (AFK - Fucking Bitches)
    NetworkManager[3333]: <info> Marking connection 'Auto AFK - Fucking Bitches' invalid.
    NetworkManager[3333]: <warn> Activation (ra0) failed.
    NetworkManager[3333]: <info> (ra0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    NetworkManager[3333]: <info> (ra0): deactivating device (reason: 0).
    This is the output right after I disconnected from my ethernet connection, which I should mention works fine through nm-applet.  Just a little background knowledge, this is a fresh install of gnome3, and I followed the ArchLinux wiki article on NetworkManager.  I should also mention, that I have never been prompted for a password, and I have tried manually entering the password using nm-connection-editor, to no avail.

    First of all, thanks for your response.  In no particular order:
    Here is my rc.conf-
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
    # startup and during the boot process. If set to 'no', the C locale is used.
    # HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
    #   in the hardware clock being left untouched (useful for virtualization)
    #   Note: Using "localtime" is discouraged.
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    # VERBOSE: Verbose level (from 1 to 8). man 3 syslog for level info
    LOCALE="en_US.UTF-8"
    DAEMON_LOCALE="no"
    HARDWARECLOCK="UTC"
    TIMEZONE="America/Chicago"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    VERBOSE="3"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    MOD_AUTOLOAD="yes"
    MODULES=(!rt2870sta !rt2800pci !rt2x00pci !rt2800lib !rt2800usb !rt2x00usb !rt2x00lib rt3572sta)
    # Udev settle timeout (default to 30)
    UDEV_TIMEOUT=30
    # Scan for FakeRAID (dmraid) Volumes at startup
    USEDMRAID="no"
    # Scan for BTRFS volumes at startup
    USEBTRFS="no"
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="SOLID"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    #   - prefix an entry in INTERFACES with a ! to disable it
    #   - no hyphens in your interface names - Bash doesn't like it
    # DHCP:     Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    #Static IP example
    #eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
    INTERFACES=(!eth0 !ra0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    #   - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    # Setting this to "yes" will skip network shutdown.
    # This is required if your root device is on NFS.
    NETWORK_PERSIST="no"
    # Enable these network profiles at boot-up.  These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    #   - set to 'menu' to present a menu during boot-up (dialog package required)
    #   - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    #   - prefix a daemon with a ! to disable it
    #   - prefix a daemon with a @ to start it up in the background
    # If something other takes care of your hardware clock (ntpd, dual-boot...)
    # you should disable 'hwclock' here.
    DAEMONS=(hwclock syslog-ng netfs crond dbus networkmanager gdm)
    This is what happens when I attempt to connect to a wireless network in my daemon.log:
    May 24 19:41:57 localhost NetworkManager[2650]: <info> (ra0): supplicant interface state: inactive -> disconnected
    May 24 19:42:43 localhost NetworkManager[2650]: <info> (ra0): supplicant interface state: disconnected -> inactive
    May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0) starting connection 'Auto AFK - Fucking Bitches'
    May 24 19:52:39 localhost NetworkManager[2650]: <info> (ra0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled...
    May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) started...
    May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) scheduled...
    May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) complete.
    May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) starting...
    May 24 19:52:39 localhost NetworkManager[2650]: <info> (ra0): device state change: prepare -> config (reason 'none') [40 50 0]
    May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0/wireless): access point 'Auto AFK - Fucking Bitches' has security, but secrets are required.
    May 24 19:52:39 localhost NetworkManager[2650]: <info> (ra0): device state change: config -> need-auth (reason 'none') [50 60 0]
    May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) complete.
    May 24 19:52:39 localhost NetworkManager[2650]: <warn> No agents were available for this request.
    May 24 19:52:39 localhost NetworkManager[2650]: <info> (ra0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
    May 24 19:52:39 localhost NetworkManager[2650]: <warn> Activation (ra0) failed for access point (AFK - Fucking Bitches)
    May 24 19:52:39 localhost NetworkManager[2650]: <info> Marking connection 'Auto AFK - Fucking Bitches' invalid.
    May 24 19:52:39 localhost NetworkManager[2650]: <warn> Activation (ra0) failed.
    May 24 19:52:39 localhost NetworkManager[2650]: <info> (ra0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    May 24 19:52:39 localhost NetworkManager[2650]: <info> (ra0): deactivating device (reason: 0).
    May 24 19:52:39 localhost NetworkManager[2650]: <info> (ra0): reset MAC address to 00:00:00:00:00:00
    May 24 19:52:40 localhost NetworkManager[2650]: <info> Policy set 'Wired connection 2' (eth1) as default for IPv4 routing and DNS.
    And this is what gets printed in my kernel.log when I attempt to connect to a wireless network:
    May 24 19:57:14 localhost kernel: [76209.155402] ===>rt_ioctl_giwscan. 6(6) BSS returned, data->length = 998
    May 24 19:57:14 localhost kernel: [76209.157419] ===>rt_ioctl_giwscan. 6(6) BSS returned, data->length = 998
    May 24 19:57:22 localhost kernel: [76216.809056] ra0: no IPv6 routers present
    May 24 19:57:36 localhost kernel: [76231.105479] (Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
    May 24 19:57:36 localhost kernel: [76231.105482] (Reassign Efuse for 3x7x/3x9x/53xx) Size=0x3c [3c0-3fb]
    May 24 19:57:36 localhost kernel: [76231.364008] RTMP_TimerListAdd: add timer obj fa284038!
    May 24 19:57:36 localhost kernel: [76231.364011] RTMP_TimerListAdd: add timer obj fa284080!
    May 24 19:57:36 localhost kernel: [76231.364012] RTMP_TimerListAdd: add timer obj fa2840c8!
    And it doesn't work in fallback mode.  It does pretty much the same thing.
    Last edited by jayd3e (2011-05-25 01:17:29)

  • I am trying to setup Microsoft office mail and need assistance  - I am receiving the error, unable to find server and DNS setting in the Network

    I am trying to setup Microsoft office mail and need assistance  - I am receiving the error, unable to find server and DNS setting in the Network

    Which version of OSX and what email provider are you using.

  • Unable to access gateway and DNS via VPN (L2TP) with Snow Leopard Server

    Summary:
    After rebooting my VPN server, i am able to establish a VPN (L2TP) connection from outside my private network. I am able to connect (ping, SSH, …) the gateway only until the first client disconnects. Then i can perfectly access all the other computers of the private network, but i cannot access the private IP address of the gateway.
    Additionally, during my first VPN connection, my DNS server, which is on the same server, is not working properly with VPN. I can access it with the public IP address of my gateway. I can access it from inside my private network. A port scan indicates me that the port 53 is open, but a dig returns me a timeout.
    Configuration:
    Cluster of 19 Xserve3.1 - Snow Leopard Server 10.6.2
    Private network 192.168.1.0/255.255.255.0 -> domain name: cluster
    -> 1 controller, which act as a gateway for the cluster private network, with the following services activated:
    DHCP, DNS, firewall (allowing all incoming traffic for each groups for test purposes), NAT, VPN, OpenDirectory, web, software update, AFP, NFS and Xgrid controller.
    en0: fixed public IP address -> controller.example.com
    en1: 192.168.1.254 -> controller.cluster
    -> 18 agents with AFP and Xgrid agent activated:
    en1: 192.168.1.x -> nodex.cluster with x between 1 and 18
    VPN (L2TP) server distributes IP addresses between 192.168.1.201 and 192.168.1.210 (-> vpn1.cluster to vpn10.cluster). Client informations contain the private network DNS server informations (192.168.1.254, search domain: cluster).
    _*Detailed problem description:*_
    After rebooting the Xserve, my VPN server works fine except for the DNS. My client receives the correct informations:
    Configure IPv4: Using PPP
    IPv4 address: 192.168.1.201
    Subnet Mask:
    Router: 192.168.1.254
    DNS: 192.168.1.254
    Search domain: cluster
    From my VPN client, i can ping all the Xserve of my cluster (192.168.1.1 to 18 and 192.168.1.254). If i have a look in Server Admin > Settings > Network, i have three interfaces listed: en0, en1 and ppp0 of family IPv4 with address 192.168.1.254 and DNS name controller.cluster.
    The DNS server returns me timeouts when i try to do a dig from my VPN client even if i am able to access it directly from a computer inside or outside my private network.
    After i disconnect, i can see in Server Admin that the IP address of my ppp0 interface has switch to my public IP address.
    Then i can always establish a VPN (L2TP) connection, but the client receives the following informations:
    Configure IPv4: Using PPP
    IPv4 address: 192.168.1.202
    Subnet Mask:
    Router: (Public IP address of my VPN server)
    DNS: 192.168.1.254
    Search domain: cluster
    From my VPN client, i can access all the other computers of my network (192.168.1.1 to 192.168.1.18) but when i ping my gateway (192.168.1.254), it returns me timeouts.
    I have two "lazy" solutions to this problem: 1) Configure VPN and DNS servers on two differents Xserve, 2) Put the public IP address of my gateway as DNS server address, but none of these solutions are acceptable for me…
    Any help is welcome!!!

    I would suggest taking a look at:
    server admin:vpn:settings:client information:network route definitions.
    as I understand your setup it should be something like
    192.168.1.0 255.255.255.0 private.
    at least as a start. I just got done troubleshooting a similar issue but via two subnets:
    http://discussions.apple.com/thread.jspa?threadID=2292827&tstart=0

  • Deleted failed DC from the domain (Server 2012 R2) - Now after doing metadata and DNS cleanup, I can no longer promote a new DC to the domain

    I work for a university and teach IT courses to undergrad and graduate students. The details below are pertaining an isolated lab environment
    I had a storage failure in my lab and the DCs became corrupt. This is a university lab environment so there isn't anything crucial on here. I just would rather avoid rebuilding the domain/forest and would rather use this as a learning experience with my
    students...
    So after the storage failed and was restored, the VMs hosted became corrupt. I did a NTDSUTIL to basically repair the NDTS.dit file but one of my DCs reverted to a state before DC promotion. Naturally, the domain still had this object in AD. After numerous
    failed attempts at trying to reinstall the DC on the server through the server manager wizard in 2012 R2, I decided that a metadata cleanup of the old failed object was necessary.
    Utilizing this article, I removed all references of the failed DC from both AD and DNS (http://www.petri.com/delete_failed_dcs_from_ad.htm) 
    So now that the failed object is removed completely from the domain and the metadata cleanup was successful, I then proceeded to re-install the necessary AD DS role on the server and re-promote to the existing domain. Pre-Requisites pass but generate some
    warning around DNS Delgation, and Dynamic Updates (delegation is ignored because the lab is isolated from external comms, and dynamic updates are in fact enabled on both my _msdcs and root domain zones).
    Upon the promotion process, I get the following error message (also worth mentioning - the account performing these operations is a member of DA, EA, and Schema Admins)
    The operation failed because:
    Active Directory Domain Services could not create the NTDS Settings object for this Active Directory Domain Controller CN=NTDS Settings,CN=domainVMDC1,CN=Servers,CN=Default-
    First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=school,DC=edu on the remote AD DC domainVMDC2. Ensure the provided network credentials have sufficient permissions.
    "While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync."
    As you can see, this error seems odd considering. Now that I'm down to a single DC and DNS server, the sync should be corrected. I've run a repadmin /syncall and it completed successfully. Since then, I've run dcdiags and dumped those to a text as well and
    here are my results...
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       Home Server = domainVMDC2
       * Identified AD Forest. 
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\domainVMDC2
          Starting test: Connectivity
             ......................... domainVMDC2 passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\domainVMDC2
          Starting test: Advertising
             ......................... domainVMDC2 passed test Advertising
          Starting test: FrsEvent
             ......................... domainVMDC2 passed test FrsEvent
          Starting test: DFSREvent
             ......................... domainVMDC2 passed test DFSREvent
          Starting test: SysVolCheck
             ......................... domainVMDC2 passed test SysVolCheck
          Starting test: KccEvent
             ......................... domainVMDC2 passed test KccEvent
          Starting test: KnowsOfRoleHolders
             ......................... domainVMDC2 passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... domainVMDC2 passed test MachineAccount
          Starting test: NCSecDesc
             ......................... domainVMDC2 passed test NCSecDesc
          Starting test: NetLogons
             ......................... domainVMDC2 passed test NetLogons
          Starting test: ObjectsReplicated
             ......................... domainVMDC2 passed test ObjectsReplicated
          Starting test: Replications
             ......................... domainVMDC2 passed test Replications
          Starting test: RidManager
             ......................... domainVMDC2 passed test RidManager
          Starting test: Services
             ......................... domainVMDC2 passed test Services
          Starting test: SystemLog
             A warning event occurred.  EventID: 0x00001795
                Time Generated: 12/18/2014   00:35:03
                Event String:
                The program lsass.exe, with the assigned process ID 476, could not authenticate locally by using the target name ldap/domainvmdc2.domain.school.edu. The target name used is not valid. A target name should
    refer to one of the local computer names, for example, the DNS host name.
             ......................... domainVMDC2 passed test SystemLog
          Starting test: VerifyReferences
             ......................... domainVMDC2 passed test VerifyReferences
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
                For the partition
                (DC=ForestDnsZones,DC=domain,DC=school,DC=edu) we encountered
                the following error retrieving the cross-ref's
                (CN=3098109a-ff99-41d4-8926-0e814ac8efde,CN=Partitions,CN=Configuration,DC=domain,DC=school,DC=edu)
                 information: 
                   LDAP Error 0x52e (1326). 
             ......................... ForestDnsZones failed test CheckSDRefDom
          Starting test: CrossRefValidation
                For the partition
                (DC=ForestDnsZones,DC=domain,DC=school,DC=edu) we encountered
                the following error retrieving the cross-ref's
                (CN=3098109a-ff99-41d4-8926-0e814ac8efde,CN=Partitions,CN=Configuration,DC=domain,DC=school,DC=edu)
                 information: 
                   LDAP Error 0x52e (1326). 
             ......................... ForestDnsZones failed test
             CrossRefValidation
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
                For the partition
                (DC=DomainDnsZones,DC=domain,DC=school,DC=edu) we encountered
                the following error retrieving the cross-ref's
                (CN=2f0b8ac0-2630-441a-891f-b5fcb91498a8,CN=Partitions,CN=Configuration,DC=domain,DC=school,DC=edu)
                 information: 
                   LDAP Error 0x52e (1326). 
             ......................... DomainDnsZones failed test CheckSDRefDom
          Starting test: CrossRefValidation
                For the partition
                (DC=DomainDnsZones,DC=domain,DC=school,DC=edu) we encountered
                the following error retrieving the cross-ref's
                (CN=2f0b8ac0-2630-441a-891f-b5fcb91498a8,CN=Partitions,CN=Configuration,DC=domain,DC=school,DC=edu)
                 information: 
                   LDAP Error 0x52e (1326). 
             ......................... DomainDnsZones failed test
             CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
                For the partition
                (CN=Schema,CN=Configuration,DC=domain,DC=school,DC=edu) we
                encountered the following error retrieving the cross-ref's
                (CN=Enterprise Schema,CN=Partitions,CN=Configuration,DC=domain,DC=school,DC=edu)
                 information: 
                   LDAP Error 0x52e (1326). 
             ......................... Schema failed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
                For the partition
                (CN=Configuration,DC=domain,DC=school,DC=edu) we encountered
                the following error retrieving the cross-ref's
                (CN=Enterprise Configuration,CN=Partitions,CN=Configuration,DC=domain,DC=school,DC=edu)
                 information: 
                   LDAP Error 0x52e (1326). 
             ......................... Configuration failed test CrossRefValidation
       Running partition tests on : domain
          Starting test: CheckSDRefDom
             ......................... domain passed test CheckSDRefDom
          Starting test: CrossRefValidation
                For the partition (DC=domain,DC=school,DC=edu) we encountered
                the following error retrieving the cross-ref's
                (CN=domain,CN=Partitions,CN=Configuration,DC=domain,DC=school,DC=edu)
                 information: 
                   LDAP Error 0x52e (1326). 
             ......................... domain failed test CrossRefValidation
       Running enterprise tests on : domain.school.edu
          Starting test: LocatorCheck
             ......................... domain.school.edu passed test
             LocatorCheck
          Starting test: Intersite
             ......................... domain.school.edu passed test Intersite
    From what I can gather, there is a definite DNS issue but I don't have any stale records to the old DC stored anywhere. I've tried this with a new server as well and get similar errors... 
    At this rate I'm ready to rebuild the entire forest over again. I'm just reluctant to do so as I want to make this a learning experience for the students. 
    Any help would be greatly appreciated. Thanks!

    As you can see, there seems to be some errors. The one that I did correct was the one around the _msdcs NS record being unable to resolve. For whatever, reason the name wasn't resolving the IP but all other NS tabs and records were. Just that one _msdcs
    sub-zone. Furthermore, the mentioning of any connections to root hint servers can be viewed as false positives. There is no external comms to this lab so no communication with outside IPs can be expected. Lastly, they mentioned a connectivity issue yet mention
    that I should check the firewall settings. All three profiles are disabled in Windows Firewall (as they have been the entire time). Thank you in advance for your help!
    C:\Windows\system32>dcdiag /test:dns /v
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       * Verifying that the local machine domainVMDC2, is a Directory Server.
       Home Server = domainVMDC2
       * Connecting to directory service on server domainVMDC2.
       * Identified AD Forest.
       Collecting AD specific global data
       * Collecting site info.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=domain,DC=school,DC=edu,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
       The previous call succeeded
       Iterating through the sites
       Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=school,DC=edu
       Getting ISTG and options for the site
       * Identifying all servers.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=domain,DC=school,DC=edu,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
       The previous call succeeded....
       The previous call succeeded
       Iterating through the list of servers
       Getting information for the server CN=NTDS Settings,CN=domainVMDC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=school,DC=edu
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       * Identifying all NC cross-refs.
       * Found 1 DC(s). Testing 1 of them.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\domainVMDC2
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             The host
             3a38b19c-4bb3-4542-acb6-9e5e97cc15c4._msdcs.domain.school.edu
             could not be resolved to an IP address. Check the DNS server, DHCP,
             server name, etc.
             Got error while checking LDAP and RPC connectivity. Please check your
             firewall settings.
             ......................... domainVMDC2 failed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\domainVMDC2
          Test omitted by user request: Advertising
          Test omitted by user request: CheckSecurityError
          Test omitted by user request: CutoffServers
          Test omitted by user request: FrsEvent
          Test omitted by user request: DFSREvent
          Test omitted by user request: SysVolCheck
          Test omitted by user request: KccEvent
          Test omitted by user request: KnowsOfRoleHolders
          Test omitted by user request: MachineAccount
          Test omitted by user request: NCSecDesc
          Test omitted by user request: NetLogons
          Test omitted by user request: ObjectsReplicated
          Test omitted by user request: OutboundSecureChannels
          Test omitted by user request: Replications
          Test omitted by user request: RidManager
          Test omitted by user request: Services
          Test omitted by user request: SystemLog
          Test omitted by user request: Topology
          Test omitted by user request: VerifyEnterpriseReferences
          Test omitted by user request: VerifyReferences
          Test omitted by user request: VerifyReplicas
          Starting test: DNS
             DNS Tests are running and not hung. Please wait a few minutes...
             See DNS test in enterprise tests section for results
             ......................... domainVMDC2 passed test DNS
       Running partition tests on : ForestDnsZones
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : DomainDnsZones
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : Schema
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : Configuration
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : domain
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running enterprise tests on : domain.school.edu
          Starting test: DNS
             Test results for domain controllers:
                DC: domainVMDC2
                Domain: domain.school.edu
                   TEST: Authentication (Auth)
                      Authentication test: Successfully completed
                   TEST: Basic (Basc)
                      Error: No LDAP connectivity
                      The OS
                      Microsoft Windows Server 2012 R2 Datacenter (Service Pack level: 0.0)
                      is supported.
                      NETLOGON service is running
                      kdc service is running
                      DNSCACHE service is running
                      DNS service is running
                      DC is a DNS server
                      Network adapters information:
                      Adapter [00000010] vmxnet3 Ethernet Adapter:
                         MAC address is 00:50:56:A2:2C:24
                         IP Address is static
                         IP address: *.*.100.26
                         DNS servers:
                            *.*.100.26 (domainVMDC2) [Valid]
                      No host records (A or AAAA) were found for this DC
                      The SOA record for the Active Directory zone was found
                      The Active Directory zone on this DC/DNS server was found primary
                      Root zone on this DC/DNS server was not found
                   TEST: Forwarders/Root hints (Forw)
                      Recursion is enabled
                      Forwarders are not configured on this DNS server
                      Root hint Information:
                         Name: a.root-servers.net. IP: 198.41.0.4 [Invalid (unreachable)]
                         Name: b.root-servers.net. IP: 192.228.79.201 [Invalid (unreachable)]
                         Name: c.root-servers.net. IP: 192.33.4.12 [Invalid (unreachable)]
                         Name: d.root-servers.net. IP: 199.7.91.13 [Invalid (unreachable)]
                         Name: e.root-servers.net. IP: 192.203.230.10 [Invalid (unreachable)]
                         Name: f.root-servers.net. IP: 192.5.5.241 [Invalid (unreachable)]
                         Name: g.root-servers.net. IP: 192.112.36.4 [Invalid (unreachable)]
                         Name: h.root-servers.net. IP: 128.63.2.53 [Invalid (unreachable)]
                         Name: i.root-servers.net. IP: 192.36.148.17 [Invalid (unreachable)]
                         Name: j.root-servers.net. IP: 192.58.128.30 [Invalid (unreachable)]
                         Name: k.root-servers.net. IP: 193.0.14.129 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 199.7.83.42 [Invalid (unreachable)]
                         Name: m.root-servers.net. IP: 202.12.27.33 [Invalid (unreachable)]
                      Error: Both root hints and forwarders are not configured or
                      broken. Please make sure at least one of them works.
                   TEST: Delegations (Del)
                      Delegation information for the zone: domain.school.edu.
                         Delegated domain name: _msdcs.domain.school.edu.
                            Error: DNS server: domainvmdc2. IP:<Unavailable>
                            [Missing glue A record]
                            [Error details: 9714 (Type: Win32 - Description: DNS name does not exist.)]
                   TEST: Dynamic update (Dyn)
                      Test record dcdiag-test-record added successfully in zone domain.school.edu
                      Warning: Failed to delete the test record dcdiag-test-record in zone domain.school.edu
                      [Error details: 13 (Type: Win32 - Description: The data is invalid.)]
                   TEST: Records registration (RReg)
                      Network Adapter [00000010] vmxnet3 Ethernet Adapter:
                         Matching CNAME record found at DNS server *.*.100.26:
                         3a38b19c-4bb3-4542-acb6-9e5e97cc15c4._msdcs.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _ldap._tcp.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _ldap._tcp.a9241004-88ea-422d-a71e-df7b622f0d68.domains._msdcs.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _kerberos._tcp.dc._msdcs.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _ldap._tcp.dc._msdcs.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _kerberos._tcp.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _kerberos._udp.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _kpasswd._tcp.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _ldap._tcp.Default-First-Site-Name._sites.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _kerberos._tcp.Default-First-Site-Name._sites.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _ldap._tcp.gc._msdcs.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _gc._tcp.Default-First-Site-Name._sites.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.domain.school.edu
                         Matching  SRV record found at DNS server *.*.100.26:
                         _ldap._tcp.pdc._msdcs.domain.school.edu
                   Error: Record registrations cannot be found for all the network
                   adapters
             Summary of test results for DNS servers used by the above domain
             controllers:
                DNS server: 128.63.2.53 (h.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.63.2.53               
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 192.112.36.4 (g.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.112.36.4               
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 192.203.230.10 (e.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.203.230.10               
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 192.228.79.201 (b.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.228.79.201               
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 192.33.4.12 (c.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.33.4.12               
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 192.36.148.17 (i.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.36.148.17               
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 192.5.5.241 (f.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.5.5.241               
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 192.58.128.30 (j.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.58.128.30               
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 193.0.14.129 (k.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 193.0.14.129               
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 198.41.0.4 (a.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.41.0.4               
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 199.7.83.42 (l.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 199.7.83.42               
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 199.7.91.13 (d.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 199.7.91.13               
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 202.12.27.33 (m.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 202.12.27.33               
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: *.*.100.26 (domainVMDC2)
                   All tests passed on this DNS server
                   Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
             Summary of DNS test results:
                                                Auth Basc Forw Del  Dyn  RReg Ext
                Domain: domain.school.edu
                   domainVMDC2                 PASS FAIL FAIL FAIL WARN FAIL n/a
             ......................... domain.school.edu failed test DNS
          Test omitted by user request: LocatorCheck
          Test omitted by user request: Intersite

  • I want to install Photoshop but everytime I get an ERROR CODE: A12E1.How do I solve that and what is it?

    Hello,
    I want to install Photoshop but everytime I get an ERROR CODE: A12E1.How do I solve that and what is it?

    A12E1 error installing Creative Cloud products | CC
    Mylenium

Maybe you are looking for

  • HotSpot Indicator Banner - feature request

    I rely on my Verzon iPhone 4 tethering / personal hotspot quite a bit. The problem is the blue indicator stripe at the top of the screen. It's very nice to know that it's on, but it moves application data down by the height of the indicator strip - w

  • Hi how can i fetch the data from tree table

    Hi i am designing a UI in which i am creating a java tree table as on sun java site http://java.sun.com/products/jfc/tsc/articles/treetable2/index.html now i have to fetch the perticular column value on the mouse click.I have implemented mouse listen

  • Most efficient way to make an ordered list?

    Hi all, I have a simulation where I have agents running around in an environment. These agents need to get the closest agent near them, and they have to do this a whole bunch of times each cycle -- closest predator to them, closest prey, closest mate

  • To create a customer in SD module

    hi can anybody telll me how to create a customer in SD module. regards.

  • VERY weird OVM networking problem

    First, this may have nothing to do with OVM, but the problem I'm seeing is happening on all FIVE of my VM servers. I can't even guess what's going on. Maybe you have seen this and solved it, or maybe you can suggest what I can do to debug this. Here