[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 257
  • Last Modified:

Windows XP Networking

I have two computers connected to the Internet through a hub.  One is running Windows XP Professional and one is running Windows XP Home. I am trying to network the two computers.  From my XP Professional, I can see the XP Home and the XP Professional in the Workgroup.  When I tried to log on to the XP Home from XP Professional, I get a box requesting a password.  Since there seems to be no Group Policy in XP Home, how do I disable password requirements for a guest account?
0
jay_jenks
Asked:
jay_jenks
  • 3
  • 2
2 Solutions
 
CrazyOneCommented:
Try this

Start > Settings > Control Panel > Users Account
Click on the Quest accoung and see if there are any password settings.
If so choose the Remove the Password option
0
 
CrazyOneCommented:
Do this from the Home installation
0
 
CrazyOneCommented:
Also why not set up an account rather then using the guest account. You will need to set up the account on both machines and configure them with or with out a password
0
 
pjimersonCommented:
I can understand wanting to remove the requirement for a password but you cannot connect to a windows 2000 or xp machine without providing some sort of authentication paramaters.

Here's what I do to sort of prime the pump:  

Create profiles on all the machines you want to network that are exactly the same.  That is, you should use the same logins and passwords on all machines.  What this does is allow you to connect to a network share without having to provide a login or password to do it.  If you don't specify a login and password when you connect to a network resource, windows automatically provides the login and password that you entered when you logged in to Windows.   Since all machines your connecting to have identical profiles created on them, then the login and password you specified on one should also work on all the others.  

It's kind of a sloppy way to do it but it works.  The reason it's sloppy is because windows doesn't just provide the username and password when logging in.  A profile is uniquely identified by the Username and the Domain.  So, when you logged in to Computer 1 you identified yourself as <Username> at Computer 1.  When you connect to a network resource on another machine you are no doubt identifying youself as <Username> at Computer 1 but this should not be a valid login on Computer 2 ..... Computer 2 should admit you only as <Username> on Computer 2.  I expect that Microsoft didn't want to have to teach people how to connect to a network share using a profile on the remote machine.  In any case it works and not only for XP but also for Windows 2000, Win98, etc......

Note:  One thing you may need to do first is to go into Control Panel, click on Users and Passwords and specify that a username and password are necessary to use that computer.  If you don't then you'll need to figure out what authentication parameters windows uses by default then make sure those same parameters are valid on all other machines.  

Good Luck,
pjimerson


Note:  
0
 
pjimersonCommented:
Oh,  one other thing that helps:

put a batch file in your start menu's startup folder with two net view commands for each machine that you want that machine to be able to see in Network Neighborhood/My Network Places.  The commands should look like this:

net view \\<IP address>        for example    Net View \\192.168.1.1
net view \\<dns name           for example     Net View \\Computer1

This will help you see  the other machines on your network.  MS recommends running the net view commands each session to enable you to see cross platform machines, that is to enable 98 machines to see Win2k or WinXP machines in network neighborhood and vice versa.

Good Luck,

pjimerson
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now