Server connectionbroke

  • Thread starter Thread starter Richard
  • Start date Start date
R

Richard

Hi,

I just downloaded/installed a bunch of non-critical updates from
Microsoft Update. Apparently one of them was Windows Firewall for my
WinXP2 system. I don't know if this has anything to do with my
problem, which is:

Now when I click a a drive-letter mapped to a Win20003Srvr folder, I
get a message box captioned "Windows" with the content:

==============
An error occurred while reconnecting S: to \\ServerMachineName
\ShareName
Microsoft Windows Network: The network path was not found.
This connection has not been restored.
==============

When I logon to the server, everything appears to be normal.
The connection worked fine yesterday before the Windows Update.

Any ideas?

TIA,
Richard
 
Hi Richard,

Strange... Try this. Right click the S: drive in explorer (if it is there -
it should be there but disconnected). Select "Disconnect".
Now log off and log on again. The drive hay reconnect OK if your
login-script is setting the drive mapping.

If you are in control of the mapping, try connecting Drive S to the resource
you want. Check the box to remember this connection.

Did any of that work?

CreateWindow
http://mymessagetaker.com Stop using those paper phone message pads - make
the computer work for you (not the other way around)!
 
Hi there,

Thanks for your response. I didn't have a chance to get back to this
until this afternoon. BTW, I run Admin-privileged logons on both my
WinXP/SP2 workstation and Win2003Svr/SP1 server. I'm connecting
through a Microsoft Workgroup.

Before I did anything else, I booted up both systems today, but
logged on only to the workstation, where I got a tray message
asserting "There is an IP address confilict [stet] with another system
on the network." I expected my drive mappings to fail, but the first
one I tried (S:) worked perfectly.

So right now, I'm planning to treat the reported problem as a fluke.
If it recurs, I'll apply your remedy and report back.

I now have an idea of how my shares are faulty (causing the foregoing
message), but I going to post that as separate question.

Regards,
Richard
 
Back
Top