|
#1
|
|||
|
|||
|
I am removing the Master Computer that set up the original network.
Before doing so, I want to set up the new network on my replacement computer to connect to my laptop. These are NOT wireless connections. How do I remove "MSHOME" network from the original computer? AGAIN - I want to set the new network up FIRST before shutting down the old computer completely |
|
#2
|
|||
|
|||
|
MSHOME isn't a network as such, it's just a default workgroup name.
Replacing a server would involve firstly examining exactly what services that server provides. There is no stock answer to this, if I was called-in to replace a server (that I hadn't installed myself) I would be inclined to spend some time making sure I understood exactly what role the server was playing, and what the requirements for its replacement were. The steps required would also depend on wheter the server in-question is an Active Directory controller, or not. If the workgroup is MSHOME that tends to suggest XP Home, though, in which case the network probably isn't domain-based. You can add a new server computer, provided it has a different name and IP address from the existing one. Quite often this is a preferable approach as it allows a more graceful hand-over from one to the other once all files have been transferred. |
|
#3
|
|||
|
|||
|
Great response Ian!
You actually hit upon a clarification I should have made up front last evening. Shows what happens when you are frustrated at 11:00 pm with computer stuff. Actually, what I'd like to do is remove the MSHOME workgroup from the original PC that set up the workgroup, and set up a new one on the replacement PC. The Old Computer is running XP Pro, but not using any of the added networking features. The New Computer is running XP Home, but will probably be upgraded to XP Pro once the old computer is out of commission. That being said, how do I decomission the MSHOME workgroup and so I can set up the new workgroup cleanly on the new computer? Thanks much! Jay "Ian" wrote: > MSHOME isn't a network as such, it's just a default workgroup name. > > Replacing a server would involve firstly examining exactly what services > that server provides. There is no stock answer to this, if I was called-in to > replace a server (that I hadn't installed myself) I would be inclined to > spend some time making sure I understood exactly what role the server was > playing, and what the requirements for its replacement were. > > The steps required would also depend on wheter the server in-question is an > Active Directory controller, or not. If the workgroup is MSHOME that tends > to suggest XP Home, though, in which case the network probably isn't > domain-based. > > You can add a new server computer, provided it has a different name and IP > address from the existing one. Quite often this is a preferable approach as > it allows a more graceful hand-over from one to the other once all files have > been transferred. > > |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Re: XPSP2 domain firewall settings | Anthony Yates | Windows XP Security Admin | 1 | 01-05-2006 04:16 AM |
| Last windows update broke my home network (file and print sharing) | Ryan M | Windows XP Network Web | 3 | 01-05-2006 04:11 AM |
| Help - Home Network Security | Orville Noah | Windows XP Network Web | 6 | 01-05-2006 04:05 AM |
| XP home network and user privlages | Brad n Mich | Windows XP Network Web | 5 | 01-05-2006 04:04 AM |
| Re: Home network problem | Patrick Murray | Windows XP General | 0 | 01-05-2006 02:32 AM |