I do this occasionaly at home with my mac laptop and my desktop pc. The only thing that is actually bound to your account are login and password as far as i know (and the setting for offline im to email, though this can only be changed if you are logged in). Most other settings are hardware dependent or describe the behaviour of your client that you wouldn't change anyway as soon as they satisfy you. Therefore, I see no reason to exchange any configuration files between my machines.
But you might run into troubles if you are sitting behind a firewall/nat (e.g. dsl router), that does port forwarding where the incoming ports are explicitly forwarded and preconfigured to a fixed ip-address on your local network. Therefore I do change my firewall settings on my dsl router for my two different machines which nerves a little bit each time

.
If this doesn't affect you, than this is a thread takeover

, because I wanna login from multiple machines from a local network behind one firewall/nat device
Recently I did some inquiry if there is a way to allow the ease of alternate use of more than one machine or the concurrent use of more than one account/machines from a single home network behind a nat/firewall router device (this is a totally common configuration for the country where I live, where your dsl connection only gets one dynamic ip-address for the internet access of your complete home network and the incoming traffic is managed with a nat/firewall router).
The major drawback in this situation is, that your internal network uses only one ip-address as incoming address for all your incoming network connections and the incoming traffic on several ports must be divided by your router to the different internal ip-addresses of your different hosts.
I came to no successful result for a number of reasons. The major reason is that it is not possible to explicitly instruct the client to negotiate with the sl grid to use a specific port range for the incoming grid2client traffic. This is needed to preconfigure your local firewall/nat box to do an appropriate forwarding of incoming port ranges to the concrete machines where you want to run the sl client on.
So, I have myself some questions and statements on if this is possible and how it is done without always having to reconfigure your firewall according to the machine that is actually used for the sl client.
As stated in
http://secondlife.com/badgeo/wakka.php?wakka=newview you can configure your client to use different TCP ports. Does that mean outgoing ports or incoming ports and is this port related to my firewall/nat router configuration?
The more important question is, how to define the incoming ports ranges for each sl client instance. The -multiple parameter allows to run different instances on one machine, which leads me to the understanding, that the sl client is able to share the incoming port range between more than one client (share means, not the ports are shared - this is not possible in a network/OS context - , rather the port *range* is shared in some way) and each client instance must therefore be able to instruct the server grid which udp ports itself is waiting for the incoming grid2client traffic.
These are only the bits I have collected so far, and someone else might have successfully run clients on different machines in one home network and knows how this is actually done. Furthermore I don't want to forget that the wiki description of the port ranges and the protocol types for the incoming traffic in the several bits and pieces on how to configure your firewall/nat for sl
(found here:
http://secondlife.com/whatis/faq.php (look at question 1

and here
http://secondlife.com/tiki/tiki-index.php?page=Configuring%20your%20firewall%20for%20Second%20Life%20accessand here
http://secondlife.com/tiki/tiki-index.php?page=TechConfigFirewalland here
http://secondlife.com/tiki/tiki-index.php?page=Login%20fails%20or%20hangs%20at%20'Verifying%20Protocol%20Version')
is somewhat contradictory and confusing and after reading them all it isn't clear what ports and what protocols are actually used (mainly for the incoming traffic). Therefore I opened my firewall to the largest described range to avoid any hassles...
I am not sure if anybody of the sl users is able to answer my questions, rather only a Linden knows how the internal port negotiation is done during the grid and client connection setup and how the needed sl client configuration can be achieved.
Wishes,
Leff.