I'm attempting to translate multicast traffic to unicast to send over the Internet.
I enabled ip forwarding and tried using the following rule:
iptables -t nat -A PREROUTING -i eth0 -d 239.0.0.0 -j DNAT --to-destination 192.0.2.1
However, the traffic is never sent out.
Is there someway to do what I'm attempting without setting up a tunnel?
I have a service (an old 4D-based application) which has been happily running on Windows Server 2003. With the pending EOL for 2003, I'm trying to migrate to a new 2012R2 host.
I set up the service using the sc command as type= own, type= interact. When starting the service from services.msc the starting message appears and slowly moves until it announces that starting the service has failed. While the progress bar is running, the service appears to be running normally. One the error appears the service is killed.
Under Server 2003 interact mode was required to run the service as it opens a status/control window on session 0. I know this functionality has changed and is deprecated on Server 2008+ and I believe it is the root of my issue.
Is there anyway to improve interactive services compatibility on Server 2012?
I have an old Intel SC5400 based server with an Intel S5000PSL board with redundant power running CentOS 6. One of the power supplies has failed and I would like to silence the alarm temporarily.
Is there a way to silence the alarm via IPMI or similar?
ipmi-sensors -r 24 kindly tells me the problem, but I don't see anything in the ipmitool suite to silence the alarm.
I have a few Mac clients connected to a Linux server running Netatalk 3.1.1. The server is connected to an AD domain, the clients are currently not. Previously all users were connecting under a single user account and everything worked relatively well. We attempted to introduce the new concept that every user should have their own account, but we're seeing permissions issues.
The root of the share has some sane ACLs and default ACLs applied which grant the appropriate rights, but OS X thinks everything read-only and forbids writes. On the local Linux machine, or through a Windows machine (speaking SMB to Samba), writing to the folders works as expected.
I attempted changing map acls = none thinking it would report no permissions to the client at all, but the issue persists.
I joined a single 10.9 test client to AD and set the LDAP settings in Netatalk. That client can now see the group names that have write permission (AD\foo-w) and running the group command shows that I am a member of that group. However, the 'Get Info' dialog still shows read-only access and Finder forbids writes.
Does anyone know how I can convince the OS X clients that it can write?
I'm attempting to get Windows (XP+) clients to talk to an NT4 server. All machines are joined to an active directory domain. Domain logins work everywhere and authentication works between all machines EXCEPT from clients to the lone NT4 machine.
When attempting to connect (start -> run -> \\nt4machine), the client receives an error "The account is not authorized to log in from this station." When connecting via IP address it does work, but is not desirable.
Local policies have been set on a test client to try to resolve the issue:
I've done packet captures between the machines (via Wireshark) and the client stops after sending acknowledgement of the server's negotiate protocol response. Of note, the server responds with security mode 0x07 (signatures supported, not required) and extended security exchange comes back as not supported in the capabilities section of the response (I do not believe it is required though).
I also need access to the machine via named pipes. Symptoms are similar here (authorization fails via machine name, works via IP).
Looking up the NT4 machine address by netbios and DNS are both working. Also the NT4 machine is able to access shares on the Win7 machine.
Unfortunately replacing the NT4 machine isn't in the cards in the near future due to the function the machine serves (interfaces with proprietary machinery via hardware/software, all of which would have to be replaced). Does anyone know how I can make it more NT4 more appealing to my Win7 clients?
I have a server process sending out mail using one out of a handful of addresses in the From header. Unfortunately, the program does not set the sender header resulting in "{Sender} on behalf of {From}" in Outlook user's inboxes.
Is there a way to make the sender header match the from header for outgoing mail from this user?