Windows Forum

Ask something
Discussion Locked

VPN in Windows 2000 Server vs. NT 4.0

0 helpful
7 replies

by vn 1 view

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

I have recently setup a VPN connection on NT v4.0 to a 98 client machine across DSL. NO PROBLEM ...
Now... I am forced to use 2000 Sever..and use my knowledge minus Active Directory Service. I read up on ADS... nothing more than something that takes over DOMAINS.
I setup the 2000 Server on an internal network and another on a dedicated DSL connection to the internet. I setup the VPN portion of it..running only on TCP/IP. I have a DHCP that will feed the clients IP addressed.
My clients (on standar dial-up ISP) log in and recieve their IP address that matches my internal network binded to their PPP (VPN) adapter.

Problem: My clients can't see any of the Servers Network resources.

How do I make it so that my client machines can see the resources. ADS is not installed. Only Server. I can see the Server only in FIND -> COMPUTER (on 98). When I try to access the resources it asks for a password. I found out the password is the password for GUEST account. What gives... I already logged in with user name and password.

Please don't point out Microsoft's Web site. Lamers Knowledge base does not apply.

7 replies

by dmiles

Clients use the browser service to announce themselves and their shared resources on the network,with NT4,double clicking on Network Neighborhood you received a list of computers and to find resources.
In a Windows 2000 network enviroment,the browser service has been replaced by the Active Directory (AD)services.
When you upgrade all down-level clients to Windows2000 and remove NETBIOS,you need Active Directory to locate and announce resources
Install Active Directory to browse resources.

by vn

Your way will work...if you want AD. AD is quite a management tool...basically used for big network management of multi-domain type environments from one machine. Permissions...shares... etc.
AD is not needed for VPN resourse sharing. Server modeof 2000 has Browser service built into it without AD. Installed. Thanx anyways...

by avenger

No NetBIOS, no file or printer sharing in Network Neighborhood. Also no \\computername. If you want to see resources like you did pre-win2k you must enable NetBIOS (this does not apply to any 3rd party remote file sharing tools which I know nothing about). Also, if you disable support for NetBIOS on all adapters of a Domain Controller you will have a mighty interesting time trying to open Group Policy - but I digress. Enable NetBIOS on internal network card (the one on private network segment) and keep external (internet) card with NetBIOS disabled. Also make sure client dial-up properties have 'use default gateway on remote network' selected or you might not be able to reach resources on the remote network.

Thanks,

Nicholas

by vn

Wow...lost me there for a sec. I could safely tell you that NetBIOS is only active in an IPX/SPX (Non-routable) Protocol. I don't wish to activate this overhead on the systems. TCP/IP is the only active protocol over the net...so, that's all that's needed as far as VPN is concerned. Good answer, but I think this didn't resolve my issue. Thanx

by juandemarco

your problem is this: your using share level permisions and your logging onto the network, not the server. VPN is a pathway between networks, not systems,even though this is used on/by the servers. As such, you need to logon to the server (when it asks for the password) to access the resources. If you want to do diffrently, set up the workstations to logon to the domain. Then use the dialup logon to connect to the domain. Then you should see all resources and be able to restrict access to users.

by vn

Had to read that slowly... Lots of thought in your one sentence. The network is the server. It is also a VPN server. And..there is no Domain. Just a plain-ole server mode. The answer lied in the initial Windows 98 Client for Microsoft Network User Name and password. That was used when VPN was established. The VPN username and password only logged you into network. And the initial U/P at 98's logon was not in the server. So, the guest account was used and since it's disabled no access to resources.

This discussion is closed to new replies.