DougN's questions

We need a way to insert a device between a target device and the network, ideally without needing to change any IP addresses.

Currently, the situation is (please excuse the ASCII art)

-----------       -------------
| x.x.x.5 | ----- | x.x.x.10  |
-----------       -------------

What we are trying to do is insert a device with two network interfaces, and what we'd LIKE to do is arrange the IPs so each side thinks it's talking to the orignal device. We'll take care of moving the data from one interface to the other.

-----------     --------------------------------    ------------
| x.x.x.5 | --- | eth0 x.x.x.10   x.x.x.5 eth1 |--- | x.x.x.10 |
-----------     --------------------------------    ------------

Is there a way to setup the routing table such that a request for x.x.x.10 that comes in from eth0 gets sent out eth1, and requests for x.x.x.5 that arrive via eth1 get sent out eth0?

The middle box is running Linux.

I've got an ASP.NET website running on IIS 7. Using PA File Sight, I've proven that it is creating 2 to 3 new files in the C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys folder every minute.

PA File Sight shows the user as IIS APPPOOL\DefaultAppPool and the process as w3wp.exe, so I know it's my website and IIS 7.

There are millions of files in that folder now (can't open in Explorer, even directory listing from command prompt takes hours). The disk is about to run out of space and the server will be hosed :(

Does anyone know WHY?

I've gone into the Machine Key setting of IIS and disabled (unchecked) "Automatically generate at runtime" and "generate a unique key for each application" for both validation key and decryption key, but that hasn't helped.

The server is Windows 2008 R2, and has all of the latest patches.

I figure I'm about a week or two from running out of space. Very anxious to hear suggestions!

One last note, the server does support SSL connections, but they are very rare (very little of the site is protected/sensitive).

Getting in a bit over my head here ...

We have a small office with a Windows 2003 AD domain controller. About to open a second small (remote) office, and would like both to share the same domain. They are across the Internet from each other, but an occasional VPN connection could be created.

My first thought is to setup the second office on a separate subnet. I planned to duplicate the PDC to the new office, but somehow demote it to a backup domain controller that would periodically connect to the PDC via VPN (domain changes are quite rare).

Is this just a disaster waiting to happen? Is there a better way to go about it? I've tried googling, but not quite sure what to call this mess I'm creating :)

Thanks for any suggestions.

I'm trying to RDP from a Win7 to a 2008 R2 machine through a tunnel (think SSH, but not exactly).

It fails and the following is in the 2008 R2 (destination) event log:

System Event Log, LsaSrv source, Event ID 6037

"The program lsass.exe, with the assigned process ID 632, could not authenticate locally by using the target name TERMSRV/{WIN7_name}. 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.

Try a different target name. "

The WIN7 side shows:

System Event Log, TermDD event source, Event ID 56

The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. Client IP: {WIN7_name}.

(with an error code of C000018D = STATUS_TRUSTED_RELATIONSHIP_FAILURE)

So apparently the the RDP client is passing the local server name to the remote side (I did tell it to RDP to the Win7 machine, but to a tunneled port).

I haven't been able to find any way to tell the RDP client or server to ignore this problem. It looks like it would be possible to use setspn.exe to set the {Win7_name} service principle name on the 2008 R2 box, but that seems messy, and in my case, my clients won't know how to do that. Plus, you'd have to do it for all clients that might connect to that server.

Is anyone else able to RDP between 2008 R2 and Win 7 using tunneling?

I'm wondering what a maximum (practical) ping response time might be. As far as I know, there isn't a max defined anywhere (TTL, but that's hops, not time). As I think about it, I'm not sure I've ever seen a ping response time of more than a second or so. But as far as I know, there is nothing to stop a remote host from waiting (or being really busy) and not sending the response back for a few seconds.

As a simple data point, I just pinged a number of servers around the world and the worst time I could find was 350ms.

I'm almost embarrassed to ask this, but I'm stuck. I installed VMWare ESXi on a Mac Pro. It's working great! The problem is that you press F12 to eject the disk, and F12 is what you use to shutdown ESX. I can power down, open the case, pull out the CD drive and use a paper clip to force the drawer open, but that's kind of a pain.

Any other way to do this?

EDIT: Setting password was a good idea - no shutdown now :) However, F12 doesn't eject the disk when VMWare is running. Attaching the drive to a VM and ejecting from there ("Eject" in Windows Explorer for example) does work. Kind of a round about way though. But maybe that's the best I can do with this Mac. Wish they had exposed the eject button...

When logged into a Remote Desktop session, you can request the audio be brought to the local computer (redirected audio). You hear the audio generated by your session. Is there anyway to have the audio generated by other sessions also redirected and forwarded to the local computer?

Sorry about the odd title, can't think of a good way to paraphrase this one.

I have a Win2008 server that is not in a domain. I have two Win2003 machines, one in the domain, one not. All of them have a local account named "testAdmin" with the same password on all three.

By using the synchronized local account, the Win2003 machine can connect to the Win2008 server via RDC, can read the remote Application Event Log, etc.

If I login to the Win2003 domain-attached machine with a domain account, and then try to connect to the Win2008 machine, no dice (expected -- 2008 isn't part of the domain). However, if I use the Windows Event Log Viewer, and try to connect to the Win2008 machine, giving the synchronized local account and password, it still doesn't work (access denied).

Odder still: I can issue a

NET USE \\<win2008>\IPC$ <local_password> /USER:<2003-local-account> 

The IPC$ attach works -- it shows up in a blank NET USE command. However, if I try and look at the Win2008 Event Log, I still get access denied.

So somehow the 2008 machine can tell whether I'm impersonating the local account on the 2003 machine. How can it do this? How can I get the 2008 machine to let me in when logged in as a domain account but use the local account credentials?

I want to do a little SNMP testing and want to issue some traps from a test Ubuntu box. What are the easiest ways (for a Linux noob) to cause some traps to fire?

Thanks