Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: staverts on March 03, 2006, 01:54:04 AM
-
I am a newbie to SME 7, at home I have a server running as my server and gateway. I set up sme to be a domain controller, and easily registered my PC's to the domain, and logged into my created account. I also have netlogon.bat working beutifully (because of this forum) :)
I have now set up SME at work to show my boss, unfortunately, when it can to registering the Windows XP SP2 workstation to the domain, ot coulsd not find the domain. My assumption was that it could not be resolved on the network. At home the SME 7.0 is my server and gateway, and work it is just a stand alone server, that prvides file sharing etc, not the computers DNS, gateway, DHCP settings etc. What I did first was to try and point the hosts file of the windows XP machine to the SME 7.0 server, exmaple:
HOSTS FILE:
---------------
199.xxx.xxx.xxx smegroup <----This is the Domain Name
It can resolve the name, as I can ping smegroup, and it responds to the proper server IP.
Unfortunately the workstation could sitll not see the server or domain to log into. My next question would be, do I need to add a wins server to the machine? Will this allow me to register the computer. I notived on my PC at home, it adds a WINS server from DHCP. I imagine I may still need the Windows Internet Name service, is this correct? I thought DNS would be enough, but then again, I'm pretty new to Samba, besides some tinkering.
Thanks in advance,
Matt
-
Windows uses two files: HOSTS and LMHOSTS.....often they can be ignored, but sometimes you need to resolve a windows networking problem (which I am pretty sure is what you have) using HOSTS and sometimes LMHOSTS.
HOSTS just maps IP address and windows hostnames. The example file I have is from an old Win98 setup I used to have:
=======================
#hosts.sam
# Copyright (c) 1998 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP stack for Windows98
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
======================
My HOSTS file is
------------------------------
127.0.0.1 localhost
192.168.1.1 smeserver #files server
192.168.1.100 junglejim #jim's PC
192.168.1.102 dianapalmer #diana's PC
192.168.1.200 printserv #printerserver
------------------------------
Notice there is no DOMAIN NAME mentioned, just IP and windows host name.
LMHOSTS is where fancier stuff can be defined, especially to do with domains
The example is found in c:\windows\system32\drivers\etc and looks like this:
# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample LMHOSTS file used by the Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to computernames
# (NetBIOS) names. Each entry should be kept on an individual line.
# The IP address should be placed in the first column followed by the
# corresponding computername. The address and the computername
# should be separated by at least one space or tab. The "#" character
# is generally used to denote the start of a comment (see the exceptions
# below).
#
# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
# files and offers the following extensions:
#
# #PRE
# #DOM:<domain>
# #INCLUDE <filename>
# #BEGIN_ALTERNATE
# #END_ALTERNATE
# \0xnn (non-printing character support)
#
# Following any entry in the file with the characters "#PRE" will cause
# the entry to be preloaded into the name cache. By default, entries are
# not preloaded, but are parsed only after dynamic name resolution fails.
#
# Following an entry with the "#DOM:<domain>" tag will associate the
# entry with the domain specified by <domain>. This affects how the
# browser and logon services behave in TCP/IP environments. To preload
# the host name associated with #DOM entry, it is necessary to also add a
# #PRE to the line. The <domain> is always preloaded although it will not
# be shown when the name cache is viewed.
#
# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
# software to seek the specified <filename> and parse it as if it were
# local. <filename> is generally a UNC-based name, allowing a
# centralized lmhosts file to be maintained on a server.
# It is ALWAYS necessary to provide a mapping for the IP address of the
# server prior to the #INCLUDE. This mapping must use the #PRE directive.
# In addtion the share "public" in the example below must be in the
# LanManServer list of "NullSessionShares" in order for client machines to
# be able to read the lmhosts file successfully. This key is under
# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
# in the registry. Simply add "public" to the list found there.
#
# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
# statements to be grouped together. Any single successful include
# will cause the group to succeed.
#
# Finally, non-printing characters can be embedded in mappings by
# first surrounding the NetBIOS name in quotations, then using the
# \0xnn notation to specify a hex value for a non-printing character.
#
# The following example illustrates all of these extensions:
#
# 102.54.94.97 rhino #PRE #DOM:networking #net group's DC
# 102.54.94.102 "appname \0x14" #special app server
# 102.54.94.123 popular #PRE #source server
# 102.54.94.117 localsrv #PRE #needed for the include
#
# #BEGIN_ALTERNATE
# #INCLUDE \\localsrv\public\lmhosts
# #INCLUDE \\rhino\public\lmhosts
# #END_ALTERNATE
#
# In the above example, the "appname" server contains a special
# character in its name, the "popular" and "localsrv" server names are
# preloaded, and the "rhino" server name is specified so it can be used
# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
# system is unavailable.
#
# Note that the whole file is parsed including comments on each lookup,
# so keeping the number of comments to a minimum will improve performance.
# Therefore it is not advisable to simply add lmhosts file entries onto the
# end of this file.
NOTE: Microsoft give you HOSTS.SAM and LMHOSTS.SAM as examples. You modify them to suit your system and
****save them as HOSTS and LMHOSTS *****
(no .SAM extension) in the same place you find the LMHOSTS.SAM...there are slight differences between Win9x/2k/XP; do a search for LMHOSTS.SAM on your PCs.
The simplest setup, BTW, is to let SAMBA be PDC and WINS server and DHCP server, and then you don't need to bother with HOSTS and LMHOSTS. But, if you can't do that, then use HOSTS and LMHOST.
Hope this helps solve your problems and I am not stering you down the wrong rabbit hole!
Cheers
Ian
-
That IP address looks to be wrong for a lan?
From RFC1918 (http://rfc.net/rfc1918.html):
3. Private Address Space
The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:
10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
Check your ip addressing first.
If you don't want to switch to the SME for DNS then the next step would be to hardcode your IP settings on the pc to use the sme server for dns / wins. Its probably best to remove the host file entries you've made to reduce the possibility of conflicts/confusion.
There are special dns/wins entries for domain controllers to distinguish them as DCs rather than just hosts, you can make host file entries to force them if your dns/wins server doesn't know about the SME (brings me back to NT4 domains and wide area networks) but there is much more chance of just getting it wrong if you go down that route ....
HTH
David.
*edit* post collision - you take 10 minutes to write a post and then someone pips you! ;-)
-
The address in right, this server is on a 199.xxx.xxx.xxx public class C address. I cannot use this server for my DNS, as it is just a stand alone file server...am I wrong about this, please let me know, I am pretty new to the SME side of things.
-
SME has 2 interfaces, 1 for the dirty internet and 1 for the clean lan.
Different services are open to the different sides. You must have a 192.168.* or a 10.* or a 172.16.* that your PCs are using at the moment .... that where the LAN side of the SME needs to be connected.
The LAN side is where the 'windows domain' services are presented. You will not be able to operate a 'windows domain' style network with only public IP addresses, there has to be a private network too.
Please tell me you haven't told the SME that its only got the LAN interface and then pointed it at the internet ....... :-o
HTH
David.
-
Hi David, I do realize thatm thans for all your help. I am actually running SME 7.0 as a stand alone server. I resolved my issue. It was DNS/WINS. Since SME does have DNS set up, even as a stand alone server, and since we have it on one of our public Class C addresses (We do have an edge device over top of it in transparent mode) I decided to just use SME as my DNS. It works BEAUTIFUL, and we were looking to start running our own DNS server anyways, so it serves a two fold benefit, I am so HAPPY! I was able to join thje domain no problem after using the SME server as my WINS and DNS server, and it serves DNS BEAUTIFULLY!
Wow, this is such a great server package. It works Flassless with my hardware raid, and flawless with my built in DLT as well, bloody beautiful. I've basically easily replaced my novell server with this, and netlogon script are working BEAUTIFULLY with the instructions from this site. Thank-you everyone!
Matt
-
Hi Matt,
Please could you let me know how you configured your DNS server, in Server-Only mode?
Thanks,
Nigel.
-
Hi Sorry for the late replay. I setup the server as SERVER ONLY, and plugged in my open Class C address:
199.xxx.xxx.xxx
And put in my gateway address which was 199.xxx.xxx.9, when all was said and done, I rebooted.
I then on my WinXP client, plugged in my 199.xxx.xxx.xxx (server address for the DNS, and WINS)
the internet came rushing through.
Hope this helps, let me know if you want me to explain further.
Matt