"Workgroup" is not accessible.

  • Thread starter Thread starter Charly
  • Start date Start date
C

Charly

When I'm tring to view the workgroup computers, i'm
getting this kind of error:
"Workgroup" is not accessible. You might not have
permission to use this network resorce.

The list of servers for this workgroup is not currently
availiable
These KB articles didn't solve the problem: 318030 &
298804. Never before I had problems like this, when I was
connecting a new computers to LAN with fresh win
instalations.
All PC's are physically connected over the LAN, have the
same workgroup & appropriate IP's. The most stupid is
that I cann't view workgroup or PC's by name, but when
I'm serching by IP address I can even go inside PC & use
shared resorces!!! For example (PC name: pc, IP address:
192.168.0.1):
\\pc\temp - don't work , but
\\192.168.0.1\temp - works!!!!!!

Any suggestions how to solve this???
!!ASAP!!
 
if mapping ip works but not host name, this is name resolution issue. if you
have mixed os, you may want to enable netbios over tcp/ip on w2k/xp. or
quoted form 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. The semaphore timeout period has expired."

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
Windows & Network Support, Tips and FAQs on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
 
Thx Robert, I'll try these operations, but I'm quite sure
that this will not help. I'm connecting new & old PC's
quite offten & I know how to connect & what to change.
This isn't a routine problem - everything is set
correctlly, the problem is in windows or maybe in some
patch/update, which were made after Lovesan (Blaster)
virus attack. I guess I can get help only from person who
got the same problem - but question is - did he solved
this problem? As I see - here shows up more & more posts
with this problem,- people just cann't connect 2 or more
PC's with NEW! win XP (home/pro doesn't matter)
installations.
P.S. I've just installed another 2 PC's with XP home -
everything is OK. But those still don't work...
 
Back
Top