policies on multiple computers behind one IP address

I've currently got 14 machines running at home behind my single external IP address, all with the same key - no problems here. :)

Hi, running several machines behind a single public IP address will work perfectly. It works for Internet Connection Sharing, net access via proxy, via router (wired / wireless) and all the other configs you can think of.

You can use the same account number for each - In fact I would recomend that you do! That way all of your machines will claim credit on the one account.

[edit]
You can run lots of independant machines on the same account... they dont have to be even in the same country!

It's been answered, but the acct key is tied to you the user, not to the computer. I've got BOINC installed at home, and put it on one PC I use in the networking lab at school. I was careful to set it not to automatically start, so I'd be the one to start it when I'm there. Only running SETI though (and as it's a PII 400, wouldn't put many projects on it). It works...

Also, tieing to IP addresses isn't something that would likely be done. Reasons are many, but suffice it to say, and due to a limitation in the number of possible IP addresses (and more to the point, networks as InterNIC assigns them in chunks, aka class a, class b, class c domains, etc) having a unique IP on every machine isn't really feasible. At least not before IP v. 6.

Though many broadband users can have static IPs (I do), many ISPs use DHCP to recycle IP addys. As to modem users, the IP is assigned depending on the modem in the pool that picks up...call back, can have a dif IP.

NAT, or actually PAT (port address translation or overloaded NAT) shouldn't be a problem.

> >I've got BOINC installed at home, and put it on one PC I use in the
> networking lab at school. I was careful to set it not to >automatically
> start, so I'd be the one to start it when I'm there.
>
> If the Machine is 'always on' you could set the client to start when the
> machine boots. You could do it either as a service using BOINC_CLI or as a
> sheduled event (triggered on system boot) for BOINC_CLI or BOINC_GUI. After
> that you could put that PC into a separate location in preferences - 'school'
> might be good! - and set it to run only between certain hours. Say 6pm and
> 8am. That way the CPU wont be getting hammered during the day and you will be
> contributing to science while you are not there.
>
> ....just a thought!
>

Yeah, thx for the suggestion... Actually I have noticed that the WUs do get a lot more completed some days then others...so I'm not sure it's always shut off at night. That could be a possibility, though from 2 pm (time my network troubleshooting class starts) and 7:50 pm (time my Cisco 4 class ends) there, I'm present but only on Mondays and Wednesdays.

The main reason I didn't want to keep it running all the time during the day (when other students would need it) is

- Pentium II 400 MHz
- 256 MB RAM (at most)
- win2k Server

Thus far when it seemed to have run for awhile, no one has thus far complained. That could be a possibility though to avoid interfering with other students on slow comps.

There would be one matter to tend to though. It is a networking lab, and so when I'm not there, it might not be able to connect to the Internet (WU cache could take care of that...so long as it doesn't fill too, too much considering a slow CPU). Reason is, with all the networking classes in there, in order for students to learn networking they need to be able to mess around in there. As such it's sorta a tear down lab, and also allows students to create small networks that can't get out sometimes, and other assignments require a certain config to get out (depending on what a given class is working on). It's never the same when one class leaves, and another has dif things to do...