XP VPN Server / NT 4 Server PDC

[vdmtery]

I am trying to configure a VPN server at our office. We have Windows NT
4.0 Server acting as a primary domain controller. I have done some
research and have found that configuring NT RAS can be iffy at times
and a lot of headaches. So, what I wanted to do is configure an XP
machine elsewhere on the internal LAN as a VPN server. I have
successfully set up the VPN server on the XP Pro machine but I am
having problems getting access to the office domain. I can log onto the
VPN server machine as long as I do not use a domain name. While I am
logged on I can see all the network computers and the NT PDC, but I
cannot gain access to any shares. Obviously it is because I am not
logged onto the domain. Besides setting up a VPN server on the NT 4.0
Server, is there any other options here with my current setup? I have
searched the web and have found similar attempts by other people but no
definitive resolution.

Thank you

 

[Robert L [MS-MVP]]

you don't need to join the domain, but you do need to use a domain logon ID to access the resources of the network. this search result may help,

computer browser over vpn
.... Computer Browsing over VPN - Permission or Cached Credentials issues. If you
can ping the remote computer but can't browse the resources, you may have a ...
www.howtonetworking.com/VPN/browsingovervpne1.htm

Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

I am trying to configure a VPN server at our office. We have Windows NT
4.0 Server acting as a primary domain controller. I have done some
research and have found that configuring NT RAS can be iffy at times
and a lot of headaches. So, what I wanted to do is configure an XP
machine elsewhere on the internal LAN as a VPN server. I have
successfully set up the VPN server on the XP Pro machine but I am
having problems getting access to the office domain. I can log onto the
VPN server machine as long as I do not use a domain name. While I am
logged on I can see all the network computers and the NT PDC, but I
cannot gain access to any shares. Obviously it is because I am not
logged onto the domain. Besides setting up a VPN server on the NT 4.0
Server, is there any other options here with my current setup? I have
searched the web and have found similar attempts by other people but no
definitive resolution.

Thank you

 

[vdmtery]

Thanks Robert,

I am logging on to the VPN server with a domain logon id. It is the
same user id & password I use to logon when I am internally at the
office. I can ping the IP addresses of the computers. When I use the
'net view' command it successfully shows me all the shares.

If I use the 'net use' command to map a network drive to a shared
folder such as this :

net use z: \\office1\temp

It returns 'System error 1130 has occurred. Not enough server storage
is available to process this command.'

NOTE : I am testing this connection over the internet connection from
another office network with a different protocol. My office is
192.168.1.x while the other office is 192.168.2.x if that has any
impact.

Terry

 

[Chuck]

Thanks Robert,

I am logging on to the VPN server with a domain logon id. It is the
same user id & password I use to logon when I am internally at the
office. I can ping the IP addresses of the computers. When I use the
'net view' command it successfully shows me all the shares.

If I use the 'net use' command to map a network drive to a shared
folder such as this :

net use z: \\office1\temp

It returns 'System error 1130 has occurred. Not enough server storage
is available to process this command.'

NOTE : I am testing this connection over the internet connection from
another office network with a different protocol. My office is
192.168.1.x while the other office is 192.168.2.x if that has any
impact.

Terry

Terry,

The somewhat cryptic message "Not enough server storage is available to process
this command." is well known here. If this problem is related to your inability
to share files between two computers, the problem is with the computer sharing
the files.
http://support.microsoft.com/?id=177078
<http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2000092713243506>

 

[vdmtery]

Chuck,

Thank you. Your suggestions have fixed one problem. I am now able to
connect to all the shares the are configured on the machine that the
VPN server is actually configured on. Unfortunately, I have been unable
to connect to any shares located on other machines on the LAN. When I
use 'net view \\office1' I get error 53. Using Robert's suggestions has
led me to the DNS and WINS. As far as I am aware there is no specific
WINS server configured. All computers within the office obtain and IP
address via the DHCP server (router). Do I need to add a WINS server?
Will setting up a WINS server affect the current DHCP settings?

Terry

 

[Chuck]

Chuck,

Thank you. Your suggestions have fixed one problem. I am now able to
connect to all the shares the are configured on the machine that the
VPN server is actually configured on. Unfortunately, I have been unable
to connect to any shares located on other machines on the LAN. When I
use 'net view \\office1' I get error 53. Using Robert's suggestions has
led me to the DNS and WINS. As far as I am aware there is no specific
WINS server configured. All computers within the office obtain and IP
address via the DHCP server (router). Do I need to add a WINS server?
Will setting up a WINS server affect the current DHCP settings?

Terry

Terry,

Is this a domain, with a DNS server? And the clients running XP? If so, you
need to setup and use the DNS server for name resolution.
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>

If not, check the Node Type on the problem computer, and compare it to a couple
properly working computers.
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>