Question

Locked

New vista PC VPN works fine but cannot see folders on domain Help!

By nnewell ·
I have recently changed to vista ultimate and had a bit of an issue getting my Netgear VPN client working etc.. but finaly have it done with new software loaded set up my domain and can sign in ok my outlook works fine connecting to exchange on the domain server. I can remote desktop to it as well. However when i try and view the domain on the network i can see nothing except my own PC. This worked fine before with my XP machine so have not changed any router settings

This conversation is currently closed to new comments.

12 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Answers

Collapse -

drive mapping

by shasca In reply to New vista PC VPN works fi ...

Can you map a drive to a network resource? Do you get any errors.
You just can't browse to resources is that the issue?

What protocals(File and print sharing, Client for microsoft Networks etc.) are enabled on the local connection?

Collapse -

Protocols that are set

by nnewell In reply to drive mapping

Hi Thanks for your reply yes i just cant browse so dont even get the chance to map.
The protocols that re set are
client for microsoft networks
determinisitic network enhancer
QOS packet scheduler
file and print sharing for microsoft networks
internet protocol version 6
internet protocol version 4
link layer topology discovery mapper i/o driver
link layer topology discovery responder
hope that helps hti sis driving me nuts ive been all over asking and no one has a clue wish i could bring back XP !!

Collapse -

Map to server

by shasca In reply to Protocols that are set

Unless you are using ip6 just uncheck it. Everything else is good.


You don't need to be able to browse to be able map.

Just right click My Computer choose any letter and in folder window \\ServerIP\C$\D$

or \\server ip\folder name,volume name.
Doing this will give an error if the problem is either VPN settings or right issues

Collapse -

Error

by nnewell In reply to Map to server

i unchecked ip6 no difference and then did your mapping and i got an error
The mapped network drive could not be created because the following error occured.
The file could not be accessed by the system.

not sure if that shines any light for you but thanks for trying

Collapse -

Access rights

by shasca In reply to Error

That sounds like VPN setup. It would appear that you aren't getting Domain access rights through the client

Collapse -

how to check rights

by nnewell In reply to Access rights

Hi Shasca
The set up of the VPN is exactly the same as it was of for the XP PC ok i could not import the policy as i was going from XP to Vista and it would have screwed up the client software ( Netgear advised this) but i had taken screen prints of all the set ups on the xp and just trnasfered them to the Vista.
Is there a way i can check if i have Domain access probably a silly question or is there something specific i should have set on the VPN client which is different from XP to Vista for doamin access
regards
Norman

Collapse -

Have you checked

by SKDTech In reply to how to check rights

Have you checked to make sure the computer itself has VPN access rights on the domain?

Collapse -

Private or public

by SKDTech In reply to New vista PC VPN works fi ...

Is Vista set to see the VPN connection as a Private or Public network.

If it is saying the connection is public then it won't allow connections with other PCs on the network.

Collapse -

Connections

by nnewell In reply to Private or public

Hi The connections are set to private. By the way if i have another pc on my home network i can see it i just cant see the server in the office although obviously the VPN is connecting as exchange is workng fine

Collapse -

One protocol related issue....

by robo_dev In reply to Connections

is that Windows uses UDP by default for Kerberos authentication, and UDP does not play well with VPNs. Therefore the workstation cannot successfully authenticate with all relevant resources.

http://support.microsoft.com/default.aspx?scid=kb;en-us;q244474

The fix is to make a registry change to the client, as outlined in the Microsoft article listed above.

From a troubleshooting standpoint, the most effective tools to use are the NetDiag utility that's part of Windows, or WireShark (free sniffer utility).

The bottom line is that the relevant protocols are either being filtered by a firewall or mangled by the VPN.

Back to Networks Forum
12 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums