Michael Broschat's questions

I am reconstructing (with a different machine) a network situation with a Windows Server 2008 R2 machine with IIS. For some years, I have run this using a Comcast Business connection. The previous server failed, and I'm replacing it. The router firmware (the way Comcast handles the connection to the Internet) seems to be correct (I specify the IP address of the server in the place for Port Forwarding--TCP, port 80).

But attempting to access the site via my publicly available site name (or its IP) yields "cannot display page." From within my home network, entering http://[that server's IP] gives the desired IIS result.

Can anyone suggest what might be going wrong here?

I have for years connected to a small set of servers via Remote Desktop (currently, Win7 client, Win2008 R2 servers). Performance is the equivalent of being directly connected. The client machine is not in the network, but I connect via IP and use network credentials.

Recently, I built a new server (to host Hyper-V), and then a new workstation (Win 7) to manage it and develop on it. This is all on the same network segment as the previously mentioned servers and client.

The new client connects easily to the new server, but latency is so bad that it can take 5-15 seconds for any mouse or keyboard action to be seen and implemented on the server. Trying the other Win7 client exhibits the same behavior. Using the new Win7 client to access the previously mentioned servers behaves identically with the other Win7 client--perfectly. Therefore, whatever the problem is, it is associated with the new server.

This problem is not unknown throughout the web world, and I have found both client-based and server-based fixes. Although tried, the client-based fix (changing AutoTuning values) does not work, nor does the server-based fix (disabling task offload).

Any other recommendations?

I'm a developer who occasionally needs to do server stuff just to get the environment he needs for working.

I have an AD domain (all servers are 2008 R2) with, presumably, a default forest. Works fine. Built a second domain elsewhere, in which I created a SharePoint farm. Now I want to move that domain (which uses a Server Core DC) into the existing forest.

Lots of instructions (and notes about child domains and tree domains), but I'm getting the feeling that all those instructions presume that the new domain is being created within that existing forest. In my case, I want to move the new domain into the old forest (to preserve the various user and service accounts).

What are my options?

[added after a couple responses]

Looking at the first two responses, let me add a wee bit about why I even consider doing this.

I built the SharePoint domain (using virtualized Server Core for the domain controller and one virtual machine for SharePoint, which then uses the Sql Server of the host server for its data store (and I wanted to have a Kerberos environment)) "away" from my "production" environment but using the same ISP. So, all machines are running IPs within the same 256-group. Performance was just fine.

I then built a Windows 7 machine just to connect with that new domain and on which to do whatever development doesn't need to be done directly on the SharePoint server. Works fine.

But upon then connecting with the server machines in the new domain via Remote Desktop Connections, I found that any action taken on the remote server required about 5 seconds to be seen from the Win7 machine. Completely unacceptable for the purpose intended.

Went back to my existing equipment to check its performance, and connecting to those servers via a different Win7 machine show the usual instantaneous response.

So, I concluded (without any real evidence) that the new domain was conflicting with the old domain (even though the old domain isn't affected at all).

I'm now getting the feeling that I can leave the two domains separate (there is certainly no need for them to communicate). But what could be causing the unacceptable performance of Remote Desktop between the Win7 and server machines?

A few years ago, I built a "front page" for my site, using CSS to implement a flexible column system (instead of fixed width). Works fine under IIS 7, but when I upgraded my web server to 2008 R2, the page content displays but no CSS activity is evident.

I brought in a couple pages from a simpler site that works in a different folder, and that works fine, proving that CSS can behave just fine.

I have compared the two pages, and the only differences are in the accompanying CSS code.

I'm attempting to move my Server 2008 (IIS7) to a different machine running R2 (IIS7.5).

Standard IIS features are installed (including static content--re: other ServerFault postings), and the default site page (pure HTML) runs fine--but it has no CSS, included images, etc.

It would certainly appear to be related to the similar "static content" postings here on ServerFault. Under Handler Mappings, I see that CGI-exe and ISAPI-dll are disabled.

Ideas?

We have developed a set of metadata fields for the user to complete during the file upload process (MOSS).

What happens is that the user chooses Upload, then specifies the file on his system. Sometimes, when he sees what metadata data is required, he clicks Cancel, knowing that he cannot supply the data at that time. The file uploads, anyway, and is in the library without any attached metadata.

Our client finds this unacceptable, but I haven't found a way to cancel the actual upload when the user tells us he no longer wants to do so.

I am analyzing ADFS logs, which reference the SharePoint webs visited (via the wcontext parameter) but do so via their GUID.

How do I translate a SharePoint site/web GUID into a URL?