Problem accessing network shares

I have a fle server that I recently replaced with a new machine. The name of
the new machine is the same as that of the old, and the names of the shares
in it are also the same.

Since the upgrade my Vista machine is unable to access the shares and gives
me this error: "The parameter is incorrect". This occurrs when trying to open
mapped drives as well as trying to access the server's root UNC path.

After seeing this error I tried the "net view" command from DOS and got this:

C:\>net view \\x6
System error 87 has occurred.

The parameter is incorrect.



I've found a way to temporarily fix the problem, but after I reboot my Vista
box it happens again and I need to apply the fix again. The fix is to use
"net use" like this:

C:\>net use \\x6\software /user:xxx\username
The command completed successfully.


Note that if I use my actual domain name this command fails, but if I put in
an invalid one (like "xxx") then it succeeds. Yes, I know that's very
strange. I was lucky to find this by mistyping my domain name once and was
surprised that the command then worked. After issuing this command I can
access the file server just fine and my mapped network drives work fine as
well.


So, does anyone know how I can fix this permanently?

Try this: net use * /d. and restart the Vista. Please post back with the
result.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"Qythyx" <Qythyx@discussions.microsoft.com> wrote in message
news:1A3E9C17-F092-4685-B61B-E19932F149D3@microsoft.com...

>I have a fle server that I recently replaced with a new machine. The name
>of
> the new machine is the same as that of the old, and the names of the
> shares
> in it are also the same.
>
> Since the upgrade my Vista machine is unable to access the shares and
> gives
> me this error: "The parameter is incorrect". This occurrs when trying to
> open
> mapped drives as well as trying to access the server's root UNC path.
>
> After seeing this error I tried the "net view" command from DOS and got
> this:
>
> C:\>net view \\x6
> System error 87 has occurred.
>
> The parameter is incorrect.
>
>
>
> I've found a way to temporarily fix the problem, but after I reboot my
> Vista
> box it happens again and I need to apply the fix again. The fix is to use
> "net use" like this:
>
> C:\>net use \\x6\software /user:xxx\username
> The command completed successfully.
>
>
> Note that if I use my actual domain name this command fails, but if I put
> in
> an invalid one (like "xxx") then it succeeds. Yes, I know that's very
> strange. I was lucky to find this by mistyping my domain name once and was
> surprised that the command then worked. After issuing this command I can
> access the file server just fine and my mapped network drives work fine as
> well.
>
>
> So, does anyone know how I can fix this permanently?

Thanks for the suggestion. It almost wored. After doing what you suggested
and rebooting I could log into Vista without any problems, but when I tried
to access the file server I received the same error. To access it I had to
use the same workaround I used before.

I forgot to mention before that accessing the share from another Vista box
shows the same problem, but from the domain controller (Server 2003) and a XP
box everything is fine. Also, the other Vista box does not have any mapped
drives at all, so the problem is not related to that.

Any other suggestions?

"Robert L. (MS-MVP)" wrote:

> Try this: net use * /d. and restart the Vista. Please post back with the
> result.
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
>
>
> "Qythyx" <Qythyx@discussions.microsoft.com> wrote in message
> news:1A3E9C17-F092-4685-B61B-E19932F149D3@microsoft.com...

>
>

Assuming you can ping x6, ping x6 from a workstation. write down the IP,
then do net view \\ipaddress of the x6. Do you receive the same error?

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"Qythyx" <Qythyx@discussions.microsoft.com> wrote in message
news:1E4F0186-1C7B-473D-AE7B-5C4893F115DF@microsoft.com...

> Thanks for the suggestion. It almost wored. After doing what you suggested
> and rebooting I could log into Vista without any problems, but when I
> tried
> to access the file server I received the same error. To access it I had to
> use the same workaround I used before.
>
> I forgot to mention before that accessing the share from another Vista box
> shows the same problem, but from the domain controller (Server 2003) and a
> XP
> box everything is fine. Also, the other Vista box does not have any mapped
> drives at all, so the problem is not related to that.
>
> Any other suggestions?
>
> "Robert L. (MS-MVP)" wrote:
>

I tried your suggestion and the result was the same.

I did manage to eventually solve my problem. What I did was just completely
rename my file server. Fortunately it wasn't being used by too many people,
so after the rename and reconfiguration of the clients to point to it all is
well.

I decided to try that since it seemed that Vista had something about the
file server cached somewhere that was wrong, and I assumed the cache was
coorelated to the name. This fix worked for me, but in some environments
renaming a server probably isn't viable.

Anyway, thanks for the suggestions.

"Robert L. (MS-MVP)" wrote:

> Assuming you can ping x6, ping x6 from a workstation. write down the IP,
> then do net view \\ipaddress of the x6. Do you receive the same error?
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
>
>
> "Qythyx" <Qythyx@discussions.microsoft.com> wrote in message
> news:1E4F0186-1C7B-473D-AE7B-5C4893F115DF@microsoft.com...

>
>

Thank you for the update.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"Qythyx" <Qythyx@discussions.microsoft.com> wrote in message
news:6DCA8024-C37E-4DA7-AD80-9C9733ACB972@microsoft.com...

>I tried your suggestion and the result was the same.
>
> I did manage to eventually solve my problem. What I did was just
> completely
> rename my file server. Fortunately it wasn't being used by too many
> people,
> so after the rename and reconfiguration of the clients to point to it all
> is
> well.
>
> I decided to try that since it seemed that Vista had something about the
> file server cached somewhere that was wrong, and I assumed the cache was
> coorelated to the name. This fix worked for me, but in some environments
> renaming a server probably isn't viable.
>
> Anyway, thanks for the suggestions.
>
> "Robert L. (MS-MVP)" wrote:
>

Is any update for the solution

I have three windows OS nodes on the network. one is vista. another i
XP. the last one is CE 6. The XP can access to the CE and the Vist
both. And the Vista can access to the XP only. The same error 87 occur
if the Vista accesses to the CE. It's impossible to rename the CE fil
server because it's production that should be sold

--
Hanbin