Can only open files through Terminal Server, not directly

Reaction score
1
Location
Nashville, TN
First of all, sorry this is so long, but wanted to give as many details as possible.

I have just inherited a fairly new SBS2008 server from a client who just moved to town. The server is only a couple of months old and the former IT guy set it up and configured it. It has Windows Server 2008 (32bit) running in a VMWare virtual server being used as a Terminal Server. It is a Dell PowerEdge T410 with two Quad Core 2.13Ghz Processors. 16GB Ram total with 6GB of that assigned to the Terminal Server. User workstations are either Vista Professional or Windows 7 Professional. Using a Watchguard firewall and Netgear gigabit switch. All users are hardwired. SBS is performing DHCP and DNS.

The employees here used the Terminal Server to connect and get email, files, etc before the server made it's way out here. Now that the server is here, the couple of employees still in the other city use it to connect remotely.

All of the user's data is stored on a separate array from the OS, in this case the D: drive. Antivirus and software CDs are also on the D drive. There are several software programs that I need to install using the installation files on the D drive.

So, here's the issue. All users can map drives to the folders that they need on the D drive. They can browse through all of the folders. When they try to access data on the D drive, it will not open. Example. There is a folder that contains a lot of fax cover sheets. Each user can browse the list of cover sheets, created in MS word. When you try to double click to open a file, let's say Fax #1, it launches Word, kind of stalls for a second and you can see in the status bar : Downloading Fax #1. Then an error message comes up that says "Cannot open Fax #1" and gives no error code and no specific details. This happens with every user on the local network. I have gone back to the folders and made sure that all users have full permissions and have even added each user one by one and given them full permissions. This seems to happen on every document that they try to open.

When I go to their local workstation and try to browse to the folders that contain the software installations, Peachtree in one instance, I can see it, but when I click the setup.exe file, it takes a little while and then gives me an error message. They seem to vary based upon what files I try to open, but basically say they can't read the file, or it isn't a valid application.

We also have Trend Micro Worry Free Business Security. I tried to install to several workstations yesterday and it took a really long time. I used the email install link and it would log onto the server and start downloading and installing the antivirus, but it was running for an hour and a half when we had to stop it. Other clients I have, when I install Trend Micro, it rarely takes longer than five minutes.

Now, here's the kicker. All of the users still have the link on their desktops to access the Terminal Server from when the server was still in the other city. If they open the Terminal Server session, they can get to all of their documents and open them just fine. No lag or hesitation, just open right up.

The local subnet is 192.168.22.0/24. I opened up the DNS snap in on the SBS server and noticed there were two A records for other subnets. One was 192.168.79.1 and one was 192.168.30.1. If I pinged them, I got a reply. In looking more closely at the network connections, each VMware virtual adapter has one of these IPs assigned.

I'm about at a loss here. When I setup servers myself, I know they will work well. I feel like I am untying someone else's knot here and of course people are looking to me to fix it pronto. I don't know if this is a DNS issue, a permissions issue or what. I feel like I have looked at so many things that I am just running in a circle here.

If I can provide any more details that I might be leaving out, please ask. Thanks!
 
As an update to this -

It appears that it is just MS office documents that will not open at all. PDFs and Jpegs will open, albeit extremely slow, like 20-30 seconds to open. Browsing network folders is fast, but accessing files is slow. The MS office documents take 30-40 seconds before it will say that it cannot open the document and like I said, the PDFs and Jpegs will open, but take a long time.
 
So the physical poweredge servers OS is in the 192.168.22.xxx range and the two VMWare servers are in 192.168.30.xxx and 192.168.79.xxx range? When you say you can ping and get a reply, where are you pinging from and to?
 
So the physical poweredge servers OS is in the 192.168.22.xxx range and the two VMWare servers are in 192.168.30.xxx and 192.168.79.xxx range? When you say you can ping and get a reply, where are you pinging from and to?

Thanks for the reply. Yes, the physical server running SBS2008 has the IP of 192.168.22.2. I noticed that when I pull up the network connections from within the control panel of the SBS , in addition to the Local Area Connection, there are two VMWare Virtual Adapters. One having a 192.168.30.1 address and one having a 192.168.79.1 address.

BUT, from within the Virtual Server, the local area connection IP is 192.168.22.3. 192.168.22.3 is the IP address that we use to with Remote Desktop for the users to access the Terminal Server (which is running Server 2008 in a VMWare virtual machine).

When I am pinging, I have the command prompt open on the physical SBS pinging FROM 192.168.22.2 to the other addresses.
 
Sounds like a permissions issue.

If it opens locally when you're connecting via terminal server, but not when you're accessing via network share, I would check the share permissions. pdfs and jpgs don't need write permissions, but office documents would.

Share permissions are probably set to read, but ntfs permissions are set with the proper permissions.
 
Last edited:
Is it a constant reply back or is there some data loss? Also, what are the reply times associated with the replys. I'm thinking it has to do with routing. The physical server OS might need to have Windows routing turned on and routing the the other subnets.
 
Sounds like a permissions issue.

If it opens locally when you're connecting via terminal server, but not when you're accessing via network share, I would check the share permissions. pdfs and jpgs don't need write permissions, but office documents would.

Share permissions are probably set to read, but ntfs permissions are set with the proper permissions.


That was my intial thought too. I have added user groups with full permissions and even tried individual users with full permissions to no avail.
 
Is it a constant reply back or is there some data loss? Also, what are the reply times associated with the replys. I'm thinking it has to do with routing. The physical server OS might need to have Windows routing turned on and routing the the other subnets.

There does not appear to be any data loss. If I open a Word file, it will launch Word. Let's say I am trying to open Fax Cover.doc. Once Word launches, at the bottom, I notice it says Downloading Fax Cover.doc. It stays that way for 30-40 seconds and then comes up and says "Cannot open Fax Cover.doc".

There are also some software install cds ripped to the server. It will not let me install the programs to any of the computers from the server either.

My gut tells me it is a DNS or routing issue. The network performance seems slow. All of the machines have gigabit adapters and we have a gigabit switch, so it should be fast. Browsing to the proper folders seems fast, but just when I try to actually open something is when the problem occurs.

This is the first time that I have had a server running in a virtual environment as well and I don't quite understand why the VMWare adapters have IPs on different subnets.

I opened up DNS manager on the physical box and saw that there were A records for the virtual adapters on the box and thought maybe the different subnets were messing things up, so I deleted them, but they have been recreated.

How do I verify if Windows routing is already turned on?
 
The Windows feature is called Routing and Remote Access. If it is not already enabled, go to control panel > programs and features > turn windows features on/off and I believe you can turn it on from there. You might also be able to turn it on from the Windows 2008 console by adding a role. Once you have installed this and configured it (can't give you much help in configuration but I can try) it should be able to setup the routing between the 3 subnets.
 
The Windows feature is called Routing and Remote Access. If it is not already enabled, go to control panel > programs and features > turn windows features on/off and I believe you can turn it on from there. You might also be able to turn it on from the Windows 2008 console by adding a role. Once you have installed this and configured it (can't give you much help in configuration but I can try) it should be able to setup the routing between the 3 subnets.

Ok, so I had made the assumption that routing and remote access was turned on because I always turn it on, but guess the previous guy did not. So I turned it on. I also noticed that Windows Search was enabled and producing some errors when trying to index some files, so I turned that role off. I generally don't enable in on my own machines. Rebooted server and still no luck.

I tried a different network switch just to make sure that there wasn't an issue with the current one dropping packets or something. Still no luck.
:mad:
 
I've never used RRAS but I'm pretty sure you have to configure it. Set it up so it knows what subnets its dealing with and where they need to go. Did you see anything like that? What kind of reply times were you getting from your ping? should be < 1ms.

EDIT: I would also see what kind of times and packet loss, if any, you are recieving on one of the PC's to the vmware servers. Out of curiosity, what network are the PC's on?
 
Last edited:
I've never used RRAS but I'm pretty sure you have to configure it. Set it up so it knows what subnets its dealing with and where they need to go. Did you see anything like that? What kind of reply times were you getting from your ping? should be < 1ms.

EDIT: I would also see what kind of times and packet loss, if any, you are recieving on one of the PC's to the vmware servers. Out of curiosity, what network are the PC's on?

All computers are on the 192.168.22.0/24 network.
IP address of physical server is 192.168.22.2
IP address of virtual server is 192.168.22.3 (this is the address used in remote desktop to access virtual server)

There are two VMWare network adapters on the physical server with addresses of 192.168.79.1 and 192.168.30.1 (I don't quite understand why this is)

Tried pinging physical and virtual server IPs from workstation. No packet loss, >1ms reply time. Received no response on workstation with trying to ping 192.168.79.1 and 192.168.30.1, 100% packet loss.

Tried pinging workstations and virtual server from physical server. No packet loss, >1ms reply time. Tried pinging 192.168.79.1 and 192.168.30.1 from physical server and had >1ms reply time and no packet loss.

In regards to RRAS, I did not configure anything, I just started the service. The more I think about this, please feel free to correct me, is this needed? I could see that if people were connected to the Terminal Server and were having problems accessing files, but in this case, that works perfectly fine, it is the local workstations, on the same subnet as the physical server, that cannot open files located on the physical server.
 
Interesting result: Went to speedtest.net on the server and workstations.

Workstations show download speed around 12Mbps and upload of about 4.5 Mbps.


Server shows download speed of around 12Mbps and upload speed of 0.07Mbps.
 
Re:

IHelp did you find a solution yet?

This is becoming interesting. I am curious to where the problem is now.
I am offering my help for a couple of hours to look into this. Do you want to do a remote desktop or something?

Let me know!
 
IHelp did you find a solution yet?

This is becoming interesting. I am curious to where the problem is now.
I am offering my help for a couple of hours to look into this. Do you want to do a remote desktop or something?

Let me know!


Onetech,

Thanks so much for your offer! After working on this for about a month, I had a breakthrough tonight.

The server had an unexpected shutdown earlier today. I was combing through event logs when I noticed something odd. There was an error that the Microsoft Virtual Server was having trouble connecting to something.

Now, I think I mentioned earlier, our Terminal Server is running virtually inside of VMWare virtual server. The tech consultant in the other state had originally setup the Terminal Server using the Microsoft program. Then something broke and he could not fix it. So, he set the Terminal Server backup in the VMWare program.

BUT, he never removed the Microsoft Virtual Server, nor stopped the processes from running, even though the virtual machine was in a saved state. I stopped the MSVS processes from running and uninstalled the software. After that, I connected to a local workstation remotely and was able to open up all the files with no problems at all. I also had problems originally not being able to access software stored on the server to install on the workstations. I am now able to get them to run with no problems.

There were no shortcuts to the MSVS or any other indication that it was still on the system, unless I went looking for it. I guess I had assumed the other tech consultant had removed MSVS when installing VMWare.

I guess I'm really not sure what the actual issue was, other than obviously having two different virtual server programs running at the same time, even if one of them didn't have a VM running, caused some sort of conflict.

I am going to have the users test more extensively tomorrow to make sure they can access everything, but it looks as if the problem may have been solved. (I hope!)

I'll be so glad to be able to focus my efforts on other things now and not have this hanging over my head!!
 
Back
Top