- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: mapped drive thru vpn
Operating System - OpenVMS
1753682
Members
5548
Online
108799
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2009 12:00 PM
03-17-2009 12:00 PM
mapped drive thru vpn
hello,
ok..got a mapped drive but....
i'm having a problem with a mapped 'alpha 800 openVMS' drive. i have 2 swe3.0s connected via vpn. i have a xp pro machine that has a mapped drive connected with no problems. the problem is the mapped 'alpha drive. xp pro sees the drive, but when i click on it it says the "drive is not usable. network access is denied" i can reboot and click on the drive and it connects. but when i close, i can't get back in....any ideas where to start?
ok..got a mapped drive but....
i'm having a problem with a mapped 'alpha 800 openVMS' drive. i have 2 swe3.0s connected via vpn. i have a xp pro machine that has a mapped drive connected with no problems. the problem is the mapped 'alpha drive. xp pro sees the drive, but when i click on it it says the "drive is not usable. network access is denied" i can reboot and click on the drive and it connects. but when i close, i can't get back in....any ideas where to start?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2009 06:42 AM
03-19-2009 06:42 AM
Re: mapped drive thru vpn
Larry,
First there is nothing wrong with your VPN, there is no need to check that out.
Symptoms
1) When tried to open network share -- Access denied message displayed,
2) Disable and reenable the network connection, then the try to access the same share --> this time it opens, NO after this you can open the share n times until your first window is kept open.
3) When the network access denied message is diplayed try to repai your netowrk connection and then it start working.
Conclusion
The tcp stack is some how into soup
Solution
Try resetting your TCP/IP Stack use the below command
Start --> RUN
netsh int ip reset c:\resetlog.txt
netsh winsock reset
Restart --> Reenter your old ip address, try connecting.
I have succedeed 5 out of 10 times
NOT WORKING Scann for Spyware using super antispyware free edition.
First there is nothing wrong with your VPN, there is no need to check that out.
Symptoms
1) When tried to open network share -- Access denied message displayed,
2) Disable and reenable the network connection, then the try to access the same share --> this time it opens, NO after this you can open the share n times until your first window is kept open.
3) When the network access denied message is diplayed try to repai your netowrk connection and then it start working.
Conclusion
The tcp stack is some how into soup
Solution
Try resetting your TCP/IP Stack use the below command
Start --> RUN
netsh int ip reset c:\resetlog.txt
netsh winsock reset
Restart --> Reenter your old ip address, try connecting.
I have succedeed 5 out of 10 times
NOT WORKING Scann for Spyware using super antispyware free edition.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP