Mapping to WIndows XP from 2000

[Guest]

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

 

[Chuck]

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.

 

[shino]

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-----


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

 

[Chuck]

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,

You ask a very interesting question, specifically your pinging.

If I interpret your statement correctly, you can ping only other computers, and
only by ip address? You can't ping your own ip address or name?

Will you please analyse your problem with this set of tests, and provide test
results precisely as follows:
Between this computer and one other, 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).

Please start a new discussion thread for this problem. Use a more descriptive
Subject, say "Connectivity between Win2000 and WinXP". Post under the exact
same name "shino" so I can find your new post. This will be to everybody's
benefit.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Guest]

Hi, my problem is very similar but I don´t seem to be able to solve it.

I´m networking a XP home with a W2000 Professional. The XP home CAN see the
shared files on the 2000, but the W2000 CAN NOT see the shared files on the
XP.

In w2000 I go to Network Neighbourhood and I can see the XP home computer,
when I double click on it, instead of appering a logon screen all I get is an
error box (in Spanish) that says something like "Unreachable \\X.X.X.X Start
up session error: the user has not been asigned this kind of start up"

I´m guessing that the problem is with the security policies but I´ve got no
access to secpol on XP home.

Any suggestions?

 

[Chuck]

Hi, my problem is very similar but I don´t seem to be able to solve it.

I´m networking a XP home with a W2000 Professional. The XP home CAN see the
shared files on the 2000, but the W2000 CAN NOT see the shared files on the
XP.

In w2000 I go to Network Neighbourhood and I can see the XP home computer,
when I double click on it, instead of appering a logon screen all I get is an
error box (in Spanish) that says something like "Unreachable \\X.X.X.X Start
up session error: the user has not been asigned this kind of start up"

I´m guessing that the problem is with the security policies but I´ve got no
access to secpol on XP home.

Any suggestions?

Networking with XP Home is pretty simple - when it works. Which means the Guest
account has to be enabled, with no firewalls interfering. That's your security
policy. :-{

Enable the Guest account, using Start - Run - "cmd" - type "net user guest
/active:yes" in the command window, on the XP Home computer.

What error number do you get with the error message? Could be a name resolution
problem.

Please provide ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post.

Please provide net view for each computer.
Start - Run - "cmd". Type "net view >c:\netview.txt" into the command window -
Open c:\netview.txt in Notepad, copy and paste into your next post.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Guest]

BTW, I did the test you suggested

From W2000 I can ping the XP by IP address but CAN NOT ping the XP Home
machine by Name.

 

[Chuck]

BTW, I did the test you suggested

From W2000 I can ping the XP by IP address but CAN NOT ping the XP Home
machine by Name.

It's a name resolution problem.

Please provide ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post.

Please provide net view for each computer.
Start - Run - "cmd". Type "net view >c:\netview.txt" into the command window -
Open c:\netview.txt in Notepad, copy and paste into your next post.

What SP level on the XP computer?

Any firewall (now or in the past) on either?

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Guest]

XP Home SP1 Machine:
-----------------------------------
Configuración IP de Windows

Nombre del host . . . . . . . . . : Alejandra
Sufijo DNS principal . . . . . . :
Tipo de nodo. . . . . . . . . . . : híbrido
Enrutamiento IP habilitado. . . . : Sí
Proxy WINS habilitado. . . . . : No

Adaptador Ethernet Conexión de área local :

Estado de los medios. . . .: medios desconectados
Descripción. . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet NIC
Dirección física. . . . . . . . . : 00-0E-0E-0E-2D-B2

Adaptador Ethernet Conexiones de red inalámbricas :

Sufijo de conexión específica DNS :
Descripción. . . . . . . . . . . : Accton WN4201B(EU) 802.11g
Wireless PCI Card
Dirección física. . . . . . . . . : 00-0E-0E-C0-94-73
DHCP habilitado. . . . . . . . . : No
Dirección IP. . . . . . . . . . . : 192.168.0.1
Máscara de subred . . . . . . . . : 255.255.255.0
Puerta de enlace predeterminada :

Adaptador PPP Conexión Arrakis ADSL :

Sufijo de conexión específica DNS :
Descripción. . . . . . . . . . . : WAN (PPP/SLIP) Interface
Dirección física. . . . . . . . . : 00-53-45-0E-0E-00
DHCP habilitado. . . . . . . . . : No
Dirección IP. . . . . . . . . . . : 213.9.250.238
Máscara de subred . . . . . . . . : 255.255.255.255
Puerta de enlace predeterminada : 213.9.250.238
Servidores DNS . . . . . . . . . .: 195.5.64.2
195.5.64.6

W2000Pro IPCONFIG
-------------------------
Configuraci¢n IP de Windows 2000

Nombre del host . . . . . . . . . . . : salon
Sufijo DNS principal . . . . . . . . :
Tipo de nodo. . . . . . . . . . . . . : Mezclado
Enrutamiento de IP habilitado . . . . : S¡
Proxy de WINS habilitado. . . . . . . : No

Ethernet adaptador Conexi¢n de rea local 3:

Sufijo DNS espec¡fico de la conexi¢n. :
Descripci¢n . . . . . . . . . . . . . : Conceptronic 54g Wireless PC-Card
Direcci¢n f¡sica. . . . . . . . . . . : 00-0E-0E-22-70-82
DHCP habilitado . . . . . . . . . . . : No
Direcci¢n IP. . . . . . . . . . . . . : 192.168.0.2
M scara de subred . . . . . . . . . . : 255.255.255.0
Puerta de enlace predeterminada . . . : 192.168.0.1
Servidores DNS. . . . . . . . . . . . : 192.168.0.1

Ethernet adaptador {3E468CE1-3241-48FE-8EA1-59DEA4D46DF0}:

Sufijo DNS espec¡fico de la conexi¢n. :
Descripci¢n . . . . . . . . . . . . . : NOC Extranet Access Adapter
Direcci¢n f¡sica. . . . . . . . . . . : 44-0E-0E-54-42-00
DHCP habilitado . . . . . . . . . . . : No
Direcci¢n IP. . . . . . . . . . . . . : 0.0.0.0
M scara de subred . . . . . . . . . . : 0.0.0.0
Puerta de enlace predeterminada . . . :
Servidores DNS. . . . . . . . . . . . :

Ethernet adaptador Conexi¢n de rea local:

Estado de los medios. . . . . . . . . : cable desconectado
Descripci¢n . . . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
Adapter (10/100)
Direcci¢n f¡sica. . . . . . . . . . . : 00-00-0E-0E-0E-D2

XP Net View
------------------
Servidor Descripci¢n

-------------------------------------------------------------------------------
\\ALEJANDRA Habitacion

\\SALON



W2000 Net View
----------------------
Servidor Descripci¢n

-------------------------------------------------------------------------------
\\ALEJANDRA Habitacion

\\SALON


Firewalls
--------------
On XP --> Panda Firewall
On W2000 --> BlackIce Firewall

I´ve resolver the ping by name problem leaving blank the DNS address on the
w2000 machine. Neverteheless I still can not access the files on the XP
machine, I CAN see the machine but when double clicking on it instead of a
Login Window I guet an error message "You can not have access to \\X.X.X.X
the user has not bee given the right privileges to it" (I´m translating from
Spanish).

Thanks a lot!!

 

[Chuck]

On Fri, 22 Oct 2004 06:27:05 -0700, "Toreador"

XP Net View
------------------
Servidor Descripci¢n

-------------------------------------------------------------------------------
\\ALEJANDRA Habitacion

\\SALON



W2000 Net View
----------------------
Servidor Descripci¢n

-------------------------------------------------------------------------------
\\ALEJANDRA Habitacion

\\SALON


Firewalls
--------------
On XP --> Panda Firewall
On W2000 --> BlackIce Firewall

I´ve resolver the ping by name problem leaving blank the DNS address on the
w2000 machine. Neverteheless I still can not access the files on the XP
machine, I CAN see the machine but when double clicking on it instead of a
Login Window I guet an error message "You can not have access to \\X.X.X.X
the user has not bee given the right privileges to it" (I´m translating from
Spanish).

Thanks a lot!!

Node Types are Hybrid (Alejandra) and Mixed (Salon). No problem there.

For my money, the problem is the Panda firewall. If you have Alejandra behind a
Panda firewall, you're going to have to either configure the firewall to allow
file sharing access from Salon, or un install Panda.

I would like to help you out by retrieving the Panda firewall manual, and
finding out how to configure the firewall, but the manual is not available
online. So you're going to have to read the manual on your own, or un install
Panda.

What SP level is Alejandra on? If SP2, you can protect it temporarily - the SP2
(Windows Firewall) firewall is better than nothing. The SP0/1 firewall (ICF)
not so much protection at all.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Guest]

Thanks, but uninstalling Panda or both firewalls didn´t work.

Its always the same message "The user has not been granted this kind of
session startup", I wish I could at least get the login screen.

BTW, I´m running XP Home SP1

I wonder if the problems is related to the security policies on the XP
machine (shame I´ve got no access to SECPOL on XP Home).

Thanks for all your help

 

[Chuck]

Thanks, but uninstalling Panda or both firewalls didn´t work.

Its always the same message "The user has not been granted this kind of
session startup", I wish I could at least get the login screen.

BTW, I´m running XP Home SP1

I wonder if the problems is related to the security policies on the XP
machine (shame I´ve got no access to SECPOL on XP Home).

Thanks for all your help

From both Alejandra and Salon, try Start - Run:
"\\192.168.0.1"
"\\192.168.0.2"

Then from both again, Start - Run - "cmd" - in the command window:
"net view 192.168.0.1"
"net view 192.168.0.2"

Local security policies are always a possibility - they can be used to affect
the behaviour of the various users and groups, far beyond the "net user ..."
command, and beyond settings in the XP Pro Local User Manager.

But, if XP Home doesn't have a Policy Manager, and if we can't find where in the
registry the policies are stored (and this has been discussed before in previous
threads), you may be wasting your time.

What happens if you boot into Safe Mode, and login as the Administrator? I've
heard you can disable Simple File Sharing in XP Home - can you run lusrmgr or
secpol too?
http://support.microsoft.com/?id=315222

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Guest]

Chuck, thanks for all your help.

With Net View from the XP machine I get a list of the files/printers ...
being shared on both computers.
With Net View from the W2000 machine I can not get a list of the
files/printes ... being shared on the XP machine. Instead I get the error
message "System Error 5. Access denied".

System Error 5 ... thats the problem!! how can it be solved?

 

[Chuck]

Chuck, thanks for all your help.

With Net View from the XP machine I get a list of the files/printers ...
being shared on both computers.
With Net View from the W2000 machine I can not get a list of the
files/printes ... being shared on the XP machine. Instead I get the error
message "System Error 5. Access denied".

System Error 5 ... thats the problem!! how can it be solved?

Access denied - inadequate permissions.

You can't edit security policies in XP Home. Let's check the registry.

Take a look at look at registry key [HKLM\System\CurrentControlSet\Control\Lsa],
value restrictanonymous.
<http://www.microsoft.com/windows200...2000/techinfo/reskit/en-us/regentry/46688.asp>
<http://www.jsifaq.com/subf/tip2600/rh2625.htm>

The above articles refer to Windows 2000. Remember WinXP is NT V5.1, and Win2K
is NT V5.0.

Have you used the Registry Editor before? If not, it's a scary tool, but it's
pretty simple once you get used to it. Here are a couple articles that might
help:
<http://www.microsoft.com/windowsxp/...home/using/productdoc/en/tools_regeditors.asp>
<http://www.annoyances.org/exec/show/registry>

Just remember to backup the key (create a registry patch) for
[HKLM\System\CurrentControlSet\Control\Lsa] before making any changes, if
appropriate.

From the Annoyances article:
You can create a Registry patch by opening the Registry Editor, selecting a
branch, and choosing Export from the File menu. Then, specify a filename, and
press OK. You can then view the Registry patch file by opening it in Notepad
(right-click on it and select Edit). Again, just double-click on a Registry
patch file (or use Import in the Registry Editor's File menu) to apply it to the
registry.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.