Re: new computer w/ XP Pro not avalible on network

Tech-Archive recommends: Fix windows errors by optimizing your registry



Malke,
Thank you very much. We will read trough the links. Yesterday, we shut all
of the firewall and internet security features off on XP Pro and Norton
Internet Security. Then we created a new Workgroup on the XP Pro machine.
We switched the XP Home machines to the new Workgroup. One of these steps
made it so that we could access all three machines and share files and
printers. I'm not sure what step did the trick. Now we have the firewall
setting turned "On" in the XP Pro machine and we are able to file and printer
share.
Thank you,
John

"Malke" wrote:

> john wrote:
>
> > We just purchased a new Dell computer that came with XP Pro. Our
> > other two computers running XP Home are conected on to each other and
> > the internet via a Linksys router. Those two computer can see each
> > other, share files and access the internet just fine.
> > We plugged the new computer with XP Pro into the router and went about
> > setting it up on the network. The new computer can access the
> > internet but
> > cannot access ether of the two other existing computers. We have all
> > three computers in the same workgroup.
> > We can see the new computer from the other computers but we cannot get
> > into
> > the new computer's shared folders. We've shut off the firewall on the
> > new computer.
> > If we try to view the other computers I think that there must be some
> > setting to allow other computers to see into the XP Pro computer's
> > shared folders.
> > If I go to the workgroup from that but for now we are get an error
> > message that reads
>
> XP Home only has Simple Sharing available. Check in your Folder
> Options>View settings on the Pro box to see if Simple Sharing is
> checked. If it isn't, try checking it. I'll give you links with more
> details. Another thing that makes networking easy is to create user
> accounts/passwords on the XP Pro box identical to those on the XP Home
> machines. Here are links to help you:
>
> http://www.practicallynetworked.com/sharing/xp/filesharing.htm (Home)
> http://www.practicallynetworked.com/sharing/xp_filesharing/index.htm
> (Pro)
> http://www.practicallynetworked.com/howto/
> http://www.practicallynetworked.com/sharing/xp/addxp.htm - Adding XP to
> an existing network
> http://www.bcmaven.com/networking/faq.htm
> http://www.bcmaven.com/networking/myths.htm
>
> Malke
> --
> MS MVP - Windows Shell/User
> www.elephantboycomputers.com
> In Memoriam - MVP Alex Nichol
> The world is diminished without him.
>
.



Relevant Pages

  • Re: XP network 2 computers - can not sign on
    ... ok - i will check the firewall thing ... but we use Nortons internet security on both machines w ... > very common cause of browser, and file sharing, problems. ... > On any XP Pro computer, check to see if Simple File Sharing (Control Panel - ...
    (microsoft.public.windowsxp.network_web)
  • Re: Reversing an action in XP Home
    ... | While running WS_FTP Pro for the first time, ... by clicking no when it (your firewall) asked for permission to grant WS_FTP ... Internet access. ... Firewall" and click "Internet Applications" where I can adjust the rules for ...
    (microsoft.public.windowsxp.basics)
  • Re: Network Path Not Found
    ... XP Pro, Comp A 32bit, Comp B 64 bit. ... What flavor are the XP machines, ... Check your firewall settings to make sure the IP of the machine is ...
    (microsoft.public.windowsxp.general)
  • Re: Suspicious 137, 138 Traffic to Broadcast address and Default Gateway.
    ... > this is Internet traffic or local traffic. ... this is internal network traffic (172.20.x.x is reserved for internal ... > the fields on your firewall logs, nor do you bother to tell us what IP ... (firewall's internal Interface AKA default gateway for XP Pro) ...
    (microsoft.public.security)
  • Re: cant ping between 2 local computers
    ... The other is an XP Pro. ... The DHCP server for the XP Pro box is the firewall on ... the machines are on the same switch anyway. ... neither one can ping the other. ...
    (microsoft.public.win2000.networking)