Re: Mapping to WIndows XP from 2000
From: shino (anonymous_at_discussions.microsoft.com)
Date: 09/17/04
- Next message: ziegel: "Re: Windows Explorer too slow when computer is connected to network"
- Previous message: Robert L [MS-MVP]: "Re: Concurrent Network Connections, Wired and Wireless"
- In reply to: Chuck: "Re: Mapping to WIndows XP from 2000"
- Next in thread: Chuck: "Re: Mapping to WIndows XP from 2000"
- Reply: Chuck: "Re: Mapping to WIndows XP from 2000"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 17 Sep 2004 08:53:51 -0700
Hi, I am having a similar problem with above person
between my win2k LAN and newly adding xp. I reviewed
Chuck's and his suggestion was very helpful, but not
having solved the problem yet.
What if, I can't ping myself(xp home) using both name and
ip but can ping others using ip but names, what is going
on?
3win2k LAN works fine, adding xp home, xp icon appears on
my existing workgroups in w2k workstations but not
accecible as "network path not found".
>From xp home, none of win2k can appear, even the workgroup
icon.
I set up win2k LAN by myself, so I was not expected this
was going to be taking time a lot...
Would someone help, please
shino
>-----Original Message-----
>On Thu, 16 Sep 2004 22:09:12 -0700, "Windows 2000 Mapping
problem" <Windows 2000
>Mapping problem@discussions.microsoft.com> wrote:
>
>>Hi all,
>>No matter how i try i simply cannot get my windows 2000
server to map to a
>>windows xp workstation. As a side note i can get the
windows xp workstation
>>to map to the windows 2000 server. Can anyone point me
in the right
>>direction or have any relevant information
>>Best regards
>
>Some more detail would be very helpful here. Maybe the
error message /
>condition you're seeing when you "cannot get my windows
2000 server to map to a
>windows xp workstation"? Maybe what version of Windows
XP (Home / Pro)? Maybe
>the service pack level on each computer?
>
>Without any of that, I'll give you the most common
problems to look for.
>
>Do you have connectivity between the two computers?
>>From each computer, test connectivity:
>1) Ping itself by name.
>2) Ping itself by ip address.
>3) Ping the other by name.
>4) Ping the other by ip address.
>5) Ping 127.0.0.1.
>Report success / exact error displayed in each test (10
tests total).
>
>Are you running both Client for Microsoft Networks, and
File and Printer Sharing
>for Microsoft Networks (Local Area Connection -
Properties), on each computer?
>Do you have shares setup on each?
>
>Are you running NetBIOS Over TCP/IP (Local Area
Connection - Properties - TCP/IP
>- Properties - Advanced - WINS) on each computer?
>
>Make sure the browser service is running on each
computer. Control Panel -
>Administrative Tools - Services. Verify that the
Computer Browser, and the
>TCP/IP NetBIOS Helper, services both show with Status =
Started.
>
>On any XP Pro computer, check to see if Simple File
Sharing (Control Panel -
>Folder Options - View - Advanced settings) is enabled or
disabled. With XP Pro,
>you need to have SFS properly set on each computer.
>
>With XP Pro, if SFS is disabled, check the Local Security
Policy (Control Panel
>- Administrative Tools). Under Local Policies - Security
Options, look at
>"Network access: Sharing and security model", and ensure
it's set to "Classic -
>local users authenticate as themselves".
>
>With XP Pro, if you set the above Local Security Policy
to "Guest only", enable
>the Guest account, thru Local User Manager (Start - Run -
"lusrmgr.msc"). If
>"Classic", setup and use a common non-Guest account on
all computers. Whichever
>account is used, give it an identical, non-blank password
on all computers.
>
>For XP Home, OR for XP Pro with Simple File Sharing
enabled, make sure that the
>Guest account is enabled, on each computer. For XP Pro,
enable Guest using
>Local User Manager (Start - Run - "lusrmgr.msc"); for XP
Home, Start - Run -
>"cmd" - type "net user guest /active:yes" in the command
window.
>
>Do any of the computers have a software firewall (ICF /
WF, or third party)? If
>so, you need to configure them for file sharing, by
opening ports TCP 139, 445
>and UDP 137, 138, 445, by enabling the File and Printer
Sharing exception, and /
>or by identifying the other computers as present in the
Local (Trusted) zone.
>Firewall configurations are a very common cause of
(network) browser, and file
>sharing, problems.
>
>Cheers,
>Chuck
>Paranoia comes from experience - and is not necessarily a
bad thing.
>.
- Next message: ziegel: "Re: Windows Explorer too slow when computer is connected to network"
- Previous message: Robert L [MS-MVP]: "Re: Concurrent Network Connections, Wired and Wireless"
- In reply to: Chuck: "Re: Mapping to WIndows XP from 2000"
- Next in thread: Chuck: "Re: Mapping to WIndows XP from 2000"
- Reply: Chuck: "Re: Mapping to WIndows XP from 2000"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|