Koozali.org: home of the SME Server
Obsolete Releases => SME Server 9.x => Topic started by: beek on December 15, 2014, 04:50:28 PM
-
hello,
in my network, I do not see the sme server. :(
i see all other computers in the network.
try to connect with windows 7 and the firewall is off
SME server is set to Gateway and server.
Workgroup settings.
Windows Workgroup name = beek
server name = server
Workgroup and Domain Controller = No
Roaming profiles = No
Erik
-
hi, welcome here
please give us as many details as you can..
start telling us something about lan/wan conf in your server and clients, thank you
-
Networking Parameters sme server
Server Mode servergateway
Local IP address / subnet mask 192.168.2.1/255.255.255.0
External IP address / subnet mask 192.168.1.201/255.255.255.0
Gateway 192.168.1.1
Additional local networks 192.168.2.0/255.255.255.0
DHCP server enabled
Beginning of DHCP address range 192.168.2.65
End of DHCP address range 192.168.2.75
Server names
DNS server 192.168.2.1
Web server www.erik.loc
Proxy server proxy.erik.loc:3128
FTP server ftp.erik.loc
SMTP, POP, and IMAP mail servers mail.erik.loc
Windows settings.
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : 192.168.2.1
IPv4 Address. . . . . . . . . . . : 192.168.2.69
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
-
Can you connect to the server directly by IP address? Try doing start > run > \\192.168.2.1
-
no
network error
windows cannot access \\192.168.2.1
-
my smb.conf
#------------------------------------------------------------
# !!DO NOT MODIFY THIS FILE!!
#
# Manual changes will be lost when this file is regenerated.
#
# Please read the developer's guide, which is available
# at http://www.contribs.org/development/
#
# Copyright (C) 1999-2006 Mitel Networks Corporation
#------------------------------------------------------------
[global]
add machine script = /sbin/e-smith/signal-event machine-account-create '%u'
bind interfaces only = yes
case sensitive = no
deadtime = 10080
display charset = ISO8859-1
dns proxy = no
domain logons = no
domain master = no
dos charset = 850
encrypt passwords = yes
guest account = public
guest ok = no
hosts allow = 127.0.0.1 192.168.2.0/255.255.255.0
interfaces = 127.0.0.1 192.168.2.1/255.255.255.0
log file = /var/log/samba/log.%m
logon drive = Z:
map to guest = never
max log size = 50
name resolve order = wins lmhosts bcast
netbios name = vuurmuur
oplocks = true
kernel oplocks = true
level2 oplocks = true
os level = 35
passdb backend = smbpasswd:/etc/samba/smbpasswd
pid directory = /var/run
preferred master = auto
preserve case = yes
private dir = /etc/samba
security = user
server string = SME Server
short preserve case = yes
smb passwd file = /etc/samba/smbpasswd
smb ports = 139
socket options = TCP_NODELAY
strict locking = no
unix charset = UTF8
unix password sync = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
check password script = /sbin/e-smith/samba_check_password
unix extensions = no
wins support = no
workgroup = erik
printcap name = /etc/printcap
load printers = yes
printing = lprng
print command = /usr/bin/lpr -b -h -r -P%p %s
-
Can you ping the server from the Windows 7 PC?
From the command prompt:
ping 192.168.2.1
-
yes i can ping it and connect trough ssh (putty)
-
Can you check your workgroup settings? In your first post you have your workgroup listed as beek, but in your smb.conf it is listed as erik.
-
both setting are now on erik and still not working
-
i build a new machine and this is working good.
so witch files do i need to copy to the old one so that the okd machine is working
-
can you tell us more, does your first server is done from a backup of sme8, does the second is installed without backup????
If the second is ok, the first should do.
Of course you have reconfigured your server
signal-event post-upgrade; signal-event reboot
-
beek
i build a new machine and this is working good.
So the problem is not with SME server, but more likely your configuration.
Please show us the same configuration settings for your new server as you have shown us for your original server (ie all the settings from the Configuration panel in server manager & smb.conf etc) and we may be able to spot where you have gone wrong.
I would ask you to describe your network setup more thoroughly
ie
do you have other servers on the LAN ?
is there a Windows server ?
do you have a seperate gatewall firewall device or are you using a bridged modem attached to the SME server ?
What mode is your SME server in , server only or gateway server mode ?
One odd thing I notice in your original settings is that you have a gateway specified that is on a different IP range (192.168.1.1) than the LAN IP for the server & the gateway specified in your workstations (both set as 192.168.2.1). That does not necessarily make sense as you say the first server is set in server gateway mode so the gateway & SME server IP should be the same (192.168.2.1), unless perhaps you have a static IP setup with a DMZ.
so witch files do i need to copy to the old one so that the okd machine is working
It is not that simple with SME server, copying & replacing selected config files will most likely mess up your server. You could do a complete backup & restore but that will transfer all the same settings & you will end up with the same issue.
One last possibility, after changing the workgroup name did you restart all servers & workstations on your network, allowing SME server to boot up fully BEFORE starting other workstations (& servers if any) ?
You need to provide more information as mentioned above in order for us to resolve your configuration issues.
-
One odd thing I notice in your original settings is that you have a gateway specified that is on a different IP range (192.168.1.1) than the LAN IP for the server & the gateway specified in your workstations (both set as 192.168.2.1). That does not necessarily make sense as you say the first server is set in server gateway mode so the gateway & SME server IP should be the same (192.168.2.1), unless perhaps you have a static IP setup with a DMZ.
The default gateway specified on his workstations is 192.168.2.1, which is the internal LAN adaptor of the server (which is in servergateway). The external LAN adaptor has a gateway of 192.168.1.1. It looks like it is a test machine set up on an internal network to me.
-
i got one server and that is the sme server and there are 2 windows 7 workstations en some nas disks and a media player in my network.
on both servers is a fresh install without restoring
after the server/gateway i have a router from my isp.
what have te settings from the router to do with not seeing the server in the network environment.
the gateway is on the sme server and routing to the isp route (192.168.1.1)
network setting first server (not working):
Networking Parameters
Server Mode servergateway
Local IP address / subnet mask 192.168.2.1/255.255.255.0
External IP address / subnet mask 192.168.1.201/255.255.255.0
Gateway 192.168.1.1
Additional local networks 192.168.2.0/255.255.255.0
DHCP server enabled
Beginning of DHCP address range 192.168.2.65
End of DHCP address range 192.168.2.75
Server names
DNS server 192.168.2.1
Web server www.erik
Proxy server proxy.erik:3128
FTP server ftp.erik
SMTP, POP, and IMAP mail servers mail.erik
second server (working):
Networking Parameters
Server Mode servergateway
Local IP address / subnet mask 192.168.2.2/255.255.255.0
External IP address / subnet mask 192.168.1.201/255.255.0.0
Gateway 192.168.1.1
Additional local networks 192.168.2.0/255.255.255.0
DHCP server disabled
Server names
DNS server 192.168.2.2
Web server www.erik
Proxy server proxy.erik:3128
FTP server ftp.erik
SMTP, POP, and IMAP mail servers mail.erik
-
i got one server and that is the sme server and there are 2 windows 7 workstations en some nas disks and a media player in my network.
Thank you.
second server (working):
Networking Parameters
Server Mode servergateway
Local IP address / subnet mask 192.168.2.2/255.255.255.0
External IP address / subnet mask 192.168.1.201/255.255.0.0
Gateway 192.168.1.1
Additional local networks 192.168.2.0/255.255.255.0
DHCP server disabled
Server names
DNS server 192.168.2.2
Web server www.erik
Proxy server proxy.erik:3128
FTP server ftp.erik
SMTP, POP, and IMAP mail servers mail.erik
OK, when this second server is connected, and assuming that the first one is not, and you have rebooted all workstations, what are the Windows configurations of the workstations please?
-
Why are the external IP addresses on both servers the same?
During boot of the seconday server that you boot, you missed the warning that the IP address of the external IP is already taken.
-
thats the ip connecting to the router from the isp
and on the second one that worked is no connection to the router from the isp
-
thats the ip connecting to the router from the isp
and on the second one that worked is no connection to the router from the isp
I don't understand, all IP's must be different, and why have a server gateway if it's not onnected with the external interface to something?
-
Beek,
To really work out what is going on we need only one server connected at a time. So can I ask you to try the following please:
1. Connect server 1 to your router via the external ethernet adaptor, and then connect it to your internal network using the internal network adapter. Reboot the workstations and see if you can ping the server, and if you can see the server on the windows network. Please post up details of server configuration, and of your Workstation configuration, including workgroup please.
2. Disconnect server 1 completely from both the internal network and external network. Connect server 2 to your router via the external adaptor, and then connect it to your internal network using the internal network adapter. Reboot the workstations and see if you can ping the server, and if you can see the server on the windows network. Please post up details of server configuration, and of your Workstation configuration, including workgroup please. I noticed that server 2 does not have dhcp enabled, so unless you have another dhcp server on your internal network you will need to reconfigure the server first.
Please report back with your findings. Thank you.
-
i have tested the server one at the time.
server 1.(the old one)
i can ping it and not visable)
workgroup = beek
internal ip adres is 192.168.2.1
netmask 255.255.255.0
external ip adress = 192.168.1.201
netmask 255.255.255.0
default gateway 192.168.1.1
Workstation
workgroup = beek
internal ip adres is 192.168.2.24
netmask 255.255.255.0
default gateway 192.168.2.1
server 2.(the new one)
i can ping it and visable)
workgroup = beek
internal ip adres is 192.168.2.2
netmask 255.255.255.0
external ip adress = 192.168.1.201
netmask 255.255.255.0
default gateway 192.168.1.1
Workstation
workgroup = beek
internal ip adres is 192.168.2.24
netmask 255.255.255.0
default gateway 192.168.2.2
-
OK, thank you for that information. On server 1, is DHCP enabled, and if so, what is the DHCP range? If it is as you stated in an earlier post, the IP address of your workstation is outside this range. That is not a problem in itself, but I would like to know where your workstation is getting the IP address of 192.168.2.24 from.
Similarily, on server 2, is DHCP enabled and if so, what is the DHCP range?
Finally, if you run ipconfig /all on your workstation, what DHCP server is listed, and what DNS server is listed please?
Thank you.
-
dhcp is enabled range 2.65 to 2.75
i dont use the dhcp on the workstation
workstation = 2.20
dhcp server = 2.1
dns server = 2.1
-
dhcp is enabled range 2.65 to 2.75
i dont use the dhcp on the workstation
workstation = 2.20
dhcp server = 2.1
So you have a static IP for the workstation? What about when the second server is attached? What is the output from ipconfig /all?
The reason I ask all these questions are:
1. The obvious difference between the two servers is that one is acting as a DHCP server, the other is not.
2. You appear to be using a static IP on the workstations, and I don't know whether you change the workstation settings when you change servers for testing
3. The static IP you gave for your workstation this time (2.20) is different from the one in your last post (2.24). I assume this is because it is a different workstation, but it would make things easier if you used the same workstation for all testing.
-
i will go build a new one
-
ok i have build or used the new one now.
but cannot understand why the old one is not working.
Can ping both servers
the only strange thing is that on the old server there are no netbios name or group to see with advanced ip scanner
SME 9 32 bits (old one)
Widows workgroup beeksplace
Servername Firewall2
Workgroup and Domain Controller No
Roaming profiles no
Networking Parameters
Server Mode servergateway
Local IP address / subnet mask 192.168.2.2/255.255.255.0
External IP address / subnet mask 192.168.1.202/255.255.255.0
Gateway 192.168.1.1
Additional local networks 192.168.2.0/255.255.255.0
DHCP server disabled
Server names
DNS server 192.168.2.2
Web server www.beeksplace
Proxy server proxy.beeksplace:3128
FTP server ftp.beeksplace
SMTP, POP, and IMAP mail servers mail.beeksplace
Domain information
Primary domain beeksplace
Virtual domains
beeksplace
Primary web site http://www.beeksplace
Server manager https://firewall2/server-manager/
User password panel https://firewall2/user-password/
Email Addresses useraccount@beeksplace
firstname.lastname@beeksplace
firstname_lastname@beeksplace
config show SystemName
SystemName=firewall2
config show smb
smb=service
DeadTime=10080
KeepVersions=disabled
OpLocks=enabled
OsLevel=35
RecycleBin=disabled
RoamingProfiles=no
ServerName=Firewall2
ServerRole=WS
ShadowCount=10
ShadowDir=/home/e-smith/files/.shadow
UnixCharSet=UTF8
UseClientDriver=yes
WINSServer=192.168.2.1
Workgroup=sme-server
status=enabled
Advanced IP scanner
Server the old one
Naam Johan2 (is a name from a web domain)
Ipv4: 192.168.2.2
Netbios-name: is blank
Netbios-group: is blank
SME 9 64 bits (the new one)
Widows workgroup beeksplace
Servername Firewall
Workgroup and Domain Controller No
Roaming profiles no
Networking Parameters
Server Mode servergateway
Local IP address / subnet mask 192.168.2.1/255.255.255.0
External IP address / subnet mask 192.168.1.201/255.255.255.0
Gateway 192.168.1.1
Additional local networks 192.168.2.0/255.255.255.0
DHCP server enabled
Beginning of DHCP address range 192.168.2.65
End of DHCP address range 192.168.2.75
Server names
DNS server 192.168.2.1
Web server www.beeksplace
Proxy server proxy.beeksplace:3128
FTP server ftp.beeksplace
SMTP, POP, and IMAP mail servers mail.beeksplace
Domain information
Primary domain beeksplace
Virtual domains
Primary web site http://www.beeksplace
Server manager https://firewall/server-manager/
User password panel https://firewall/user-password/
Email Addresses useraccount@beeksplace
firstname.lastname@beeksplace
firstname_lastname@beeksplace
config show SystemName
SystemName=firewall
config show smb
smb=service
DeadTime=10080
KeepVersions=disabled
OpLocks=enabled
OsLevel=35
RecycleBin=disabled
RoamingProfiles=no
ServerName=firewall
ServerRole=WS
ShadowCount=10
ShadowDir=/home/e-smith/files/.shadow
UnixCharSet=UTF8
UseClientDriver=yes
Workgroup=beeksplace
status=enabled
Advanced IP scanner
Naam Firewall
Ipv4: 192.168.2.1
Netbios-name: Firewall
Netbios-group: Beeksplace
Workstation 1
Ipv4: 192.168.2.20
Ipv4 subnet: 255.255.255.0
Ipv4 default gateway: 192.168.2.1
Ipv4 DNS server: 192.168.2.1
Netbios over TCIP: yes
Workstation 2
Ipv4: 192.168.2.24
Ipv4 subnet: 255.255.255.0
Ipv4 default gateway: 192.168.2.1
Ipv4 DNS server: 192.168.2.1
Netbios over TCIP: yes