Topic: Make SME better aware of Windows network

[Confucius]

A kind of problem I keep on stumbling into, every release from SME.
Maybe the procedure can be made default since I didn't notice any drawbacks so far but that's up to the developers.

The procedure to make SME being able to, for example, do commands like: ping <windowsmachine>

Code: [Select]

mkdir -p /etc/e-smith/templates-custom/etc/nsswitch.conf

cp /etc/e-smith/templates/etc/nsswitch.conf/10files \
/etc/e-smith/templates-custom/etc/nsswitch.conf/10files

pico /etc/e-smith/templates-custom/etc/nsswitch.conf/10files


adjust the line:

hosts:      { ($AccessType eq "off") ? "files" : "files dns" }

to

hosts:      { ($AccessType eq "off") ? "files" : "files dns wins" }

and save the file (ctrl-x, Y)

To make all become functional you only have to do 1 more thing:

Code: [Select]

/sbin/e-smith/expand-template /etc/nsswitch.conf

Harro

[byte]

Have you raised a NFR ? Also what makes you think SME isn't aware of windows networks ? Thanks.

[Confucius]

I was thinking about the NFR possibility but didn't think it would be that much of a problem when it's not default.
Furthermore this is mostly related to servers that are set up without being a PDC or at least don't provide DHCP to the clients. That's where the awareness 'problem' is caused I think.

I didn't suggest SME is not aware of windows network. I only noticed it could become more aware.

[cactus]

hosts:      { ($AccessType eq "off") ? "files" : "files dns wins" }

What kind of windows systems are we talking about? AFAIK wins resolution is something from the stoneage and only neccesarry for NT based systems and by this I mean NT 4.0 and lower, W2000, WXP and even W98 I guess should not need this AFAIK (see also: http://en.wikipedia.org/wiki/Windows_Internet_Name_Service)

[Confucius]

We're talking about a situation like :

SME as Member server/gateway in a Windows 2003 Network with XP SP2 clients.

Since I'm not the super-guru I'd like to be I concluded that this was the solution for my situation. Now I can run different network related linux tools by simply using the machine-name assigned in windows (not by DHCP)

In case there is a better solution... I'm open to suggestions.

Harro