VPN problems - Page 2

andyflashlite · 05-04-2004, 01:12

MGC,

(As I hinted at at in my intial posting, can you confirm that there is a completely different IP address range being used on you office LAN, including the firewall, compared to you home IP including it's firewall? The DNS has no chance of resolving if that is the case.)

My office LAN range is 192.168.1.*, my home LAN range is 192.168.2.*

I had to set it like this because the firewalls wouldn't accept the same LAN range.

Just realised as well, DNS won't resolve over a normal VPN, my firewall to firewall VPN will (if it ever works) 'cause it allows pass through of netbios but my laptop to office VPN won't unless I do the LMHosts file at each end. (I think

)

(Your office server, is it a one NIC or two NIC setup? )

It has 2 NIC's but only one is in use. The network is set up so that the firewall lan port goes to a switch and then out to the server and the client pc's. The idea was to take the load off the server and let it serve.

I think I'm at the opint where I might (very nervously) patch the office server up to SP4 with all of the updates.

If anyone knows of any problems with patching W2k server up to that level please could you let me know 'cause I'd rather know in advance than find out the wrong way and have to do another 48 hr shift sorting it out (did one of them already when I set it up the first time

)

Thanks in advance

Andy

goldchip · 05-04-2004, 18:56

Well, my VPN took a about an hour to sort out, here's what I have:
At home I use XP's built-in VPN client. At work I have an IPcop firewall (www.ipcop.org) - this is a Linux firewall distro that I have serving 9 UK domains. I setup a Win2k server as a RRAS server, using domain authentication via a policy setup in AD. The firewall forwards GRE & tcp 1723 to the RRAS server (PPTP connection). That's it, job done. I'm working on using certificates to authenticate next, so I can use L2TP, just having probes getting XP to use them :-(
Oh, I only use one nic on the server cos otherwise I lose domain visibility, contrary to what MS says, this works fine. (I think u'd need the two nic scenario if the server was internet facing, and u would have to use the filters RRAS sets up for u). This setup has been working flawlessly (and securely) for the last 8 months.