Joseph's questions

I'm standing up a TeamCity server that's running it's own embedded Tomcat instance on Amazon EC2.

I have successfully gotten the instance to respond on port 8111 or 8080, but when I try to change the port to 80 I can't get it to respond on that port.

I have my security group set up to allow port 80, and verified that that's not the problem.

I'm not running anything else on my linux instance, just the TeamCity distro, so I don't have an apache server or anything running.

What seems odd to me is that when I run it on 8111 or 8080 and subsequently do a netstat I can see those ports being listened on, but when I put the port to 80 and run another netstat port 80 never shows up as being listened on.

Does anyone know why I can't get tomcat to respond to port 80?

I just tried to access a folder like so:

\\somecomputeronmynetwork\somelocation$

When going to this location I'm prompted for a user name and password.

I put one in, and it let me in fine.

Now I need to remove that login, so I can try a different user name and password.

What's the easiest way to do this?

I have a windows 2008 server running with FTP 7 on IIS 7.

I have it configured to connect as it is out of the box, with a particular user (lets say john) with read/write access.

When I use my FileZilla client software, I can connect to the server as john just fine. No problems at all. However, when I try to connect using Windows Explorer or using the cmd prompt I get stone walled, saying "Login failed". My client machine is Windows Vista Ultimate.

Does anyone know what might be causing this?

I just recently remoted into a dedicated server I recently got which is running windows server 2008.

I went into the Programs and Features and I don't see any .NET framework installed, but I know its running some version of .NET

Does anyone know what version of .NET windows server 2008 comes with?

Are there any technical/legal/contractual limitations to using a CA certificate on multiple sites that are running on a

single machine?

multiple machines?

Or are the certificates to be used on a per site basis?

Are there any benefits of a self signed certificate on a live site?

I know in IIS 7 you have the ability to self sign a certificate and I was wondering if using that as a precurser to buying one from a CA would be a good idea.

Do you get the same encryption benefits that you get from a CA signed cert or am I confusing terms? (running off the https protocol)

The title says it all. I'm looking for a good set of tools that I can use to load test a web application on IIS 7 before deployment.