kigge lige på den solutions
Using Remote Web Workplace to connect a remote computer to a client computer results in an error message before the connection is established.
Note
The client computer you are connecting to must be running Microsoft Windows 2000 or later.
Cause: The client computer may not be turned on.
Solution: Verify that the client computer is powered on and connected to the Windows Small Business Server network.
Cause: Remote Desktop connections may not be enabled on the client computer.
Solution: Verify that Remote Desktop is enabled on the computer you are connecting to.
To enable Remote Desktop
To complete this procedure, you must be logged on as a member of the Domain Admins security group.
Click Start, click Control Panel, click Performance and Maintenance, and then click System.
On the Remote tab, select the Allow users to connect remotely to this computer check box.
Ensure that you have the proper permissions to connect to your computer remotely, and then click OK. You must be an administrator or a member of the Remote Desktop Users group to connect remotely to your computer.
Verify that Remote Desktop is enabled by creating a Remote Desktop connection from another computer on the Windows Small Business Server network, and then attempting to connect to your computer. To start Remote Desktop, click Start, point to All Programs, point to Accessories, point to Communications, and then click Remote Desktop Connection.
If you are running any firewall software on the client computer, ensure that it is not blocking access to port 3389 (the port specific to Remote Desktop Connections). For more information, see the firewall manufacturer's documentation.
Cause: The remote computer may have reached the maximum number of allowed connections.
Solution: Verify that the computer you are connecting to has not reached the maximum number of allowed connections. If you are connecting to a computer running Windows XP Professional, only one user can be connected at a time. If you are connecting to an application sharing server, connections are determined by the number of client access licenses (CALs) purchased by your company. For more information, see your administrator.
Cause: Firewall settings may be blocking port 4125.
Solution: Verify that port 4125 (the port specific to the Remote Web Workplace) is open to the Internet on the computer running Windows Small Business Server. If you ran the Configure E-mail and Internet Connection Wizard, and chose to publish the Remote Web Workplace, this is configured automatically on the server. If you have a router or firewall device that does not support Universal Plug and Play (UPnp), you must manually configure this device to accept Internet traffic through port 4125. For more information, see the device manufacturer's documentation.
If the computer running Windows Small Business Server is running Microsoft Internet Security and Acceleration (ISA) Server, run the Configure E-mail and Internet Connection Wizard, choose to publish the Remote Web Workplace, and ISA Server will be automatically configured to allow Remote Desktop connections.
If you are connecting from a remote computer that accesses the Internet through ISA Server, the person responsible for ISA Server must create a protocol rule allowing outbound traffic through port 4125. You must also install ISA Firewall Client on the remote computer.
Verify that your Internet service provider (ISP) is not blocking Internet traffic through port 4125.
A client computer does not appear in the Computers list after you click Connect to my computer at work.
Cause: The client computer has not been joined to the Windows Small Business Server domain.
Solution: Join the client computer to the Windows Small Business Server domain.
To join the client computer to the Windows Small Business Server domain
Open Internet Explorer, and type the following URL in the address bar:
https://servername/connectcomputer (where servername is the name of the computer running Windows Small Business Server 2003).
Click Connect to the network now, and follow the instructions in the Network Configuration Wizard to join the client computer to the Windows Small Business Server domain.
Cause: The computer is not running Windows 2000 Professional or later.
Solution: Verify that the client computer is running Windows 2000 Professional or later.
Cause: You are attempting to access the Remote Web Workplace from the computer you are logged on to.
Solution: Access the Remote Web Workplace from another computer.
Note
Computers running server operating systems do not appear in the list of computers you can connect to. Application sharing servers are available through the Connect to my company’s application-sharing server link.
Links appear in and disappear from the Remote Web Workplace.
Cause: Remote Web Workplace links are dynamic, and are based on Windows Small Business Server network features that are available from the Internet. Links may also be manually disabled by your network administrator for security reasons, and they may not appear if you are accessing the Remote Web Workplace from a public or shared computer that is using an earlier browser.
Solution: This behavior is by design. If a link that you regularly use disappears, contact your administrator, upgrade the browser on the public or shared computer to the latest version, or access the Remote Web Workplace from a computer that is not public or shared.
Remote Web Workplace features are inaccessible with my Web browser.
Cause: Some browsers do not support technology required by the Remote Web Workplace. This technology may include the use of unsigned certificates, ActiveX Controls (which are required for Remote Desktop sessions), and Windows Integrated Authentication (which is required for accessing Monitoring links and your company's internal Web site).
Solution: Upgrade to the latest version of the Web browser and ensure the browser supports the noted technologies.
The connection to the Remote Web Workplace is frequently interrupted or lost.
Cause: The Remote Web Workplace contains a built-in timeout feature for security reasons. When your session has been inactive for a specified period of time, you are logged off automatically. The Remote Web Workplace will timeout after 20 minutes of inactivity by default if you use the site from a public or shared computer. If the computer is not public or shared, the timeout is 120 minutes by default.
Solution: If you would prefer the 120-minute timeout, you can access the Remote Web Workplace from a computer that is not public or shared, and clear the I'm using a public or shared computer check box on the logon page.
If you need more time, contact your network administrator. The timeout values for the Remote Web Workplace can be manually configured. However, seriously consider the security implications of a longer timeout.
Cause: If you run a backup program or antivirus scan while remote users are connected to the network, Remote Web Workplace remote desktop sessions may be disconnected. If this occurs, the error message "An Internal Error has occurred" appears, and users are returned to the Remote Web Workplace computer selection page or log on page. At this point, users can log back on to the remote computer and resume work.
Solution: A supported fix is available from Microsoft. For more information, see Knowledge Base article 821438 at the Microsoft Product Support Services Web site (
http://go.microsoft.com/fwlink/?LinkId=19635).
Note
As a best practice, backups and antivirus scans should be scheduled for times when users are least likely to be logged on to a remote session.
Cause: Certain Internet connection types, such as dial-up and PPoE connections, may be subject to timeouts due to inactivity.
Solution: This is by design. Contact your Internet service provider if you require a longer timeout period.
Cause: Intermittent drops in connectivity may result from wireless or faulty network connections.
Solution: Ensure that network hardware is not resetting. See your hardware vendors documentation
Ny bruger
Nybegynder
Opret
Preview
