Topic: Can't see Server from Windows network browse

[wibbly]

I have set up 6.0.1 as a stand-alone server (not gateway).

I have an ADSL NATing router providing Internet access, & a DHCP server, and DHCP serving is 'off' on e-smith.

My Windows workgroup name is OFFICE. There is no Windows domain controller or server machine on the network - it's all peer-to-peer, and seems to work fine.

I have a public dynamic DNS name also managed by the router. This is only used at the moment for access to a networked Webcam with a suitable port forwarded direct by the router.

The Windows client machines access their email direct via IMAP and POP3 servers out on the Internet. To start I want to introduce e-smith just to offer file and print server facilities to the existing Windows clients, and I'm trying to change as liite else as possible. Using e-smith as a staging post for email, or using it to provide some of the services offered by the router today, may come later.

Problem is that I can only seem to get the e-smith server from Windows client machines via the static IP address I've given it (outside of teh DHCP range), not by its server name, etc. Nor does the server appear in Windows Network Neiborhood. I think I'm confused about how I ought to be setting this all up anyway.

1. Given the config above, can someone give me an example, please, of entries I could be using on the e-smith server, and how these are used/become visible by the Windows client machines?

2. I was also a little confused by docs that seem to suggest that Windows (XP, for example) user login and passwords need to be synced with the user names and passwords on the e-smith server. Is this true? Isn't/can't the user just be prompted for his own name/password when he tried to use the e-mith server?

Any steer would be helpful. Or is there a "e-smith for Windows dummies" doc somewhere ?

W

[Reinhold]

...http://linux-newbie.sunsite.dk/index.html...

and (since you took dhcp and gateway away from SME .-)

YES to your no.2 question. In SME server-manager under  users, then workgroup:
- use the same username/password as in your XP clients when you register users.
- set "OFFICE" as the workgroup name

...it's a bit too much to explain in a post
but in addition to the above you might want to
grab a "samba for dummies" .-) ...
and use the "search" facility of this forum...

Anyway the 2 above should get you running
(for s*cking XP-Home you may have to search in addition )

Enjoy
Reinhold

[Brave Dave]

Just checking the obvious ...

The network/netmask is the same on the SME server

Are you running a firewall on your windows machine - trend pc-cillin and nortons avirus, for instance, installs firewalls which block netbios browsing

then you need to check the b-node setting - this will be issued by the dhcp server - needs to be set to resolve names by broadcast

can you ping the server by name ?

[wibbly]

YES to your no.2 question. In SME server-manager under  users, then workgroup:
- use the same username/password as in your XP clients when you register users.
- set "OFFICE" as the workgroup name

Thanks. This is odd though, as I think I did set the e-smith workgroup name to the same as the client machines. AH - the e-smith name is lower case now (seems it HAS to be?!), and the client machines all have the name in upper case. Maybe this is the problem

Client machines should be able see the e-smith server in Network Neiborhood, regardless of the users that have been configured, right?

W

[wibbly]

Just checking the obvious ...

The network/netmask is the same on the SME server

Are you running a firewall on your windows machine - trend pc-cillin and nortons avirus, for instance, installs firewalls which block netbios browsing

then you need to check the b-node setting - this will be issued by the dhcp server - needs to be set to resolve names by broadcast

can you ping the server by name ?

No firewall on the client machines. And all the Windows machines can see each other in Notwork Neiborhood. I can browse the server, and transfer files to it so long as I use its IP address. Will need to check the netmask. All clients are actually set to 10.10.10.x 255.255.255.0 and there are 5 client PCs in all.

Don't think I have a b-node setting in the DHCP server config. But it's not a DNS server. It just caches DNS requests it sees as they pass to the DNS server at my ISP.

I'll have to check if I can ping it the e-smith server by name. I suspect not, as if I use the browser in the Windows machine to admin the server, I have to put the IP address in there too. It doesn't resolve the name of the server.

With no local DNS server (except in the e-smith server??), and no custom hosts files everywhere, the Windows naming/resolving is done with WINS, isn't it? Can e-smith 'play' in a WINS environment?

W

[mark_53]

I am having the same problem in server only mode.  I'm using Win98 on the client side an esmith 6.0. Esmith is the dhcp server for the local network and a Linksys wireless router is the gateway to the internet with dhcp turned off.  At the DOS prompt I can ping the esmith by host name, but in Windows network neighborhood it doesn't show up.  If I try to "find computer" or "map network drive" by host name, it can't be found, but if I try the same thing with the local ip it works.  Only after the ip has been found I can map network drive by host name.

[wibbly]

My problem now solved. A typo in the workgroup name. Doh!

W