Hi
You can try this.
SYMPTOMS
In a Windows 2000 domain environment, you may encounter the following error
message when you try to access a Windows 98 or Windows Millennium network
resource from a Windows 2000-based computer:
\\ComputerName is not accessible. The account is not authorized to log in
from this station.
Note: You can browse the above-mentioned network resources by going to the
IP address, but you cannot browse the resource by using the NetBIOS name.
CAUSE
This behavior occurs because there is an invalid entry that contains the
computer name in the Users and Computers area of Active Directory, which
occurs if you install Windows 2000 onto a client computer, add it to a
Windows 2000 domain, and then later replace the operating system with
either Windows 98, Windows Millennium, or Windows NT.
RESOLUTION
To resolve this behavior, either remove the old entry from Active Directory
or change the computer name of the client computer.
Link:
http://support.microsoft.com/default.aspx?scid=kb;en-us;289547
Also go through the following
----------------------------------------------------------------------------
--
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional
----------------------------------------------------------------------------
---
SYMPTOMS
========
When you attempt to connect to a computer that is running an earlier
operating system (such as Microsoft Windows NT 4.0 or Microsoft Windows 98)
by using a universal naming convention (UNC) path, you may receive the
following error message:
The remote computer is not available.
-or-
System error 53 has occurred. The network path was not found.
This behavior can occur whether you attempt to connect to the UNC path from
within Windows Explorer ("\\<server>\<share>") or from a command prompt
("net use * \\<server>\<share>").
CAUSE
=====
There are two possible causes for this behavior.
1. This behavior can occur if NetBIOS over TCP/IP is disabled. Windows 2000
can use the Server Message Block (SMB) protocol, which is used for file and
printer sharing, directly over TCP without using NetBIOS. Earlier
operating systems do not include this ability; NetBIOS over TCP/IP must be
enabled to communicate with computers that are running such operating
systems.
-or-
2. The error: "The remote computer is not available" can also be caused if
the File and Printer sharing service is not bound to the network card.
RESOLUTION
==========
Resolution for Cause 1 above:
1. Click Start, point to Settings, and then click "Network and Dial-up
Connection".
2. Right-click "Local Area Connection", and then click Properties.
3. Click "Internet Protocol (TCP/IP)", and then click Properties.
4. Click Advanced.
5. Click the WINS tab, and then click "Enable NetBIOS over TCP/IP".
Resolution for Cause 2 above:
1. Click Start, point to Settings, and then click "Network and Dial-up
Connection".
2. On the Advanced menu, click "Advanced Settings".
3. On the "Adapters and Bindings" tab, in the connections list, select the
NIC that the clients use to connect to the server.
4. In the bindings list below, check the option for File and Printer
Sharing for Microsoft networks. Also select the appropriate sub option for
protocol as needed based on what the clients are using. this is commonly
Internet protocol (TCP/IP).
Shilpa Sinha
This posting is provided "AS IS" with no warranties, and confers no rights.
