QUOTE (wolfv @ 10-6-07, 1:44pm)

Add a second TAP-Win32 adapter:
Start Menu > All Programs > OpenVPN >
Add a new TAP-Win32 virtual ethernet adapter.After installing there are two Network Connections:
Local Area Connection
Local Area Connection 4
Enable Internet Connection Sharing (ICS) (this part is specific to Win2k):
Control Panel > Network and Dial-up Connections >
Local Area Connection 2 > Sharing > check box "Enable Internet Connection Sharing for this connection".
On the one hand, you've indicated that the new TAP-Win32 interface is "
Local Area Connection 4," but then you've enabled ICS on interface "
Local Area Connection 2." Was the latter a typo?
QUOTE (wolfv @ 10-6-07, 1:44pm)

Disconnect PC from the Internet
Reboot
Disable all software firewalls on the PC
From command line:
ipconfig/all
There was no DNS Suffix.
Good.
QUOTE (wolfv @ 10-6-07, 1:44pm)

Connect PAP2 to PC via crossover cable
Power on the PAP2
Wait 5 minutes
Factory Reset:
Dial ****
Enter: 73738#, 12 to confirm
Cycle the PAP2 power
Wait 10 minutes (light never turned red)
Cycle the PAP2 power
Wait 5 minutes
For now, you can cease waiting 5 mins, factory resetting, and waiting another 10 mins. Simply connect your PAP2, wait about a minute, and try grabbing its IP Address. If it's a
192.168.0.xxx address, it's getting an ICS assigned address (in which case you can try the unlock method properly). Otherwise, the unlock process is dead in the water as the adapter isn't receiving an ICS assigned IP address.
QUOTE (wolfv @ 10-6-07, 1:44pm)

Start SolarWinds
Make sure that SolarWinds is configured to "Transmit & Receive" files.
SolarWinds is listening to 169.254.194.196 (lower-right corner)
Ideally SolarWinds should be launched BEFORE the PAP2 gets connected to the PC; however, if launching SolarWinds that way prevents it from listening on "192.168.0.1," after the PAP2 has been connected to the PC, SolarWinds should be started almost immediately thereafter. Obviously though, if ICS isn't working correctly on your PC, SolarWinds won't listen on "192.168.0.1."
QUOTE (wolfv @ 10-6-07, 1:44pm)

Get the IP address of your PAP2 web-interface:
Dial ****
Enter: 110#
Put that number in your Web Browser Address: 192.168.2.100 (should be 192.168.0.xxx)
This is the part which I find most intruiging. Your PC doesn't doesn't show any network interfaces on the 192.168.2.xxx network, yet your PAP2 keeps getting assigned that 192.168.2.100 IP Address. Perhaps this is a default IP Address built into the PAP2, or perhaps your PAP2 is currently configured w/ a STATIC IP ADDRESS. A FACTORY RESET of the PAP2 should force it back to DHCP.
QUOTE (wolfv @ 10-6-07, 1:44pm)

ping 192.168.2.100 timed out
The lack of any PC network interface on 192.168.2.xxx explains why this ping fails.
CODE
C:\>ipconfig/all
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : wolfPC
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
This looks good.
CODE
Ethernet adapter Local Area Connection 4:
Media State . . . . . . . . . . . : Cable Disconnected
Description . . . . . . . . . . . : TAP-Win32 Adapter V8
Physical Address. . . . . . . . . : 00-FF-64-A0-D9-0F
This too looks good. Hopefully this is the interface you enabled ICS on.
CODE
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-14-2A-31-C1-90
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.194.196
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 169.254.194.196
DNS Servers . . . . . . . . . . . : 68.87.85.98
68.87.69.146[/color][/b]
This looks BETTER, but the
two DNS servers above (68.xxx.xxx.xxx) are "real" IP Addresses (i.e. ones likely belonging to Comcast. An "
ipconfig /release" should clear those values out.
Now.. I did some additional Googling on ICS and Win2K and found
this web-page. It takes ICS configuration a step further than is normally required. Read through all of the steps on that page, but pay careful attention to sub-steps 8, 9 & 10.
Note 1: In sub-step 3, instead of the network interace which connects to your cable modem, you need to use the "TAP-Win32 Network Interface" (i.e. "Local Area Connection 4.")
Note 2: In sub-steps 8, 9, and 10, the network interface you want to modify is your PHYSICAL ETHERNET INTERFACE (i.e. "Local Area Connection").
Diggler