Re: Network - WinXP and WinXP x64

Nevermind, I finally figured it out. For some reason, on the x64 machine, if
the Windows Firewall/Internet Connection Sharing service is disabled, shares
will not be accessible. However, that same setting on the x32 machine didn't
affect whether or not the shares could be accessed. Very strange. I went
through the network troubleshooter you posted in another post regarding this
topic, and that answered the problem I was having. Thanks, that was a great
resource actually.

"AFGuy012799" wrote:

"Malke" wrote:


Your file/printer sharing problems have nothing to do with WinXP
32-bit/WinXP 64-bit. You've got something set up wrong. Go through these
general networking steps systematically to narrow down the culprit.
Since you didn't say whether you have a domain or not, I'm assuming you
don't. If you have a domain, some of the following information will
apply but you need to come back with more information about your server.

Problems sharing files between computers on a network are generally
caused by 1) a misconfigured firewall; or 2) inadvertently running two
firewalls such as the built-in Windows Firewall and a third-party
firewall; and/or 3) not having identical user accounts and passwords on
all Workgroup machines; 4) trying to create shares where the operating
system does not permit it.

Here are some general networking tips for home/small networks:

1. Configure firewalls on all machines to allow the Local Area Network
(LAN) traffic as trusted. With Windows Firewall, this means allowing
File/Printer Sharing on the Exceptions tab. Normally running the Network
Setup Wizard on XP will take care of this for those machines.The only
"gotcha" is that this will turn on the XPSP2 Windows Firewall. If you
aren't running a third-party firewall or have an antivirus with
"Internet Worm Protection" (like Norton 2006/07) which acts as a
firewall, then you're fine. With third-party firewalls, I usually
configure the LAN allowance with an IP range. Ex. would be
192.168.1.0-192.168.1.254. Obviously you would substitute your correct
subnet. Do not run more than one firewall.

2. With earlier Microsoft operating systems, the name of the Workgroup
didn't matter. Apparently it does with Vista, so put all computers in
the same Workgroup. This is done from the System applet in Control
Panel, Computer Name tab. Even if you don't have Vista, it is more
consistent to have everything the same.

3. Create identical user accounts and passwords on all machines. If you
wish a machine to boot directly to the Desktop (into one particular
user's account) for convenience, you can do this. The instructions at
this link work for both XP and Vista:

Configure Windows to Automatically Login (MVP Ramesh) -
http://windowsxp.mvps.org/Autologon.htm

4. If one or more of the computers is XP Pro or Media Center:

a. If you need Pro's ability to set fine-grained permissions, turn off
Simple File Sharing (Folder Options>View tab) and create identical user
accounts/passwords on all computers.

b. If you don't care about using Pro's advanced features, leave the
Simple File Sharing enabled.

Simple File Sharing means that Guest (network) is enabled. This means
that anyone without a user account on the target system can use its
resources. This is a security hole but only you can decide if it matters
in your situation.

5. Create shares as desired. XP Home does not permit sharing of users'
home directories (My Documents) or Program Files, but you can share
folders inside those directories. A better choice is to simply use the
Shared Documents folder.


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User


I don't think he has something set up wrong, as I have the exact same
problem, and I have nothing different on either of my systems, and also have
previously set up my systems with the tips provided before I searched here,
and again when I read your post just to make sure I wasn't missing a step. My
x64 machine can access my x32 machine, but not vice versa. My x64 machine
will show up in the network places explorer window, but when I click on it to
try and access the shares I made, it tells me that it is inaccessible. I know
that XP x64 sets some auto-administrative shares, of which the permissions
cannot be changed, or even viewed. I don't know if these auto-shares are
overriding any other shares made or not though. I can see the shares within
the x64 system, just not on the network. I have seen this question posted
over at PlanetAMD64 as well, so I have a feeling that all of us can't be
setting up something wrong.

.

Relevant Pages

  • Re: Almost got it - just a little wireless help please
    ... I also have Simple File Sharing ... The firewall is a bit iffy though. ... with Windows Firewall: ... Elephant Boy Computers ...
    (microsoft.public.windowsxp.network_web)
  • Re: Sharing program files folder
    ... Simple Sharing from Folder Options>View. ... This is most commonly caused by a misconfigured firewall. ... the Windows Firewall is probably on. ... firewall properly to allow the Local Area Network traffic as trusted. ...
    (microsoft.public.windowsxp.general)
  • Re: XP SP2 Inbound Connections
    ... >shares on the Win2k3 machine but the Win2k3 machine cannot ping the XP ... >SP2 firewall and stopped the firewall service. ... If you don't want to use Windows Firewall, ...
    (microsoft.public.windowsxp.network_web)
  • Re: New install, cant get file sharing to work.
    ... I've got Windows Firewall disabled, ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.network_web)
  • RE: Userenv 1030 error on member server
    ... Thanks a lot for your great information sharing! ... Microsoft CSS Online Newsgroup Support ... Windows Firewall showing that LSASS.EXE was trying to open a port and was ...
    (microsoft.public.windows.server.sbs)