Re: The list of servers for this workgroup is not currently availiable



This is the Small Business Server Newsgroup. If you have a SBS Server it must be installed in Domain Controller mode and not Workgroup. If this is Standard server post to the correct NG if it is SBS be sure it is installed correctly and post back.

--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC

<bglenn@xxxxxxxxxxxxxxxxxx> wrote in message news:b5ca0c7d-ebce-4c35-af13-a3fd7803fc5c@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have been struggling w/ this one and have found no answers on the
Internet.

Server 2003 (home office) Windows 2000 server (remote office). Not
exactly sure when this problem started whether it begin before two (2)
Vista machines were added to the network. Mixed environment of XP,
W2K, and Vista pcs. I already had all pcs mapped to either server w/
no error messages....could map drives all day long between both
offices. Now I can't create any new mapped drives from either office.

I'm not sure if Vista is the problem because of this. User is getting
a new pc. Has old XP machine being upgraded and still using XP. Drives
are mapped and you can map a drive to the remote office just fine
prior to replacement. Replace pc and try to map a drive to the remote
office......when browsing for a folder the remote office server will
either not show up or does show up but you cannot "open" it to access
any folders or you finally get an error message as follows.....

Remote server is not accessible. You might not have permission to use
the network resource. Contact the administrator of this server to find
out if you have access permission.

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

I went to an older pc here in the home office while I was typing this
and the pc will show the remote office server and let me map a drive
to it. I have a new pc sitting beside me that will not see the remote
server. I was talking to a user in the remote office and I was going
to help them map a drive. They already had a mapped drive to the home
server. Now they cannot see the home server nor map a drive and then
gets the error message. It can't be a permission problem because they
already have a drive mapped to the home server and can access it all
they want....

Any clues?

TIA!!

.



Relevant Pages

  • Re: map network drive - password error - logistics
    ... server rather than just the "root" of the server?" ... Drives are concerned with data storage - if you mapped drive X: ... it goes to the root directory. ... If you want to map a drive to the 'root' of a server, ...
    (microsoft.public.windowsxp.network_web)
  • Re: Vista drive mapping to 2008 Server
    ... The chimney offload was disabled on both client and server and I have reset ... Now I can map a drive using the command Prompt and access it via that method ... It sounds like something in the network infrastructure may not be working ... connect or map drives. ...
    (microsoft.public.windows.vista.networking_sharing)
  • Re: After manually undoing a recent MS Update, my server is a mess
    ... Keep in mind that I have seen OEM drivers up there so given that you've blown that image away, I can't say for certain that the 'critical' was 100% pushed by Microsoft. ... External USB is no replacement for local drives. ... LOL I show my naivety here when I say that I showed great diligence in my blind application of any MS suggested resolution to "Critical Errors" on my Small Business Server Monitor Report. ... When I got the first BSOD, I booted from the orginal CD and chose to only restore the System files. ...
    (microsoft.public.windows.server.sbs)
  • Re: After manually undoing a recent MS Update, my server is a mess
    ... information to login to my server remotely to look around--hoping he could ... External USB is no replacement for local drives. ... stored on) and chose to only restore the System files. ... The "Cases" drive was actually a shared folder on an external ...
    (microsoft.public.windows.server.sbs)
  • Re: After manually undoing a recent MS Update, my server is a mess
    ... During the restore, the server rebooted without confirmation. ... The "Cases" drive was actually a shared folder on an external ... I mirrored the two drives ...
    (microsoft.public.windows.server.sbs)

Loading