NT VPN server and Windows 98 VPN client

[Klegy]

I have set up a VPN server on a Win NT server machine. The Win NT server is located on a company LAN. The LAN machines all have a fixed private IP address (192.168.0._) including the server. A D-Link (DSL-504) router sits on the network with a default gateway address (192.168.0.1). There is an ADSL line connected directly to the router with an (external) fixed public address. The router is connected to the network via ethernet to a switch. All (NT) machines access the internet via the router. I am trying to connect two of the director's home PCs as VPN clients to the VPN server at work. One machine is running Win 98, the other running Win 98se. On those Win 98 machines one has a dial-up connection to the internet (no problems dialing up) and the other has an always on connection (Cable modem - Blueyonder Broadband connection). I have the latest DUN software running on both machines and as far as I can see the configuration is fine.
Something must be wrong with the physical set up at work. D-Link tell me that a firmware upgrade for the router is imminent but in the meantime I should put the server machine in the DMZ. I have done this and installed a Zone Alarms Pro firewall on the server. I have made sure that the relevant ports/protocols are open on this firewall.
Before I go bald can anyone firstly tell me if I can connect to the VPN server from these remote Win 98 machines in respect to the physical set up I have at work. If it is possible can you advise/explain what I should be looking for on the Win 98 machines. On both the Win 98 machines I get the error message, 'Error 645 DUN could not complete the connection to the server. Check your configuration and try again'.

 

[pathebert]

I had a similar problem connecting a Win98 client through a checkpoint firewall. The solution turned out to be placing a LMHOSTS file on the client. That pointed to the PDC for authentication and then what I did was enable SDL in the Checkpoint site configuration, on the client, and also make the client a member of the domain. That can be a little annoying when the user doesn't want to VPN, since the domain log on pops up, but it has to be there for this to work. Hope this helps!