RE: Dropping Shared Connections (only)



If I'm understanding your situation, it sounds as though you've proved that
name resolution is your problem. All systems member of same workgroup? Are
the IP addresses of all of these systems fixed, provided by DHCP from some
source like a router or a server (if server, the one with the shares?), or a
mix? You are connecting to the server via RDP as an admin or as a TS user?
You have what kinds of accounts on the server / local workstation?

Worst-case scenario, as in you you have no admin rights to fix general
issues / make sure that NetBIOS over TCP/IP is working everywhere, you could
just creat your mapped drives using the IP address instead of the server
name. If that's not satisfactory, maybe you could post back with an outline
with more information about the general network environment infrastructure
and your working relationship to it. That might provide enough information
for someone here to give more concrete suggestions.

"+Bob+" wrote:

Vista SP1

I have an issue with Vista dropping shared drive connections, often
while working on files on those drives. Today I was working in Word on
a file on a shared drive... the connection just dropped. Word hung,
checking in Explorer (clicking on drive letter) gave me a "drive not
available" message on several drives mapped to that machine.

The drives are shared off a win2003 server and I use simple
username/password authentication to access the drives, no domains, no
A/D.

It's not a physical or general networking issue. I can still browse
the Internet. In fact, the last time it happened I was logged into the
server with an RDC connection and it continued to act normally.

I found that I could not see the server by browsing the network.
Browsing from the win2003 server side I could still see the client on
the network.

Ideas?

.



Relevant Pages

  • Re: How does authentication work?
    ... This I believe is because 4 drives ... the connection fails all 4 drives have to be deleted before any can be ... is the remote server that requests the credentials to authenticate the ...
    (microsoft.public.windows.server.general)
  • 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)
  • Re: After manually undoing a recent MS Update, my server is a mess
    ... Before installing this server, my users were accustomed to storing all of ... The "Cases" drive was actually a shared folder on an external ... I mirrored the two drives ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.sbs)