If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
workgroup is not accessible???
This is driving me crazy ... I just upgraded my Win2K system to XP Pro
(almost exclusively so I can get remote desktop). When I was using Win2K, I had a small workgroup setup and working fine. Now that I have XP installed, I am getting the error "workgroup is not accessible ...". I have Netbios over TCP/IP enabled, the builtin firewall is disabled, no other firewalling software is installed, and the workgroup worked fine before. I have reviewed the MS kb article http://support.microsoft.com/?kbid=318030, but nothing there seems to apply. My network consists of my XP pro system, my wife's Win2K system, and a linux system running Samba. All in the same workgroup. I AM able to map drives directly to other systems and access them via a share. I just can't browse the workgroup. Any suggestions on a next step for troubleshooting? Thanks! |
Ads |
#2
|
|||
|
|||
workgroup is not accessible???
quoted from http://www.ChicagoTech.net
System Error 1240 - The account is not authorized to login from this station. Symptoms: 1. You may get the system error 1240 when using net view \\remotecomputer' 2. "Workgroup_name is not accessible. Account is Not Authorized to Log In to this Station" when attempting to browse the workgroup from a networking computer. Resolutions: 1. Use Regedit to enable unencrypted (plain text) passwords for the SMB client. 2. Enable Send Unencrypted Password to Connect to 3rd Party SMB Servers under Local Security Policy. 3. Set the following policies as showing: Digitally sign client communications (always) - disabled Digitally sign server communications (always)- disabled Digitally sign server communications (when possible) - disabled LAN Manager Authentication Level set to Send LM and NTLM - use NTLMv2 session security if negotiated - (default) send LM & NTLM responses Secure channel: Digitally encrypt or sign secure channel data (always) - disabled Secure channel: Require strong (Windows 2000 or later) session key - disabled 4. Contact the third-party SMB server manufacturer if you have a third-party SMB server, such as DEC Pathworks, Samba or Linux. -- 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. "David Gibbs" wrote in message ervers.com... This is driving me crazy ... I just upgraded my Win2K system to XP Pro (almost exclusively so I can get remote desktop). When I was using Win2K, I had a small workgroup setup and working fine. Now that I have XP installed, I am getting the error "workgroup is not accessible ...". I have Netbios over TCP/IP enabled, the builtin firewall is disabled, no other firewalling software is installed, and the workgroup worked fine before. I have reviewed the MS kb article http://support.microsoft.com/?kbid=318030, but nothing there seems to apply. My network consists of my XP pro system, my wife's Win2K system, and a linux system running Samba. All in the same workgroup. I AM able to map drives directly to other systems and access them via a share. I just can't browse the workgroup. Any suggestions on a next step for troubleshooting? Thanks! |
Thread Tools | |
Display Modes | |
|
|