whatsisname's questions

I'm struggling to get an lxc container to startup with proper networking.

/etc/network/interfaces:

auto lxcbr0
iface lxcbr0 inet static
        address 192.168.5.69
        netmask 255.255.255.0
        bridge_ports eno1
        bridge_stp off
        bridge_fd 0
        bridge_waitport 0
        bridge_maxwait 0

container config:

lxc.network.type = veth
lxc.network.name = eth0
lxc.network.link = lxcbr0
lxc.network.hwaddr = 26:0b:6c:e8:dc:65
lxc.network.flags = up

When I boot up the container, networking doesn't work. When I look at the bridge config, the container isn't connected:

# brctl show
bridge name     bridge id               STP enabled     interfaces
lxcbr0          8000.509a4c6f57b4       no              eno1

If I manually add the container's virtual network device to the bridge, then everything is groovy:

#brctl addif lxcbr0 veth0BCEEH

These configs are basically from an existing machine with working configurations, so there must be some sort of simple gotcha that I am missing.

How can I get the container to add the veth to the bridge automatically?

In case it matters:

 lxc version: 2.0.7
 Linux hostname 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux

I have a Server 2008 file server, and and while here an employee encrypted several files, and has now since left to seek greener pastures.

I want to decrypt the files, so others can access them. Can I simply change the account password, then login as the user, and uncheck the encryption? Or will doing so destroy the encryption keys, rendering the files forever lost?

If logging in with a new password isn't going to work, how can I go about decrypting the files? The employees user account was a domain account, and I have domain administrator access.

I am not sure what method of encryption is being utilized, beyond the File Properties > Advanced > Encrypt contents to secure data checkbox, and the filenames are green.

Thanks

I have a Cisco 5505 working as a DHCP server, and a server 2008 DNS server running an AD domain.

I am having problems with all XP computers not updating the forward lookup zone. The reverse lookup zone updates are working. Windows vista and 7 computers update just fine. Additionally the DNS server accepts both secure and non-secure updates.

When people are connected through the Cisco's VPN, they cannot resolve to any machines that have reverse lookup zones, but they can resolve entries in the forward lookup zone.

I have tried ipconfig /registerdns, but the forward lookup zone entries for the XP clients are not being populated.

How can I get the XP Dynamic DNS client to make the updates, or what can I do to debug what's going on?

Thanks

I have a single domain server running Server 2003 running a 2003 functional level domain. I am trying to add a server 2008 R2 machine to be another domain controller, with the intention of promoting it to be the primary, and taking off the server 2003 machine.

I am required to run adprep /forestprep on the Server 2003 machine. When I run it, it fails with the following errors:

Adprep failed to verify whether schema master has completed a replication cycle after last reboot.
[Status/Consequence]
The schema is not upgraded.
[User Action]  
Check the log file ADPrep.log in the C:\WINDOWS\debug\adprep\logs\20101109153331 directory for possible cause of failure.

Adprep encountered an LDAP error. 
Error code: 0x32. Server extended error code: 0x2098, Server error message: 00002098: SecErr: DSID-03151D7D, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

I have confirmed that the user account I am using to run ADPREP, mydomain\administrator, is in the Schema Admins, Enterprise Admins, and Domain admins group.

Attempting to figure out what is with the replication, running repadmin /showrepl

repadmin running command /showrepl against server localhost

Default-First-Site-Name\SERVERNEW
DC Options: IS_GC
Site Options: (none)
DC object GUID: 0657168e-d854-48d8-a40a-dea3e41e6e87
DC invocationID: 0657168e-d854-48d8-a40a-dea3e41e6e87

Anyone know how to fix this error? Would raising the domain and forest to a 2003 functional level have any likelihood of working? While just making a new domain from scratch and typing in all the user names and stuff again isn't a deal breaker because we only have about 15 users, it would still be a big pain.

Thanks