I had a similar-sounding problem once. The LAN had a W2K-server domain controller, mix of W2K and XP workstations, FreeBSD file servers. After modifying some samba configurations, W2K clients continued to function without issue - but XP clients couldn't resolve the hostname of the fileserver (accessing by IP worked fine). In my case restarting all the samba services on the fileserver corrected the issue.
Before I tried restarting the services - I had begun to suspect it was something to do with netbios and whatever default order XP uses to resolve hostnames. Building a netbios hosts file and using the '-H <netbios hosts file>' option in the script that runs nmbd on your samba DC might do the trick. If not - at least it's easy to try ;) Dana Harding ----- Original Message ----- I have a school with a few hundred WinXP Pro systems. They are all on a Samba domain controlled server for authentication and home directories. It works great except for some reason some names will not resolve. I am using IPcop to set hostnames for static systems on the network. IPcop is the DNS server for the network. If IPcop knows the name and IP of a local system it will resolve that IP. All the Linux workstations resolve all names correctly but it seems like Windows will not resolve a hostname unless there is a Samba server running on it. That is really stupid and what I would expect from Microsoft but not helpfull at all. I have servers that privoleged staff need to access from WinXP via Firefox and don't know squat about Windows so I would like if someone could help me figure out what is wrong with it, all joking aside.
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
