Samba in the service console installation

[pierre_gronau]

Hello,

I know it is unsecure to realize Samba in the service console ...

How can I install samba in the service console ?

Where can I find the correct rpms compliant to the service console of ESX 3 ?

Which port in the esx firewall should be opened and how ?

Thanks in advance

[FredPeterson]

This isn't answering your question, but why would you want to do this? I see no reason to create a Windows accessible share on an ESX host OR join the server to the domain unless you want to control access via domain membership - but then you don't need to join it to the domain to do that.

[admin]

I won't waste a lot of words here

How can I install samba in the service console ?

You don't[/b]

Where can I find the correct rpms compliant to the

service console of ESX 3 ?

They are not.[/b]

Which port in the esx firewall should be opened and

how ?

See Above[/b]

[Texiwill]

Hello,

While I do not recommend this, you can. This is one of the most insecure things you can do. But it is possible. Horrible to do.

From the ESX media install samba-3.0.9-1.3E.8vmw.i386.rpm. (That is from the 3.0.1 media).

Open up ports. You can find the port numbers in /etc/services.

TCP:netbios-ssn

UDP:netbios-dgm

UDP:netbios-ns

Once more, you DO NOT want to make an ESX Service Console a File server.

You may want it to be a client, a client only needs to use 'esxcfg-firewall -e smbClient' to enable it.

Best regards,

Edward

[petedr]

Agree with what everyone is saying, while it is possible it is not a good idea to install and setup Samba in the console.