You are currently browsing the RDPTECHS Blog weblog archives for the day 15. May 2008.
15. May 2008 by admin.
We are the ultimate web based fast response on-site resource for end users, businesses and corporations, deploy and manage computer service calls anywhere over the internet. We offer support to many different systems and networks over a secure network connection (128bit and 256bit encryption) We offer our services through remote access.
Remote IT Help Desk allows us to troubleshoot and repair a great deal of problems via the internet! This is the most convenient repair service we offer! No need to disconnect, drop off, or wait! We’ll fix your computer right over the internet, anywhere in the world!
Requirements:
1. Broadband Internet access (Cable, DSL, Wireless, etc.) Note: Dialup accounts can use our service. It would not be cost effective to use our services. (due to limitations or dropped connections) Contact us to find out what services will work for you.
2. Must have an e-mail (to receive a download by e-mail for our software)
You can also e-mail our support group at support@rdptechs.net
Posted in Website | No Comments »
15. May 2008 by admin.
Remote Desktop Protocol is based on, and is an extension of, the T-120 family of protocol standards. A multichannel capable protocol allows for separate virtual channels for carrying presentation data, serial device communication, licensing information, highly encrypted data (keyboard, mouse activity), and so on. As RDP is an extension of the core T.Share protocol, several other capabilities are retained as part of the RDP, such as the architectural features necessary to support multipoint (multiparty sessions). Multipoint data delivery allows data from an application to be delivered in “real-time” to multiple parties without having to send the same data to each session individually (for example, Virtual Whiteboards).
In this first release of Windows Terminal Server, however, we are concentrating on providing reliable and fast point-to-point (single- session) communications. Only one data channel will be used in the initial release of Terminal Server 4.0 However, the flexibility of RDP gives plenty of room for functionality in future products.
One reason that Microsoft decided to implement RDP for connectivity purposes within Windows NT Terminal Server is that it provides a very extensible base from which to build many more capabilities. This is because RDP provides 64,000 separate channels for data transmission. However, current transmission activities are only using a single channel (for keyboard, mouse, and presentation data).
Also, RDP is designed to support many different types of Network topologies (such as ISDN, POTS, and many LAN protocols such as IPX, NetBIOS, TCP/IP, and so on). The current version of RDP will only run over TCP/IP but, with customer feedback, other protocol support may be added in future versions.
The activity involved in sending and receiving data through the RDP stack is essentially the same as the seven-layer OSI model standards for common LAN networking today. Data from an application or service to be transmitted is passed down through the protocol stacks, sectioned, directed to a channel (through MCS), encrypted, wrapped, framed, packaged onto the network protocol, and finally addressed and sent over the wire to the client. The returned data works the same way only in reverse, with the packet being stripped of its address, then unwrapped, decrypted, and so on until the data is presented to the application for use. Key portions of the protocol stack modifications occur between the fourth and seventh layers, where the data is encrypted, wrapped and framed, directed to a channel and prioritized.
One of the key points for application developers is that, in using RDP, Microsoft has abstracted away the complexities of dealing with the protocol stack. This allows them to simply write clean, well-designed, well-behaved 32-bit applications, and then the RDP stack implemented by the Terminal Server and its client connections takes care of the rest.
For more information on how applications interact on the Terminal Server and what to be aware of when developing applications for a Windows Terminal Server infrastructure, look at the “Optimizing Applications for Windows NT Server 4.0, Terminal Server Edition” white paper available on the following Microsoft Web site:
http://www.microsoft.com/technet/prodtechnol/win2kts/maintain/optimize/tsappdev.mspx Four components worth discussing within the RDP stack instance are the Multipoint Communication Service (MCSMUX), the Generic Conference Control (GCC), Wdtshare.sys, and Tdtcp.sys. MCSmux and GCC are part of the International Telecommunication Union (ITU) T.120 family. The MCS is made up of two standards: T.122, which defines the multipoint services, and T.125, which specifies the data transmission protocol. MCSMux controls channel assignment (by multiplexing data onto predefined virtual channels within the protocol), priority levels, and segmentation of data being sent. It essentially abstracts the multiple RDP stacks into a single entity, from the perspective of the GCC. GCC is responsible for management of those multiple channels. The GCC allows the creation and deletion of session connections and controls resources provided by MCS. Each Terminal Server protocol (currently, only RDP and Citrix’s ICA are supported) will have a protocol stack instance loaded (a listener stack awaiting a connection request). The Terminal Server device driver coordinates and manages the RDP protocol activity and is made up of smaller components, an RDP driver (Wdtshare.sys) for UI transfer, compression, encryption, framing, and so on, and a transport driver (Tdtcp.sys) to package the protocol onto the underlying network protocol, TCP/IP.
RDP was developed to be entirely independent of its underlying transport stack, in this case TCP/IP. RDP, being completely independent of its transport stack, means that we can add other transport drivers for other network protocols as customers needs for them grow, with little or no significant changes to the foundational parts of the protocol. These are key elements to the performance and extendibility of RDP on the network.
Posted in Learn | No Comments »
15. May 2008 by admin.
To see what IP address, default gateway, and subnet mask your computer is using:
Start button and select All Programs (XP) or Programs (NT and 2000).Accessories, then Command Prompt (2000 and XP), or Command Prompt (NT).For other IP information on Windows, including the physical address, at the command prompt, enter:
ipconfig /all | moreThis will give you information regarding your computer’s TCP/IP setup, including:
Host name
DNS servers
Physical address
IP address
Subnet mask
Default gateway
WINS servers
The IP address will be a series of numbers following the pattern xxx.xxx.xxx.xxx, for example, 156.56.27.32.
The physical address, which many people call the MAC address, will be a series of six hexadecimal number pairs following the pattern xx-xx-xx-xx-xx-xx, for example, 00-40-A4-F3-C0-01.
Note: If you have more than one active network adapter, you will see multiple entries here. Many laptop users nowadays have at least two adapters: one for the regular Ethernet adapter, and one for the wireless 802.11b or 802.11g card. Some computers will have three entries or more (for example, for either an infrared or a Bluetooth adapter). Sometimes it’s easy to distinguish between the two (for example, one of them will say “wireless” next to “Description:”), but other times it’s not (the description will give only a manufacturer and model). You may have to consult the manufacturer’s documentation for your computer to tell which section of the ipconfig/all | more output refers to which network adapter.
Alternatively, in Windows XP, if you want to find this information and want to stay within the graphic user interface, or for any reason do not want to use DOS commands, you can find this information by doing the following:
My Network Places icon, and then select Properties.Local Area Connection icon. Occasionally, there will be a number on the end (e.g., Local Area Connection 2); it depends on your computer’s configuration. If you are looking for the MAC address for a wireless adapter, the icon will normally be named Wireless Network Connection.Support tab.Details... button.The physical address (MAC address) and IP address will be listed in the window that appears.
To check your computer’s IP address or physical address, follow the steps below:
Start button and select Run... .winipcfg and click OK.PPP Adapter if you’re dialing in.The IP address will appear in its labeled field. The MAC address will appear in a field labeled Adapter Address.
Alternatively, you may follow these steps:
Start button and select Settings, then Control Panel.Network. Select TCP/IP, then click Properties.The IP address appears under the IP Address page tab
Posted in Troubleshooting | No Comments »
15. May 2008 by admin.
| Safe Mode in Windows XP |
|
For diagnostic purposes, it is possible to operate Windows with a reduced set of drivers and files. This is called Safe Mode. How to get to Safe Mode is discussed here. What is Safe Mode?All versions of Windows come with a diagnostic setup called “Safe Mode”. Many average PC users are unfamiliar with the purpose of Safe Mode and only encounter it when there has been a system crash or similar problem. They are then puzzled by what to do next. The purpose of Safe Mode is to help troubleshoot computer problems by operating with a bare minimum of drivers and Windows components. By reducing what is running, Safe Mode can help you diagnose a problem caused by a faulty driver or software. How to Get to Safe ModeOne way to reach safe mode is by booting up and pressing the F8 key right after the POST check. In practice this can be tricky to time correctly and all too often you can end up in the regular boot mode. The technique is to repeatedly tap the F8 key until the startup menu appears. Sometimes you will fill up the buffer memory with all the key taps and get an error message or the computer will complain by beeping. Also, the F8 key may not work with a USB keyboard because USB drivers have not yet been loaded. However, newer computers have USB support in the BIOS so this problem should be limited to older machines. When you successfully initiate the boot options selection, the window shown below will open. The menu provides a number of advanced options. The default selection is “Start Windows Normally” and is highlighted. To open in Safe Mode, use the up arrow key to select it and then press the Enter key.
Add Safe Mode to boot menuIf you try out a lot of new gadgets or software and find yourself frequently needing to go into Safe Mode, you can add Safe Mode to the Boot Menu by editing the file boot.ini. The Boot Menu and how to edit it is discussed in detail on another page. For a specific example of adding Safe Mode, see this Elder Geek page Use Msconfig to get to Safe ModeIf you only want to enter Safe Mode occasionally and have trouble using the F8 key, you can use the System Configuration Utility (msconfig) . Go to Start|Run and enter “msconfig” (without quotes). When the utility opens, click on the tab BOOT.INI as shown in the figure below.
Highlight the operating system listed in the section [operating systems] as shown in the figure below. Next put a check by the entry /SAFEBOOT as shown below. Also click the radio button MINIMAL Then reboot. The system should open in Safe Mode. When finished using Safe Mode, open Msconfig again and remove the check by /SAFEBOOT. Otherwise, you will continue to open in Safe Mode whenever you boot.
When the Computer Boots to Safe Mode without AskingMany people have probably had it happen that instead of a normal boot, Windows puts up an error message and boots into Safe Mode. The most common reason for this to happen is that Windows has been shut down improperly. This will be indicated in the error message that comes up first. Generally, all that needs to be done in the case of improper shutdown is to restart the computer and Windows will clean up the problem and reboot normally. If the system continues to go into safe mode, there may be a corrupt file or a driver problem. The error message may indicate the problem. Try doing a system restore. If the problem persists, there may be a problem with spyware or other pest so use the methods for cleanup associated with your particular anti-malware programs. |
Posted in Learn, Troubleshooting | No Comments »
15. May 2008 by admin.
This is often found on a computer that has hardware problems. I found a great site to troubleshoot errors. http://msdn.microsoft.com/en-us/library/ms789516.aspx
Posted in Troubleshooting | No Comments »