Somebody else mentioned that the same problem occured with 64-bit Vista. 
As far as I know, Windows 2008 is primarily 64 bit (although there is a 
32-bit version available). Maybe it helps if you can use Wireshark or 
similar to see what is actually being sent/received?

Stefan Eriksson wrote:
> Yes I can telnet 192.168.0.13 on port 9102 with no problem so the port is
> open,
> As for vmware networking, it shouldnt be an issue as it works great with
> windows 2003.
> And I dont think its a fw issue as I've completely turned of the firewall
> and still no go.
>
> As for connections, the bacula server do connect, I get a standard error if
> I disable the networking device on the client.
>
> Maybe this is a bug, thinking win2008 is rather new
>
>
> Från: Timo Neuvonen [mailto:timo-news AT tee-en DOT net] 
> Skickat: den 4 november 2008 16:31
> Till: bacula-users AT lists.sourceforge DOT net
> Ämne: Re: [Bacula-users] Fatal error: File daemonat
> "192.168.0.13:9102"rejected Hello command
>
>   
>>>> 04-Nov 13:31 backup-dir: test.2008-11-04_13.31.41 Fatal error: File
>>>> daemon
>>>> at "192.168.0.13:9102" rejected Hello command
>>>> 04-Nov 13:31 backup-dir: test.2008-11-04_13.31.41 Error: Bacula
>>>> backup-dir
>>>> 2.2.4 (14Sep07): 04-Nov-2008 13:31:44
>>>>
>>>> Hello I'm getting this error with the client using windows 2008.
>>>>
>>>> I have the correct password etc as its not the same error message, does
>>>> anyone know what this error means and how to fix it? I've googled it and
>>>> there's not much info about it.
>>>>
>>>>         
>>> Sounds like you had a too tight firewall in the client machine?
>>>       
>> Suspected that, but which type of package is the hello message, I suspect
>> its not on a specific port. More like a echo request.
>>
>>     
>
> I don't know the Bacula's protocol for sure, but I guess "Hello" is a token
> the director uses when trying to establish a connection with a file daemon
> that is expected to listen at the spesific port. Something similar like HELO
> / EHLO to port 25 when opening a connection to a mail server. The Bacula
> Developer Manual could be your friend to find it out more closely.
>
> Do you get the same error message if you turn off the file daemon (or
> disconnect the network cable or...)? If that's the case, it looks like now
> the director does not get any reply from the file daemon either, and it
> could be a firewall (or some other networking) issue.
>
> If your client is running on a virtual machine on vmware, is vmware set for
> bridged networking and the ip address belongs to the virtual machine alone?
> Have you tried to port scan that ip, is there anyone listening at all in the
> port 9102?
>   


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users