Jump to content

Recommended Posts

Posted (edited)

We have a problem on a handfull of PCs and laptops where they won't map to the staff network drive.

 

One is a win 98 machine, any staff member who uses it cannot access the staff drive, but can on other pcs, so this leads me to belive it is a problem with the individual computers. Using Winsuite to log on.

 

Any ideas why this might be happening?

Edited by Griffo
Posted (edited)

TCP/IP protocol stack could have become corrupt, you will need to rebuild ok:

 

following should resolve above issues:

Sometimes Windows 98 runs into some issues with the tcp/ip stack, if you have issues getting to web pages, and can not view most of them, you may have a corrupt winsock and tcp/ip stack. Follow these steps and you should be back on your way.

 

Open Network settings

1.) Remove all protocols or everything EXCEPT leave the NIC Adapter

2.) Click Apply & Close the Properties box, but on reboot notice, hit Cancel. Do not reboot!

3.) Open Regedit and delete these keys:

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\VXD\Dhcp

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\VXD\Dhcpoptions

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\VXD\MSTCP

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\VXD\Winsock2

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Winsock2

 

Close Registry Editor.

 

4.) Open Network Properties again, and Click ADD - PROTOCOL - Microsoft/TCPIP (should Add Client for MS Networks Automatically)

 

Have your windows CD ready or the CAB files, once you are done, reboot the machine.

 

hope this resolves your issue ok:

Edited by bossman
Posted

Is this only Win98 clients? And is it a case of the drive not showing on these machines?

 

Have you checked that the drive letter is not used by something else?

Posted

@Griffo:

TCP/IP protocol stack rebuild XP:

Run this command from start menu: netsh int ip reset c:\tcpiprebuild.log

 

Hope this resolves the issue.

 

BTW Penfold, I hadn't thought of that good reply. :)

Posted
Just a few 98's so far, no the drive letter isn't used, will try the stack rebuild later when the room is free ad will let you know, thanks
Posted

Right, I gave it a go and still have the same problem, I also double cheked which drive letters were assigned and S:\ for the staff drive to map to is definitly not used. The public drive on P:\ and personal drive on H:\ are mapping ok.

 

It doesn't seem to be caused by winsuite either as I had to uninstall it at one point and the normal windows logon still doesnt let it map.

 

The easiest option is to get rid of 98, but that probably wont happen.

 

Any other ideas of what it may be would be appriciated

 

Its not a major problem as they can use another PC

Posted
I assume your using a logon script to map the drives? One thing i've successfully done in the past is run the login script from a command prompt and checked for error messages. Another thing to check would be share permissions etc for the staff share, or run a tweaked sctipt that gives the user the staff share on drive z: to check.
Posted

Thanks all, Sorted now :)

 

There was a line of crap on the login.bat script, on the same line as mapping the staff drive that 98 obviously didnt like.

 

Looks like somebody had sat on the keyboard :doh:

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...