Networks

Ask something
Question Locked

Windows 2003 Shares not working

0 helpful
14 replies

by dlee

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have windows 2003 ent sp2. File shares on the server does not work. I can access \\servername and get listing of the file shares, however i can nnot access any of the shares i get a message that no network provider accepted the given network path. If i try and connect on \\ServerIP i get error Windows cannot find ServerIP. If i try to connet to \\Localhost i get Windows cannot find ... if i try to connect to \\127.0.0.1 i get windows cannot find ....

I can Net view the Servername and get a list of shares, but can not net view \\Server IP get error code 87 Paramater is incorrect.

I have tried the following:
Sysprep
Rebuild TCP\IP
Repair windows
Changed IP
Changed Hostname
Checked the GPO
No Firewall
Anti-Virus Turned off.
Sharelevel access everyone Full Control
NTFS Level access Everyone Full Control

14 replies

by mohammad oweis

It seems that you did a lot of checks, but there is left NetBios settings.

In the "Internet Protocol (TCP/IP)" properties go to Advanced -> WINS
And set the NetBios settings from Default to Enable.

Maybe this will fix it.

by dlee

Hi did as your sugested, even bounced the server, still no luck, same issues.

Thanks for the replies, i am really stumped looks like a server rebuild at this point in time.

by kenone

Can you ping the server from a workstation?
Is file and Printer sharing turned on?
Can you map a drive to a share?

by dlee

Yes i can ping the server.
File and print sharing is turned on.
No i cannot map a drive to or from the server. get error: Network Resource can not be found

by cg it

to quote you "If i try and connect on \\ServerIP i get error Windows cannot find ServerIP"

your machine has to be able to find the server address to connect.

if you know the ip address of the server, then the syntax is \\server ip address\share name. Note: you must be on the same subnet as the server.

If you use that syntax, and stil can not connect to the share, then make sure file and printer sharing is enabled in the network card properties on the server [should be enabled by default].

by dlee

I am trying to brows the shares localy on the server. the sytax is correct as i use the exact same syntax on the other servers. \\10.112.3.10 is the IP or \\servername both of these should give me a share listing. \\127.0.0.1 also returns "Windows cannot find \\127.0.0.1 make sure you have spelled ....." File and print sharing is enabled.

Thanks for the response

by mohammad oweis

Try to reset the TCP/IP stack, with the following two commands:
As i remember this will set the server to use DHCP for IP configuration
Then you will need to restart the server.

netsh int ip reset
netsh winsock reset

by dlee

I have checked and could not find any diffrences. All the keys are the same ... except for the GUID key ...

Thanks for the help ..

by dlee

I have run the netsh int ip reset command, will try the winsock rest and report back,

Thanks

by dlee

Nope did not work, same results.

Thanks for helping ..

by mohammad oweis

Check offline files on the server, try enable or disable it, sometimes they cause troubles like this.

if it did not work, try to re-initialize the offline cache by doing:
Tools -> Folder Options -> Offline files

Press Ctrl+Shift and hit "Delete Files" button, then restart.
But this will delete all offline files on the server if they exist; i don't believe that anyone using it inside a server.

by dlee

I dont have any options just a message:

Remote Desktop is configured to support mulitple connections Offline Files cannot be enabled with Remote Desktop in this configuration.

I supose this means that offline files is disabled ?

Thanks again for the help.

by mohammad oweis

Yes, offline is disabled; it does not work with remote desktop.

Try to check the following key on register and compare the values with another server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters

I had the same problem with Windows XP client last year, the problem caused by a virus.
But i did not work hard to solve it, i formatted the PC, anyway it was in a mess.

Hope you will find something in the registry.

This discussion is closed to new replies.