How do I modify protocol binding in Windows 2000?

In Windows NT 4.0, it was a simple task to modify protocol binding. At first glance, this option seems to have disappeared from Win2K, but don't worry. Microsoft has just moved it.

1. Open the Network and Dial-up Connections window (Start, Settings, Network and Dial-up Connections).
2. Select the connection you want to modify (e.g., Local Area Connection).
3. From the Advanced menu, select Advanced Settings.
4. Select the Adapters and Bindings tab.
5. Modify the bindings as required.
   
6. Click OK.

What is REXEC?

Windows NT/2000 ships with a command REXEC.EXE which when used in conjunction with a REXEC daemon (REXECD) can run commands on remote systems, hence the name, Remote EXECution.

C:\>rexec 10.129.210.71 -l john@savtech.com dir
Password (10.129.210.71:):
> rexec:connect:Connection refused
rexec: can't establish connection

The -l is the name to use on the remote system, here I've used the Windows 200 format, name@domain.com, however you could also use the older domain\name format.

Notice in the example the command failed, this is because the remote machine did not have the REXEC daemon installed. This is actually a problem, Windows NT/2000 does not have a REXEC daemon, only the client. REXEC does not only work for NT servers, but also Unix, VMS and anything else that supports REXEC.

What is Universal Plug and Play (UPnP)?

UPnP is a peer-to-peer network architecture for connecting intelligent appliances, wireless devices, and PCs that are in close proximity. The architecture is based on TCP/IP and Web technologies that provide easy-to-use, flexible, standards-based connectivity to ad-hoc or unmanaged home, small-business, public-space, and Internet-based networks.

UPnP does more than just extend the Plug and Play (PnP) peripheral model. According to Microsoft's Web site, UPnP supports zero-configuration, "invisible" networking, and automatic discovery for a breadth of device categories from a wide range of vendors. Through this design, a UPnP device can dynamically join a network, obtain an IP address, convey device capabilities, and learn about the presence and capabilities of other UPnP devices.

UPnP leverages Internet components, including IP, TCP, UDP, HTTP, and XML. For example, UPnP establishes contracts based on wire protocols that are declarative, expressed in XML, and communicated via HTTP. UPnP is well suited for IP internetworking because it was explicitly designed to span different physical media, enable real-world multiple-vendor interoperation, and achieve synergy between the Internet and many home and office intranets. Further, UPnP can use a technique known as bridging to accommodate media that runs non-IP protocols.

Because UPnP uses common protocols, instead of device drivers, UPnP networks can run on any media, including phone lines, power lines, Ethernet, radio frequency (RF), and FireWire. You can use any programming language on any OS to address UPnP devices. Windows XP and later OSs use two new services--the Simple Service Discovery Protocol (SSDP) discovery service and the UPnP device hosting service--to natively support UPnP.

What REXEC daemons (REXECD) are available for NT/2000?

Microsoft do not provide an EXEC daemon for NT however there are 3rd party solutions:

• http://www.denicomp.com/rexecnt.htm - Winsock REXECD/NT
• http://www.ataman.com/products.html#ATRLS - Ataman TCP Remote Logon Services

Where is Microsoft NetMeeting in Windows XP?

NetMeeting is a standard XP component that's hidden until you initially configuration. NetMeeting lets you participate in virtual meetings, work in shared applications, share data over the Internet or an intranet, and share live video with others in far-away places.

To enable NetMeeting, perform the following steps:

1. Go to the Start menu and select Run.
2. Type

   Conf 

   and click OK.
3. After the NetMeeting configuration wizard starts, click Next.
4. Enter your personal details and click Next.
5. Select listing directory options and click Next.
6. Select your connection media and click Next.
7. Configure the shortcut options to your liking and click Next.
8. Click Next to configure volume options and Next again to confirm that the microphone works.
9. Click Finish.

To begin a NetMeeting session, start NetMeeting (e.g., run conf.exe again to start the application or select the appropriate shortcut from the Start menu or desktop), click the Phone button, and enter the IP address of the machine you want to communicate with.

 1    2    3    4    5    6    [>>]