|
|
Joined: Apr 2006
Posts: 105
Member
|
Member
Joined: Apr 2006
Posts: 105 |
Just set up a new win2k server (actually old hardware, new HD and installation) and am trying to set up VPN on it. It's telling me I need two network adapters, one for internet, one for private network. Is there any workaround for it? I have a VPN "server" on an XPpro box now, and I never had any problems using it with one network card and one connection. Any help or hints are greatly appreciated! --Chad
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Feb 2006
Posts: 826
Member
|
Member
Joined: Feb 2006
Posts: 826 |
You really should be using two NICs. If you only use one NIC, then you're exposing your network directly to the internet. The VPN server routes traffic between your internal network and VPN clients...in one NIC out the other. If you're set on only using one NIC, then you might want to try Hamachi. https://en.wikipedia.org/wiki/Hamachi
|
|
|
|
Joined: Sep 2006
Posts: 329
Member
|
Member
Joined: Sep 2006
Posts: 329 |
Dear Chad,
In the Universe according to Microsoft, nobody uses any equipment that isn't running Microsoft Windows. You must read Microsoft documentation with that in mind to understand many things they say in MicroSpeak(C). From Microsoft's point of view, you are not going to have a separate firewall or router box, but are going to connect your Microsoft Windows Server directly to the Internet and use it as a router. Microsoft calls that Internet Connection Sharing instead of routing. A router must have at least two network interfaces to have any purpose, since the purpose of a router is to route packets between sub-networks. Therefore the Manual according to Microsoft says that you must have two network interfaces in your Windows Server to set up a VPN.
However I will assume that you are not, in fact, connecting your Windows Server directly to the Internet, but instead have a separate router and/or firewall. In that case you do not need two network interfaces in your Windows Server.
If you set up your VPN successfully on Windows XP, you already know how to set up a VPN on Windows 2000 Server. The steps are essentially the same. Just do on Windows 2000 Server what you did on Windows XP. The process is also similar on Windows Server 2003.
Of course you must have TCP port 1723 open on your firewall and redirect it to your Microsoft Windows 2000 Server.
Michael Paul CertifiedTechs.com
|
|
|
|
Joined: Oct 2006
Posts: 17
Member
|
Member
Joined: Oct 2006
Posts: 17 |
honestly, I'd just run 2 nics, get the $10 fry's special and call it a day.
|
|
|
Forums84
Topics94,512
Posts639,934
Members49,844
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
113
guests, and
31
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|