Re: Trying to network two XP computers - help needed.



zeebop wrote:

(Please advise if there is a more appropriate group for this question)


I have 2 computers that I am trying to connect to eachother.
(They can both connect to the Internet)

The error I get when trying to click through in the microsoft network
browser is:
"\\abc is not accessible. You might not have permission to use this
network resource. Contact the administrator of this server to find out
if you have access permission. The user name could not be found"

Laptop:
Using wireless connection to router
XP Home SP3
Can ping itself, not desktop (timed out)
Can view desktop in 'Microsoft Windows Network browser'

Desktop:
Using wireless connection to router
XP Pro SP3
Can ping itself and laptop
Cannot view laptop in 'Microsfot Windows Network broswer'



I have enabled 'file and print sharing' on both.
Both computers have at least one folder shared.
Both computers can browse their own shares through the network browser
Both computers are running the Microsoft firewall, with file and print
sharing ticked as an exception.
I have tried with the firewall disabled on both PC's and I get the
same result.
Both computers have 'Guest' Account enabled.
I am using simple XP networking.
I have checked that the 'restrictanonymous' value in the registry is 0
I have tried connected in the //name and //ipaddress format, I dont
get any different results than if I browse the network.

Does anyone have any recommendations to get these two talking?

Create matching user accounts and passwords on both machines. Disable Simple
File Sharing on the XP Pro box. See below.

For XP, start by running the Network Setup Wizard on all machines (see
caveat in Item A below).

Problems sharing files between computers on a network are generally caused
by 1) a misconfigured firewall or overlooked firewall (including a stateful
firewall in a VPN); 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.

A. 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. DO
NOT TURN OFF FIREWALLS; CONFIGURE THEM CORRECTLY.

B. For ease of organization, put all computers in the same Workgroup. This
is done from the System applet in Control Panel, Computer Name tab.

C. Create matching user accounts and passwords on all machines. You do not
need to be logged into the same account on all machines and the passwords
assigned to each user account can be different; the accounts/passwords just
need to exist and match on all machines. DO NOT NEGLECT TO CREATE
PASSWORDS, EVEN IF ONLY SIMPLE ONES. 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

D. If one or more of the computers is XP Pro or Media Center, turn off
Simple File Sharing (Folder Options>View tab).

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
FAQ - http://www.elephantboycomputers.com/#FAQ

.



Relevant Pages

  • Re: No computer find from workgroup
    ... ping and find from the search network computer function. ... start by running the Network Setup Wizard on all machines (see ... Problems sharing files between computers on a network are generally caused ... by 1) a misconfigured firewall or overlooked firewall (including a stateful ...
    (microsoft.public.windowsxp.general)
  • Re: Sharing one printer with two Vista desktop
    ... If the printer is not a network printer (connected to one of the computers ... install the printer on both machines. ... by 1) a misconfigured firewall or overlooked firewall (including a stateful ...
    (microsoft.public.windows.vista.print_fax_scan)
  • Re: Simple Printer Sharing/Networking Question
    ... And all 3 desktop computers are running Windows XP Pro ... We have turned on sharing for the network printers (in association with this ... caused by 1) a misconfigured firewall or overlooked firewall (including ...
    (microsoft.public.windowsxp.network_web)
  • Re: Sharing a printer
    ... Here are general network troubleshooting steps. ... start by running the Network Setup Wizard on all machines (see ... a misconfigured firewall or overlooked firewall (including a stateful ... put all computers in the same Workgroup. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Sharing a printer
    ... Here are general network troubleshooting steps. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked 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. ... On the assumption that you in fact do have a router that connects to the Internet and that your computers then connect to the router, then if you think that you have one IP for multiple computers then you probably are using a website tool such as http://whatismyip.com/ That shows the your public IP address -- the one that the rest of the world sees. ...
    (microsoft.public.windowsxp.network_web)