• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 344
  • Last Modified:

Remote Web Workplace Issue?

Myself and an associate have a couple of customers running SBS2003. We are noticing a problem that seems to be happening on both servers.
Domain 1:
SBS 2003 latest service packs installed.
There is a workstation that is running Windows XP Pro.
Win Proxy is running on this XP machine. It is configured to "run as a service" which means that the Win Proxy service will start when the computer boots up.
The issue is that when I connect to that desktop from remote web workplace the Win Proxy service stops and has to be restarted manually. It does not matter if I connect using the domain administrator account or a normal user account.

Domain2:
SBS2003
There is a workstation that is running Windows XP Pro.
There is a software package installed that allows the customer to monitor and record security cameras. This runs as a service also.
Everything works fine until you connect to the desktop using Remote Web Workplace. Then the service that records and monitors the security cameras is not running and has to be manually started.

Has anyone seen issues like this before?
0
Exchange_Admin
Asked:
Exchange_Admin
  • 8
  • 7
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
There are a number of services that will not operate under RDP (which is what RWW is using).  For instance, you can't modify the video settings when connected.

My guess, though, is that these services are running under a user account instead of the Local System account, and that could cause issues like this.  Try running them under the Local System account if this is the case.  Otherwise review your event logs and see if there are any information, warning or error messages about what is shutting down the service.

Jeff
TechSoEasy
0
 
Exchange_AdminAuthor Commented:
Thanks for the response Jeff.
I know for a fact that the machine that is running WinProxy has the service configured to use the Local System Account.
I checked the event viewer logs and cannot see anything out of the ordinary. I do see informational events about the service stopping but no codes or clues.

I don't know about the machine running the security camera software. I don't have the access to that machine.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Exchange_AdminAuthor Commented:
I have some more information on this:
As far as WinProxy goes this may be a bug in WinProxy. They are looking into this.

The WinProxy service will continue to run as long as you close the Remote Desktop screen by selecting START>DISCONNECT or clicking on the "x" in the upper right corner.

If you select LOGOUT then the service is stopped.

But by ending the session via disconnect or the "x" we run into another problem. When the user gets to work they have to reboot the machine to be able to login. If they don't then they get the message that another user is connected.

Russ
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I'm thinking that there is an RPC conflict or filter happening somewhere... so I searched a bit and came across this:
http://www.microsoft.com/downloads/details.aspx?FamilyID=678cdcb6-6f05-45c0-acfa-d8e3774b8e9c&DisplayLang=en

If you read the SBS SP1 release notes (http://download.microsoft.com/download/d/5/b/d5be2c2c-b1cb-47f8-9235-8cf89820139e/SBSRelNotes_WEB.htm) you will see that there have been "Changes in RPC client and server behavior in Windows Server 2003 SP1 cause the ISA Server 2000 RPC filter to deny RPC access to the Windows SBS computer."  These same changes MAY be filtering out WebProxy's calls as well, and for some reason, when you connect a user to that server it binds to the user.

This is a wild theory, but at least part of it makes sense.  :-)

Jeff
TEchSoEasy
0
 
Exchange_AdminAuthor Commented:
"These same changes MAY be filtering out WebProxy's calls as well, and for some reason, when you connect a user to that server it binds to the user."

Good idea Jeff. But this was happening before WinProxy was installed.

From my above post:
"But by ending the session via disconnect or the "x" we run into another problem. When the user gets to work they have to reboot the machine to be able to login. If they don't then they get the message that another user is connected."
This issue was resolved by having the users LOGOUT of the remote session.

Thanks for your input Jeff.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Sorry, I was thinking the two issues were related.  You can fix the problem with users not logging out by adjusting that property in the user properties > session tab.  Set the "End a disconnected session" to a shorter time period, or change the "When a session limit is reached or connection is broken" to "End Session".

Jeff
TechSoEasy
0
 
Exchange_AdminAuthor Commented:
Jeff,
No problem. These are indeed 2 diffent problems but the resolution to resolve the WinProxy service stopping causes the second issue to crop up.
You gotta love the IT world.

Thanks for the suggestion on "end a disconnected session". I will try this.

Russ
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
FYI, if a user gets to work and the machine says another user is connected, then they just need to log in anyhow which will either log out the other user or if that user is actually their account will just let them jump into the session.  The user needs to be a member of the local administrators group on that workstation for this to happen though.

Jeff
TechSoEasy
0
 
Exchange_AdminAuthor Commented:
I am going to close this qustion and award the points.
At this time WinProxy is looking into why the service stops when connecting to the machine using RWW.

I am awarding the points to Jeff (since he is the only one to respond) because he was able to offer a solution to my other issue mentioned.

Thanks Jeff.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Well, I appreciate the gesture, but honestly... if a question is unanswered then it doesn't add much to the knowledge pool... so you really would be better off requesting a refund and having the question deleted.  Which you're welcome to do by posting to the Community Support TA.

Jeff
TechSoEasy
0
 
Exchange_AdminAuthor Commented:
But there is indeed an answer to the problem of having to reboot the workstation after using RWW to access it.
Just not a resolution to my initial problem.

But if you still feel that I should request a refund and have the question deleted I will. Just post back with your request. I will follow you suggestion.

0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Well, such is the problem with having two issues in one question.  :-)  you can let it stay if you like... it's up to you.

(i'm pretty good at tossing the ball back...)

Jeff
TechSoEasy
0
 
Exchange_AdminAuthor Commented:
I will let it stay as is then.

Thanks again for the assistance.
Russ
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
No prob.  :-)

TSE
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 8
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now