Niclas Lindqvist's questions

I'm in the works of installing a postfix mailserver on a machine currently being used as web server. As of right now, I've got it working as far as that I can send and receive emails using telnet through port 25.

However, as my customer is concerned with downtime, I'd like to setup all the accounts one by one over time, and making sure it works, rather than just cutting the cord to the old mail server and start creating new accounts on the new system.

How can I add the domain customer.com to my mail server and just add something like [email protected] to the users and aliases-lists without the web server trying to send all emails with the @customer.com domain to the new mail server?

I'm running ubuntu, using postfix and postfix-mysql on the new machine, the old mail server is on a hosted environment somewhere else, where I don't have any control.

I'm wondering what I'd have to do to make the following scenario possible:

 _____________           __________________
|             |         |                  |
|  Network A  |         |  Network B       |
|             |         |     ___________  |
|             ----------====== Network C | |
|             |         |    |___________| |
|_____________|         |__________________|

I.e. I want to tunnel the trafic from Network C to network A through the network and firewall of Network B.

I have
- a Cisco ASA-5510 on Network A
- an unknown setup on Network B
- Requirements of an as small as possible unit on Network C

My current idea is to prime an ASA-5505 and use it as a hardware VPN-client using EZVPN, but I'd like to have a product that's more rugged and industrial, as the unit may work in +40°C areas.

BTW: Never mind my mad ASCII-art skills ;)

We have a couple of Macs, running Leopard and Snow Leopard in our otherwise pure Windows environment.

We cannot get file names longer than 31 characters and some times the file permissions gets scrabbled (users can't delete their own folders or access files they usually access). This only occurs when connecting through AFP, We've tried with SMB but it's horribly slow when working with larger documents, so it's not an option.

I somewhere read about AFP 3.0 being the answer. So my question is:

Is there some way of updating my "AFP version" on Windows Server 2003, or does anyone have a different idea of what might help to resolve this situation?

I'm having a hard time with SQL Transaction Log Shipping with the following premisses:

• Server A, where data gets loaded to the database
• Server B is on a remote location
• The two servers never share a common network and can communicate via common protocol. (HTTP, Email etc.)
• The internet connection on Server A is slow and only available a few times a month.
• I want to get data from Server A to Server B when an internet connection is available.

The idea i have so far is to make a Transaction Log Shipping setup on Server A and ship to Server B. I've got the setup running on Server A (Taking backups n times a day) but how do i set up Server B to accept the files i get to it (ATM via email)?

If the computers were in network, i could connect to Server B from Server A when making the TLS setup, and get the Server Agent Jobs setup like that. Is there a way to setup Server B separately? Write the Jobs directly on Server B sounds like an easy enough solution but the "Create New Job" dialog isn't very helpful.

Any other ideas or help in this matter is greatly appreciated!

Best regards Niclas Lindqvist

I'm setting up an IPSec connection from an Westermo MRD310 to our company Cisco ASA5510.

We've had many successful setups using this method, creating a tunnel network between a remote location and our internal network. This time I'm trying to do this setup over a GPRS speed network (that's what you get way up in the north of Sweden). But it won't go through.

Does anyone have information about what fails in the following log, or have information about minimum transfer rates for establishing an IPSec tunnel. Also, any information on what could decrease transfer rate requirements would be appreciated.

I use a subscription with public, static IP-address to avoid NAT:ing and unexpected address changes. However as the GPRS is the initiator, static IP shouldn't be a requirement for this, am I right?

<83>Jun 21 23:00:57 ipsec__plutorun: Starting Pluto subsystem...  
<27>Jun 21 23:00:57 ipsec_setup: ...Openswan IPsec started  
<84>Jun 21 23:00:57 pluto[5860]: Starting Pluto (Openswan Version 2.4.12 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR; Vendor ID OEKBzdY{wM]@) 
<84>Jun 21 23:00:57 pluto[5860]: Setting NAT-Traversal port-4500 floating to on 
<84>Jun 21 23:00:57 pluto[5860]:    port floating activation criteria nat_t=1/port_fload=1 
<84>Jun 21 23:00:57 pluto[5860]:   including NAT-Traversal patch (Version 0.6c) 
<86>Jun 21 23:00:57 ipsec__plutorun: Unknown default RSA hostkey scheme, not generating a default hostkey 
<84>Jun 21 23:00:57 pluto[5860]: ike_alg_register_enc(): Activating OAKLEY_AES_CBC: Ok (ret=0) 
<84>Jun 21 23:00:57 pluto[5860]: no helpers will be started, all cryptographic operations will be done inline 
<84>Jun 21 23:00:57 pluto[5860]: Using KLIPS IPsec interface code on 2.6.25-uc0 
<84>Jun 21 23:00:57 pluto[5860]: Changing to directory '/etc/config/cacerts' 
<84>Jun 21 23:00:57 pluto[5860]: Changing to directory '/etc/config/aacerts' 
<84>Jun 21 23:00:57 pluto[5860]: Changing to directory '/etc/config/ocspcerts' 
<84>Jun 21 23:00:57 pluto[5860]: Changing to directory '/etc/config/crls' 
<84>Jun 21 23:00:57 pluto[5860]:   Warning: empty directory 
<27>Jun 21 23:00:57 ipsec_setup: Starting Openswan IPsec 2.4.12...  
<84>Jun 21 23:00:58 pluto[5860]: loading secrets from "/etc/config/ipsec.secrets" 
<84>Jun 21 23:01:01 pluto[5860]: added connection description "SPMVPN" 
<84>Jun 21 23:01:01 pluto[5860]: listening for IKE messages 
<84>Jun 21 23:01:01 pluto[5860]: adding interface ipsec0/hso0 85.117.XXX.XX:500 
<84>Jun 21 23:01:01 pluto[5860]: adding interface ipsec0/hso0 85.117.XXX.XX:4500 
<84>Jun 21 23:01:01 pluto[5860]: forgetting secrets 
<84>Jun 21 23:01:01 pluto[5860]: loading secrets from "/etc/config/ipsec.secrets" 
<84>Jun 21 23:01:02 pluto[5860]: "SPMVPN" #1: initiating Main Mode 
<27>Jun 21 23:01:02 ipsec__plutorun: 104 "SPMVPN" #1: STATE_MAIN_I1: initiate  
<27>Jun 21 23:01:02 ipsec__plutorun: ...could not start conn "SPMVPN"  
<84>Jun 21 23:01:02 pluto[5860]: "SPMVPN" #1: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n] method set to=106  
<84>Jun 21 23:01:02 pluto[5860]: "SPMVPN" #1: ignoring Vendor ID payload [FRAGMENTATION c0000000] 
<84>Jun 21 23:01:02 pluto[5860]: "SPMVPN" #1: enabling possible NAT-traversal with method draft-ietf-ipsec-nat-t-ike-02/03 
<84>Jun 21 23:01:02 pluto[5860]: "SPMVPN" #1: transition from state STATE_MAIN_I1 to state STATE_MAIN_I2 
<84>Jun 21 23:01:02 pluto[5860]: "SPMVPN" #1: STATE_MAIN_I2: sent MI2, expecting MR2 
<84>Jun 21 23:01:13 pluto[5860]: "SPMVPN" #1: ignoring informational payload, type INVALID_COOKIE 
<84>Jun 21 23:01:13 pluto[5860]: "SPMVPN" #1: received and ignored informational message 
<84>Jun 21 23:01:32 pluto[5860]: "SPMVPN" #1: ignoring informational payload, type INVALID_COOKIE 
<84>Jun 21 23:01:32 pluto[5860]: "SPMVPN" #1: received and ignored informational message 
<84>Jun 21 23:02:12 pluto[5860]: "SPMVPN" #1: max number of retransmissions (2) reached STATE_MAIN_I2 
<84>Jun 21 23:02:12 pluto[5860]: "SPMVPN" #1: starting keying attempt 2 of an unlimited number 
<84>Jun 21 23:02:12 pluto[5860]: "SPMVPN" #2: initiating Main Mode to replace #1 
<84>Jun 21 23:02:12 pluto[5860]: "SPMVPN" #2: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n] method set to=106  
<84>Jun 21 23:02:12 pluto[5860]: "SPMVPN" #2: ignoring Vendor ID payload [FRAGMENTATION c0000000] 
<84>Jun 21 23:02:12 pluto[5860]: "SPMVPN" #2: enabling possible NAT-traversal with method draft-ietf-ipsec-nat-t-ike-02/03 
<84>Jun 21 23:02:12 pluto[5860]: "SPMVPN" #2: transition from state STATE_MAIN_I1 to state STATE_MAIN_I2 
<84>Jun 21 23:02:12 pluto[5860]: "SPMVPN" #2: STATE_MAIN_I2: sent MI2, expecting MR2 
<84>Jun 21 23:02:22 pluto[5860]: "SPMVPN" #2: ignoring informational payload, type INVALID_COOKIE 
<84>Jun 21 23:02:22 pluto[5860]: "SPMVPN" #2: received and ignored informational message 
<84>Jun 21 23:02:42 pluto[5860]: "SPMVPN" #2: ignoring informational payload, type INVALID_COOKIE 
<84>Jun 21 23:02:42 pluto[5860]: "SPMVPN" #2: received and ignored informational message