New client account, no ip4 address assigned

[PatG]

Running vpnserver v4.04 on windows 7 pro. Using Secure NAT.

Running vpnclient v4.04 on debian wheezy.

Created a new account using the same values from an existing account.

Start client with following command sequence from terminal window

vpnclient start
vpncmd
take option 2, client on localhost.
issue command accountconnect accountname
quit
ifconfig

the vpn client is connected and the vpn has both an ip4 and ip6 address assigned.

stop the vpnclient with vpncilent stop

vpnclient start
vpncmd
take option 2, client on localhost.
issue commadn accountconnect newaccountname
quit
ifconfig

the vpn client is connected and the vpn has no ip4 address, only an ip6 address assigned.

Why no ip4 address for the new account using the old account values?

If I compare the extracted accounts from the vpn_client.conf files the olny differences I see are meaningless.

diff olree.config olreeold.config
1,2c1
< old
< declare Account1
---
> declare Account2
5,7c4,6
< uint64 CreateDateTime 1390379330372
< uint64 LastConnectDateTime 1408592845796
< string ShortcutKey C9EACEF04EACEC5F453F029EC24501A0A5878DE9
---
> uint64 CreateDateTime 1408594414694
> uint64 LastConnectDateTime 1408594514261
> string ShortcutKey B6C296076813E0D41F2A871D2AD62F621284F55C
9c8
< uint64 UpdateDateTime 1408215713634
---
> uint64 UpdateDateTime 1408594508638
19c18
< string AccountName olree
---
> string AccountName olreeold

[PatG]

Did some more testing.

AfterI connected I did an accountstatusget accountname command.

And now an ifconfig command shows the ip4 address.

So I don't know what to think about this.

[thisjun]

SoftEther VPN client doesn't control acquiring IP address.
I guess that acquiring process accidentally take a long time.