On 01/28/2015 1:28 am, Luc Van der Veken wrote:
> On 27 January 2015 21:18, dweimer wrote:
> 
>> it appears to already have determined the IP prior to it hanging.
>> 
>> Putting it back to IP instantly connects.
> 
> Yes, but I see it's connecting to another IP address (...5.4 instead of 
> ...1.4).
> Was it supposed to do that because you changed network settings
> between attempts, or is that the problem?
> 
> | Connecting to Director bacula.dweimer.local:9101
> | bconsole: bsock.c:208-0 Current 192.168.1.4:9101 All 192.168.1.4:9101
> 
> versus
> 
> | Connecting to Director 192.168.5.4:9101
> | bconsole: bsock.c:208-0 Current 192.168.5.4:9101 All 192.168.5.4:9101
> | bconsole: bsock.c:137-0 who=Director daemon host=192.168.5.4 
> port=9101
> | bconsole: bsock.c:310-0 OK connected to server  Director daemon
> 192.168.5.4:9101.
> 
> 
Your right, totally missed an obvious error, was just looking at the 
last octet, as my network is a 24 bit mask. Now to find out where its 
getting that from...

-- 
Thanks,
    Dean E. Weimer
    http://www.dweimer.net/

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users