how can I establish a VPN between win98 and Windows2000 advanced server

  • Thread starter Thread starter Sniper@SDU/HKPF
  • Start date Start date
S

Sniper@SDU/HKPF

I can't see any when I login to my Windows2000 Advanced server.can't anyone
solve my problem?
 
I have a Word Document explaining this. I think I tested it once, but
I'm not expert and didn't continue using. Eventually, something
brought the VPN down on our server and I haven't looked into it.

Here are part of the instructions from the document, titled:
"Employee VPN Access to the corporate LAN"
search the web for that Word document.

Hope this helps.

Installing and Configuring on Windows 98

1. Install the Microsoft VPN client software on your PC.

· Open the control panel (Start->Settings->Control Panel)
· Double-click on Add/Remove Programs
· Click on the Windows Setup tab
· In the components list click on Communications and then press the
Details…button. Be careful not to uncheck the Communications group
when you do this. Click on the word Communications instead of the
checkbox.
· Scroll down and place a check next to Virtual Private Networking. If
this is already checked skip forward to step 2.
· Press the OK button and let Windows install the VPN client software.
You will need to reboot before proceeding to step 2.

2. Configure the VPN connection.
Double-click on My Computer and then on Dial-Up Networking
· Double-click on Make New Connection
· For the connection name type "Corporate VPN"
· For the device select "Microsoft VPN Adapter
 
You'd be wanting
http://www.twice.nl/download/MSVPN.doc
and
http://www.microsoft.com/windows2000/docs/vpndeploy.doc

One thing to note - if you're having problems seeing NetNei computers then
it's more than likely down to not having netBIOS/WINS configured for your
VPN. If you're using W2k RRAS as the VPN server then note that you have to
manually configure the WINS info on the server - if your RRAS server is
using DHCP to source it's own configuration it doesn't pass that on to it's
VPN clients.

Standard checklist for probing a VPN from the client end.. let's say your
VPN server is 10.0.0.1 (vpn.domain.local), your domain fileserver is
10.0.0.2 (files.domain.local) which has shares open for domain users only:

when connected, first test IP routing - ping 10.0.0.1 then 10.0.0.2
now test DNS using the FQDNS: ping vpn.domain.local and files.domain.local
then test authentication - Start..Run.. \\files.domain.local (you should get
the list of shares, or a re-authentication box if your membership has
faltered)
Finally try WINS/NBT - Start..Run..\\FILES (you should get the same as
above)

(it'd be nice to have a netBIOS ping, but life's never fair.)

Also remember that on a slow VPN, it can take several aeons for the full
NetNei list to populate when you first browse it after connection. VPN is a
lovely lil varmint but not known for lightning-fast performance between
modems.

~D~
 
Back
Top