My situation:
I am a reitred Oracle Database Administrator with little expertise in Windows. I am currently doing volunteer work for an organization of volunteers maintaining their network of 8 computers in a Windows XP Professional Workgroup. I have little experience but am learning.
The volunteer who set the system up did not leave any documentation behind.
I need to learn more about
1. installing Windows and configuring Workgroups
2. adding a new computer to the system
3. Networking in general (in this context).
Can anyone point me in toward a good website or well-written book on these subjects?
Thanks very much
Andy Nicsatro

Answer Wiki

To change the computer name, to join a domain, or to add a computer description for a Windows XP-based computer, use the Computer Name tab in the System Properties dialog box. To locate this tab, use one of the following methods:

Change the computer name and join a domain or a workgroup
To change a computer name and to join a domain or a workgroup, follow these steps.

Warning Before you change a computer’s membership from a domain to a workgroup, be sure that you know the user name and the password for an account in the local Administrators group. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
317049 (http://support.microsoft.com/kb/317049/ ) You cannot log on after you remove the computer from the domain

1. Click the Computer Name tab, and then click Change.
2. Type the new computer name in the Computer name dialog box.
3. Type the new domain or workgroup in either the Domain dialog box or the Workgroup dialog box.
4. Click More to change the primary Domain Name System (DNS) suffix.

Note Windows XP Home Edition is not designed to join domains. Windows XP Home Edition is only designed to join workgroups. Therefore, use Windows XP Professional to join domains.
5. Click OK three times, and then restart the computer.

Add a computer description
To add a computer description, type a name or a description in the Computer description box on the Computer Name tab, and then click Apply.
Network ID Wizard
If you do not know how to complete these tasks, you can use the Network Identification (ID) Wizard to help you. To start the Network ID Wizard, follow these steps:

1. In the System Properties dialog box, click Network ID.

Note This wizard is new to Windows XP. With this wizard, you can add the computer to a workgroup or to a domain.
2. Move backward and forward in the wizard by using the Back and Next buttons.

The first set of options in the Network ID Wizard is as follows:

* Option 1
“This computer is part of a business network, and I use it to connect to other computers at work.”
* Option 2
“This computer is for home use and is not part of a business network.”

If you select option 1, the following options appear:

* Option 1a
“My company uses a network with a domain.”
* Option 1b
“My company uses a network without a domain.”

If you select option 1a, a dialog box appears that requests the following information:

If you select option 1b, you can also configure the computer as a “Workgroup Member,” and you can type the name of the workgroup.

If you select option 2, you are prompted to click Finish to restart the computer. If you follow this step, the computer is configured as a “Workgroup Member.” By default, the name of the workgroup is “Workgroup.”

Then, the next page requires the domain name to which the computer is to be added. Also, the next page requires the username and the password of an account that has the rights to add a computer to the domain. Additionally, the next page enables the user account from the previous page to be added to this computer. Finally, the next page enables the new user to have various rights on the local computer.

The user may be added to the following built-in groups on the local computer:

Note If the computer is a member of a domain, the computer also maintains a local domain that has security accounts. These security accounts only pertain to that computer. To change domains at the logon screen, press CTRL+ALT+DELETE. If the Domain box does not appear, click the Options button to display the Domain box, and then select the required domain from the menu.

Note Generally, you must have Administrator credentials on the computer to complete the tasks that are mentioned in this article.

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
246804 (http://support.microsoft.com/kb/246804/ ) How to enable/disable Windows 2000 Dynamic DNS registrations
255913 (http://support.microsoft.com/kb/255913/ ) Integrating Windows 2000 DNS into an existing BIND or Windows NT 4.0-based DNS namespace
Back to the top
Windows Server 2003
To change the computer name, to join a domain, or to add a computer description for a Windows Server 2003-based computer, use the Computer Name tab in the System Properties dialog box. To locate this tab, use one of the following methods:

Change a computer name and join a domain or a workgroup
To change a computer name and to join a domain or a workgroup, follow these steps:

1. Click the Computer Name tab, and then click Change.
2. Type the new computer name in the Computer name dialog box.
3. Type the new domain or a workgroup in either the Domain dialog box or the Workgroup dialog box.
4. Click More to change the primary Domain Name System (DNS) suffix.
5. Click OK three times, and then restart the computer.

Add a computer description
Type a name or a description in the Computer description box on the Computer Name tab, and then click Apply to add a computer description.

Introduction to the Networking Changes in Windows XP
Windows XP is the first major change in interface since the step from Windows 3.1 (aka Windows for Workgroups) to Windows 95. In some ways it is simpler with many Wizards and more consistent. The support for earlier systems is being rapidly reduced so there are no fixes or patches any more for Windows 95, on sale less than 5 years ago and furthermore XP no longer supports the networking protocols that used to believe to be the most logical and secure choice. Windows 3.1 and Windows 95 used NetBEUI as the prime choice of Network protocol, by Windows 98 IPX/SPX was perhaps the favoured choice although NetBEUI, IPX/SPX and TCP/IP were all loaded by default with any network adapter. Now only TCP/IP is loaded by default, IPX/SPX can installed easily although the name has been subtly changed to put one off and NetBEUI is not offered as an option but can be hunted out from the CD (or via Microsoft Technical Support Articles) at your own risk and without guaranteed ongoing support.

The case against TCP/IP for simple LANs Superficially it may seem a very attractive and logical solution to use TCP/IP for local area networks as well as for Internet access but it has a major flaw – it makes it very easy for a machine to be hacked into from the Internet. The whole philosophy behind the way I set up Networks in Painless Networking I was that of Gibson at the Gibson Research Corporation who produces the definitive Internet Connection Security analysis Software (Shields UP!). The philosophy was basically to totally separate the protocols used for external access to the Internet (TCP/IP) via a DialUp Adapter (Modem or similar) and Local Area Network access via at Network Adapter Card by using NetBUI and/or IPX/SPX and ensuring there were no “bindings” between TCP/IP and any non-essential Internet Services, in particular the “File and Printer Sharing” Services. If that was rigorously enforced then a Firewall was a luxury rather than an essential.

A world without NetBEUI The lack of support for NetBEUI in a Windows XP machine make adding one to an existing Network between Windows 9X machines a bit of a minefield. Running the Network Wizard in Windows XP and using the option to create a floppy disk to run on the other machines, providing they are new enough to run Windows 98, is the Microsoft proposal. If they are older then they are considered unsupported and useless and there are no suggestions on how to proceed.

What you need to do: I do not agree that older and less powerful machines have no role and and have modified the first part of Painless Networks to cover the minor changes to allow easy expansion to Windows XP machines. You should carry them out first. This part covers the changes needed to the default XP configuration to match a typical existing Network. It took me a long time to do it the first time as the XP interface is rather different. I therefore provide step by step notes so hopefully your new shiny XP machine can be got up and running quickly without you having to climb the steep learning curve.

Configuring Windows XP to match an existing Network

1. Disable your firewall and virus checking: Before removing, installing or making significant modifications to anything to do with the Network, you should disable your firewall and virus checking. They may link into TCP/IP and give problems when their links disappear. Most Firewalls and Virus checkers have a flag to say if they should load automatically on startup which should be unticked and the system rebooted. After you have finished they should be re-enabled before you take too many risks.

2. Disable the Internet Connection Firewall: To disable ICF on the Local Area Network (LAN) Connection,
* Open Network Connections,
* Right click LAN Connection at the bottom and click Properties.
The Properties sheet shows the network components associated with the connection.
* Select the Advanced tab, then un-check the “Protect my computer and network by limiting or preventing access to this computer from the Internet” box.
* Windows XP asks you to confirm your decision to disable the firewall – Click OK to disable it.
This step should also be done for the Internet Connections if you intend to use a separate Firewall such as ZoneAlarm.

3. Set up Names: Firstly set up the Computer Name, Workgroup Name and Computer Description – on XP this is via the Network Connections I prefer to
* Go to the Control Panel and to change it to Classic View
* Open Network Connections
* Select LAN Connection at the bottom
* Click Network ID on the Advanced drop down Menu at the top
o Enter a Computer Description
o A unique Computer Name and
o the same Workgroup Name for all machines on the same network

If you are selecting and setting the Name and Workgroup for the first time on a new network it is best to use Upper letters and numbers only and to keep them less than 12 characters for

4. Add the IPX/SPX Protocol: IPX/SPX is fully supported in XP and is my prefered “safe” protocol which is used on networks set up as in Painless Networking. The name is slightly different with NW (for Netware) in the front.
* Click Start, click Control Panel, and then Open Network Connections.
* Right-click the LAN Connection and then click Properties.
* On the General tab, click Install.
* Click Protocol, and then click Add.
* Click NWLink IPX/SPX/NetBIOS Compatible Transport Protocol and click OK.
Two NWLink items are added to the connection’s Properties
* Restart your computer even if not requested and The IPX/SPX protocol should now be installed and working.

5. Set up Bindings: By default, Windows XP binds all installed protocols to each network connection and service. We need to remove various bindings to limit the services using each protocol. The mechanism is very different to Win9X and in XP one should:
* Open the Network Connections folder and on the Advanced drop down menu click Advanced Settings
* Click the connection name under Connections. The appropriate bindings appear under Bindings.
* To remove a binding, un-check the corresponding box. For example, we want to use IPX/SPX instead of TCP/IP for file sharing,so we un-bind TCP/IP from both File and Printer Sharing and Client for Microsoft Networks.
* It is also necessary to right click the LAN Network Connection and click properties then untick the TCP/IP box to completely prevent TCP/IP being used instead of IPX/SPX.
* Restart your computer even if not requested

6. Sharing: The existing network will already have shared folders but you will need to set them up on the XP machine before you will see it over the Network. If you can not see the Sharing Tabs on the Properties of a Folder check File and Printer Sharing is enabled in the LAN configuration

7. Testing: The Configuration should now be complete and you should be able to see the XP machine from the existing network and vice versa in Network Neighborhood/Network Places. One thing to note is that it can take a long time before Network Neighborhood/My Network Places fully updates for new machines and reconfiguration – this is because a Browse Master is automatically selected to retain Network configuration information and organise traffic and that process is not repeated until a change is recognised which can take a while. It took a long time before the XP machine was displaying up to date information although the Network was working fine from the other machines. Turning all the machines off and starting together may help.

8. Security Testing and Firewalls: The use of the IPX/SPX protocol and breaking of all bindings between TCP/IP should now have closed the security holes inherent in the use of TCP/IP over a LAN but it is still wise to check the security both with and without the firewall using the the Shields Up tests at the Gibson Research Corporation.

9. Windows XP Internet Connection Firewall: If you do not have a firewall it may now be possible to (re-)enable the simple built in Firewall on the Dial-up Connection without affecting the LAN – see above for the proceedure. I have not tried as I use ZoneAlarm, the excellent free firewall. If you do so repeat the Shields Up tests at the Gibson Research Corporation.

10. Re-enable Virus checkers: Remember to re-enable any virus checking you earlier disabled once you are sure you have finished making changes.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

Processing your response...

Discuss This Question: 1 &nbspReply

There was an error processing your information. Please try again later.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

Processing your reply...

Ask a Question

Free Guide: Managing storage for virtual environments

Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!

To follow this tag...

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy