Re: Network connection

I too have this problem,

"(domainname) is not accessible. You might not
have the permission to use this network ressource.
Contact the administrator of this server to find out if
you have access permissions.

The list of servers for this workgroup is not currently
available"

It has only started happening today and it happens for all users including administrators, but only from one particular PC.
All others are still fully functional

Possible clue to the cause:
I also note that prior to browsing to the domain name i browse to the Microsoft Windows Network Icon.. and normally there are two others Win Terminal servers and Web Client Network, but since this has started the second two icon dont appear either...

I would love to hear anyones ideas on what causes this behavior

Thanks Nick

Hi, Nick

Maybe you should check this MS article -->
http://support.microsoft.com/default...b;en-us;318245
Is this computer a member of a domain or Workgroup?
Maybe restore to an earlier time would not be a bad solution?

--
Best Regards,
Sebastjan Kocelj, MCSA
Avtenta.SI
Microsoft Gold Certified Partner
for Support Services

"Nick" <anonymous@discussions.microsoft.com> wrote in message
news399D3E5-A57D-47D7-9534-2971CD58CC76@microsoft.com...
> I too have this problem,
>
> "(domainname) is not accessible. You might not
> have the permission to use this network ressource.
> Contact the administrator of this server to find out if
> you have access permissions.
>
> The list of servers for this workgroup is not currently
> available"
>
> It has only started happening today and it happens for all users including
administrators, but only from one particular PC.
> All others are still fully functional
>
> Possible clue to the cause:
> I also note that prior to browsing to the domain name i browse to the
Microsoft Windows Network Icon.. and normally there are two others Win
Terminal servers and Web Client Network, but since this has started the
second two icon dont appear either...
>
> I would love to hear anyones ideas on what causes this behavior
>
> Thanks Nick