Wireless Print Servers

A print server is basically a computer that is connected with the printers or print devices. It is composed of an operating system like Windows XP, Vista and client computers. Client computers send requests to the print server and it fulfills those requests. It processes these requests on the first come first serve basis. Now let us discuss about the wireless print server. Due to the wireless print server, one or two printers can be easily shared across a WiFi network. These are available in both 802.11b and 802.11g varieties for home networks. Advantages of wireless print servers are as follows:

• It permits that printers can be positioned anywhere, but within the network range.
• For performing a print job, it is not required that the computer always be turned on.
• It has the facility to transfer the work of a printer to another one present in the network.
• This feature also increases the performance of the printers.
• Administrators can alter the computer names and other settings, without assembling the network printing settings.

USB 1.1 or USB 2.0 is normally used for connecting the wireless print server with the printers. The print server itself can be linked with a wireless router over WiFi. For completing the initial configuration of the device, you have to install the setup software on one computer. This software is present on the CD-ROM, which is included with the print server products. Like network adapters, wireless print servers should be configured with the correct network name and encryption settings. A client software should be installed on each computer demanding the use of a printer.

Alteration in Terminal Server's listening Port

As we have described earlier about installing Telnet Server 2003 that is how to install telnet server 2003, now will describe how to alter listening port of your Server.

It is a well-known fact that TCP port 3389 is used by Terminal Server and Windows 2000 Terminal Services for client connections. Alteration in this port is not recommended by Microsoft. But you can change this port. You have to perform this task carefully, otherwise you will face serious problems.

You have to give more concentration while modifying the registry. If you want to change the default port, then you have to follow these steps:

• You start with the task of running Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp.
• Then you have to find the port number subkey and notice the value of 00000D3D, hex is for 3389.
• After this, you have to change the port number in Hex and save the new value

If you want to change the port for a particular connection on the Terminal Server then follow these steps:

• You have to run Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\connection.
• After this, you have to find the port number subkey and notice the value of 00000D3D, here hex is for 3389.
• Then you have to change the port number in Hex and save this new value.

After performing this, you have to make alteration in the Port on the Client Side. Follow these steps to perform this:

• You have to open Client Connection Manager.
• Then on the File menu, click on New Connection and then create the new connection. After executing the wizard, you will view a new connection listed there.
• Then you have to ensure that new connection is highlighted. After this, on the File menu, click Export.
• Then you have to edit the .cns file using Notepad. You have to make modifications in the server port, Server Port=3389 to Server Port= new port number, that you had specified on Terminal Server.
• Now import the file back into Client Connection Manager. Then you will be demanded to overwrite the current one.
• If it has the same name, then overwrite it.

In this way, you will receive a client that has the correct port settings to match your Terminal Server settings. Hope it will help you out, Don’t Forget to subscribe to my blog for more tips and tricks on server and Microsoft Server Support Services

Telnet Server 2003 Installation

Telnet is a server solution added to Microsoft server software including Windows 2003. Telnet services are not automatically enabled when you install the operating system. Administrators must add telnet services after installation of Windows 2003. Installing and enabling telnet only takes a few steps in the Windows Control Panel.

Please follow the following steps and you will able to enable telnet services on you system;

• Click the Windows "Start" button and select "Control Panel." Double-click the "Add/Remove Programs" icon. This opens a window with all the installed components on the Windows 2003 server.


• Click the "Windows Components" tab. Select "Telnet Services" from the list and click "Ok." The installation may take a few minutes. Once it is finished, click "Ok" to close the window.


• Click the Windows "Start" button again and select "Run." Type "services.msc" into the textbox and click "Ok." This opens the Services window. Although telnet is installed, the service needs to be configured to run.


• Scroll down to the service labeled "Telnet." Right-click the service and select "Properties."


• Select "Automatic" from the drop-down box in the "Startup" section. This enables Telnet to start when the computer is booted.


• Click the "Ok" button to save changes. Right-click the service again and select "Start." This enables the service without rebooting.

If you still feeling difficulty then we are 24/7 with you for all type of server solution.

So just login at : http://www.iyogibusiness.com/managed-monitoring.html

Windows Server Set-up

Since the inception of Windows-based domains, the ability to provide robust and resilient authentication mechanism in inherently non-secure locations constituted a challenging and risky undertaking. Placing a domain controllers in an office without appropriately protected data center or in a DMZ section of the network jeopardized confidentiality of its content, including all credentials stored in its database. Any accidental corruption (not unlikely in environments lacking qualified local support) or a malicious hack propagating back to the rest of the network could easily lead to an enterprise-wide disaster.

On the other hand, relaying authentication requests to domain controllers residing within properly protected main office or internal network frequently was not feasible due to security, performance or reliability implications. To address these issues, Microsoft customized some of standard Active Directory mechanisms, bundled them together and released the resulting combination as part of the new product feature set in the form of Read Only Domain Controller (or simply RODC).

The main purpose of this customization was to reduce the range and severity of vulnerabilities associated with hosting full-fledged domain controllers in environments where they could be easily compromised. In general, the resulting changes can be grouped in the following three categories, depending on the functionality they provide:
Preventing any unauthorized or potentially harmful changes from replicating back to the rest of domain controllers.

This goal was accomplished by having Active Directory database operating in read-only mode. In cases where write access is required (e.g., due to application-specific requirements), RODC returns a referral to a Windows Sever 2008 writable domain controller, which availability is, incidentally, one of the prerequisites for installing RODC.

The same rule applies to Active Directory integrated DNS zones, which are implemented typically in the form of ForestDNSZones and DomainDNSZones application partitions. Although the RODC is fully capable of responding to any query regarding its authoritative or cached records, new registrations or updates are handled through referrals (making the client responsible for contacting DNS server residing on a writable instance of Windows Server 2008-based domain controller). However, the local server will attempt to keep its copy of the respective zone up to date, by reaching out to the referenced server and requesting replication of the most recent change.

With no originating writes to the replica of the database and to the content of SYSVOL (hosting file system portion of Group Policies Templates), there is no reason for the RODC to participate in traditional multimaster replication, which has been one of the core principles in earlier implementations of Active Directory. Consistency of its content is ensured by maintaining uni-directional inbound replication (including Distributed File System Replication mechanism that, with Windows Server 2008 domain functional level in place, is used to keep SYSVOL current) from full-fledged domain controllers. This is reflected by the lack of connection objects in Active Directory Site.

Three basic mechanisms deliver this functionality. The first one relies on restrictions placed on caching of user and computer credentials in the RODC database, which are controlled by the Password Replication Policy; the second involves RODC-specific krbtgt accounts; and the third is based on filtering attributes of objects replicated to RODCs.

Password Replication Policy settings are revealed during setup of an RODC via the Active Directory Domain Services Installation Wizard. This allows you to designate security principals (users, groups and computers), for which the credentials caching allow or deny rules will apply. By default, the denied list includes four domain built-in groups (Administrators, Server Operators, Backup Operators and Account Operators) and the Denied RODC Password Replication Group (containing Cert Publishers, Domain Admins, Domain Controllers, Enterprise Admins, Group Policy Creator Owners, Read-only Domain Controllers and Schema Admins domain groups, as well as krbtgt domain-level user account). Allowed consists of a single Allowed RODC Password Replication Group (initially empty), but you can customize each to match your preferences, either directly from the same page or after the wizard completes. In the case of conflicting settings, deny rule always takes precedence.

During a local computer startup or user logon, RODC reaches out to a writable Windows Server 2008 domain controller to verify its credentials. If the response is positive, RODC requests the password hash so it can be stored locally and reused during subsequent authentication requests from the same security principal. Its full-fledged counterpart that provided this information verifies that the step will not violate established Password Replication Policy. Assuming that is not the case, it forwards the hash to RODC.
Source: enterpriseitplanet.com

Microsoft's Windows Server

In the world of information technology, businesses turn to servers to manage the storage, flow and backup of just about every bit of important data. What about the family home? Many households around the world have broadband wireless networks, multiple PCs and everything from priceless vacation photos to bank account information stored on individual PC hard drives. Their networks are already in place with PCs in multiple rooms, but where's the central home server to connect and protect them all?

Microsoft and HP have paired up Windows Home Server and HP's Media Smart Server to create the dominant lead in this nascent home server space, though the dynamic duo is far from the first to tackle the mass-market digital home. Tech-savvy enthusiasts have been building and deploying their own servers -- often Linux-based since they're relatively cheap. However, solutions that are pre-built and ready for consumers remains the key needed to unlock the well-served home.

Consumers are confused, and what's worse, technology vendors have made their own missteps as well. So what's going on? What's here and real and useful? Is there a home server that millions of households can call their own?

I think part of the problem with the market for home servers is, there's been a great deal of confusion at the vendor level about defining what a home server is going to be,"

"There has been a lot of visionary products. For example, Intel had Viiv, but it didn't take off, and they finally put a bullet into it a few weeks ago. And that sort of confusion of what the integrated home network world is going to look like has translated into confusion for consumers," he explained.

A home server is basically a PC-like device capable of storing files, running applications and providing access to files and applications over a local network or even over the Internet. It's also a backup device, but it's more functional than a network-connected hard drive, and far more functional than a standalone PC-connected external backup drive (like the common USB (Universal Serial Bus) drives available at any electronics store).

What about Apple TV? Is that a home server? Apple TV is more of a media extender -- while it comes with a hard drive and connects to a TV and home wireless network, it's all about using media files stored on a Mac or PC and moving them to the living room HD TV for viewing. It doesn't provide a backup of the files, let alone a backup of the entire Mac or PC where the files are stored.

What about Microsoft's Windows Media Center? Is that a home server? Nope. Windows Media Center is an application -- albeit a really cool application -- that uses the PC on which it's installed to work as a home media hub. To get it from Microsoft, you need to have Windows XP Media Center Edition, Windows Vista Home Premium or Vista Ultimate. The application then uses a second device, called a "Windows Media Center Extender" -- or even an Xbox 360 to bring photos, videos and music to a home's television. There are other features built into Windows Media Center, and PCs can utilize integrated television tuners for watching and recording shows.

Still, while Windows Media Center and Windows Media Center Extenders can let consumers use media all around the house, it's not a home server.

How about an extra PC that's designated as a home server, even though it may not have been mass-produced for that idea in mind?

Some tech-savvy consumers will use an old PC and set it up to function as a server on their networks, but usually this means it's just a PC with a hard drive that other PCs can access. Some Apple aficionados have used the little Mac Mini as a central storage hub for iPhoto and iTunes libraries, for example, but it's not designed to be a home server either.

Home Theater PCs (HTPC) as simply PCs designed to be connected to home theater systems, most notably to HD televisions. The primary benefit of an HTPC is to access and use all your home media files in the living room, on the big screen. An HTPC has an advantage over a media extender, for example, in that it'll let you run any PC application you want on your big screen, as well as browse the Web. HTPCs have been all the rage for a small number of enthusiasts, but haven't really caught on with a broad range of consumers.

"Home theater PCs is suffering a well deserved death in the market. The PC does not belong in the living room," Van Baker, vice president of research for Gartner (NYSE: IT) , told TechNewsWorld. "The confusion [with home servers] lies more in the advantages of a dedicated device versus just using the PC with the biggest hard drive to back up other PCs."

When it comes to dedicated home servers, the main benefit for consumers is automated backup, Baker said. "But there are a number of applications that are coming along as well, including an integrated iTunes library and photo library on the HP server. More will come, I am sure. But that said, this market will be slow to develop. Most consumers are going to ask why they need a home server, and that education process will be a slow one. It is also hard to demo the value at retail," he added.

”One of the issues is as simple as the term 'server' to consumers. It tends to conjure up nightmares of technical problems and IT support from some people," Joyce Putscher, principal analyst of residential connectivity for In-Stat, told TechNewsWorld. "However, when you ask consumers if they would like to listen to their digital music that they have on their PC on a stereo system that is in another room in the house -- think legacy stereo system in the living room -- most broadband consumers say, 'Yes.'"

Source: www.technewsworld.com