Winxp Pro unable to connect to nt4 server

[drummerguy]

I just took over this job that requires me to maintain a NT/98/x
network. I have the book knowledge, just no hands on! So...here is m
problem.

We have a Dlink wireless router and 2 laptops running XP pro. The res
of of the workstations are win 98. I am able to get access to th
workgroup no problem, but when I try to get access to the domain, i ge
an error " a domain controller for the domain SAOG coun not b
contacted. Ensure that the domain name is typed correctly. If the nam
is correct, click details for troubleshooting info."

I tried the troubleshooting stuff there, and when i do the NSLOOKU
command i get this message:
***Can't find server name for address 192.168.0.1: Non-Existant domain
***Default servers are not available
Default server: UnKnown
Address: 192.168.0.1

Now i believe that is the address of the router, and it is doing th
DHCP. It seems i need to access the server for the DHCP settings, but
do not know what to do with XP. I have no probs setting up the win9
machines, I did that in tech school.

So...what next!!

Thanx
Case
-
drummergu

 

[Robert L [MS-MVP]]

quoted from http://www.ChicagoTech.net
.... is not accessible

Message: "....is not accessible. You may not have permission to use this
network resource. Contact the administrator of this server to find out if
you have access permissions. Network path was not found."

Resolutions:
1) make sure no any firewall running.
2) make sure you have created the same workgroup, and the same username on
w2k/xp for logging on a remote computer.
3) check user's rights.
4) you may want to enable guest account on w2k/xp.
5) if you are using simple file sharing, you may try to disable it and
re-share the drive manually.
6) if it is mixed OS (win98, NT, ME and W2K/XP) network, enable NetBIOS over
TCP/IP.
7) make sure the Computer Browser service is started if all computers are
w2k/xp.
8) stop Computer Browser service on win9x, ME and NT if this is a mixed OS
network.
9) cache credential by using net use \\computername\share /user:username
command (it is better to have the username logon shared computer).
10) if you have tried enabling netbios over tcp/ip but doesn't work, you may
try to load netbeui (loading netbeui may slow your network).
11) Make sure the server service is running.
12) If you can see the share in Network Neighborhood but not access it, this
issue may be resolved by verifying that both the share permissions and the
NTFS partition permissions are correctly configured for individual user or
group access.



--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

 

[drummerguy]

Well...I figured it out! Happened across the network protocol list o
the server and noticed it had every protocol installed. So I Went ou
on a limb and tried installing some protocols. When I put NWLink on m
XP machines, they saw the server and got authentication just fine!

Live and learn, I dont know why NWLink took priority over TCP/IP, bu
it did, and would not allow authentication through TCP/IP.

Thanx for the info!
Case
-
drummergu