Quote:
That would be more than sufficient for me as well. I would rather have seen three VPN users, but two would do. 25 users is overkill. I need no more than 5.

Quote:
- Trying to configure the Windows VPN client to connect to the sonicwall VPN was more hassle than it was worth and I couldn't get it to work. Instead, I simply had to purchase a few licences for the proprietary sonicwall VPN client, then give the users burned CDs of the sonicwall client software.

Quote:

Clarification on the way Sonicwall handles VPN: You can purchase VPN-user-license "packs" that you add on to the router as you need them. At least that's the way it worked on the TZ170 I had.

Quote:

- Trying to put the VPN server in a DMZ was more hassle than it was worth and I couldn't get it to work. Instead, I had to put my DSL Modem into "bridge" mode so that the sonicwall box was the internet-facing appliance.

This is the way I've been planning to do the whole setup all along. So that's not a problem for me.

Quote:

- Trying to configure the Windows VPN client to connect to the sonicwall VPN was more hassle than it was worth and I couldn't get it to work. Instead, I simply had to purchase a few licences for the proprietary sonicwall VPN client, then give the users burned CDs of the sonicwall client software.

Quote:

Something else looking back that I'm realizing... Back then, I didn't understand how simple it was to set up a RADIUS server.

Valid point, but this setup will be for four users maximum, and will never change anymore. So this won't be necessary for what I'm planning to do.

I have been reading up on the thread of your experiences. Very informative! And I understand about 80% of what is said in that thread, so I guess it's not all that bad.

Quote:
SonicWall Global VPN client is freely downloadable here. I don't know if that was always the case, but it has been for at least the past year or two.

Quote:
this setup will be for four users maximum, and will never change anymore.

ROFLMAO

Oh, I'm sorry, you were serious?

Yeah, um... Change and expansion is inevitable in all networking systems. No matter how much you expect it to stay static.

In my experience, networked systems have only two directions to go: Expansion and upgrade, or complete dismantling if the company goes out of business. They never just get smaller and they never stay the same.

Quote:
I have been reading up on the thread of your experiences. Very informative! And I understand about 80% of what is said in that thread, so I guess it's not all that bad.

Hey, that's a better comprehension level than my 2%.

Quote:

Quote:
this setup will be for four users maximum, and will never change anymore.

ROFLMAO

Oh, I'm sorry, you were serious?

Yeah, um... Change and expansion is inevitable in all networking systems. No matter how much you expect it to stay static.

Normally, I would agree with you. But not in this case, because this is not a 'company' network. My father-in-law works for himself, with only one secretary to help. One of his daughters (not my GF) is also working for him now on a temporary basis because she is out of work ATM and he wanted to help out. So the normal situation is 2 persons, that's it. He's worked like this for 15 years now, and I'm pretty sure it'll stay like that for the next 10 years or so he still has to go before his retirement.

Quote:

In my experience, networked systems have only two directions to go: Expansion and upgrade, or complete dismantling if the company goes out of business. They never just get smaller and they never stay the same.

Well, this will probably be the exception which confirms the rule then.

Quote:

Quote:
I have been reading up on the thread of your experiences. Very informative! And I understand about 80% of what is said in that thread, so I guess it's not all that bad.

Hey, that's a better comprehension level than my 2%.

Cheers!

Quote:
I can setup the router IP, I can setup the subnetmask.... but where do I setup the subnet itself?? Or again, will it simply follow the subnet I choose with the router's IP?

Quote:
You set up the subnets in the DHCP server.

Quote:
On the other hand, it looks like the router requires that you manually configure the subnet or subnets of the remote LAN into the VPN rules. It's under "VPN and Remote Access->LAN to LAN->4. TCP/IP Network Settings->Remote Network IP and Remote Network Mask".

Quote:
Okay, you have a router whose internal IP address is 192.168.1.1 and another whose internal IP address is 192.168.2.1. This implies that your two networks are 192.168.1.0/255.255.255.0 and 192.168.2.0/255.255.255.0, respectively. (Actually, it doesn't imply the netmask, but you already told us those.) On the 192.168.1.1 router, the remote network and netmask are 192.168.2.0 and 255.255.255.0. On the 192.168.2.1 router, the remote network and netmask are 192.168.1.0 and 255.255.255.0. Each router wants to know what network it's supposed to be expecting on the remote side.

Quote:
I did understand however that a lot of network admins don't understand it 100% either, and because of this use some sort of online subnet calculator to find the correct subnet and mask they need for their project. (for the reference: I don't think you're one of those!)

Quote:

When you set the router's LAN-side IP address and netmask, you define the subnet. There is no need to specify the network manually; it's trivially inferable.

It's only now I remembered again that subnets are defined by the subnetmask. As I said, I spent some time grasping the theory of subnetting a while ago. It was quite embarassing having to conclude I seemed to had forgotten the essence of it so quickly. I just wanted to thank you again for reminding me.

Cheers!