Koozali.org: home of the SME Server
Contribs.org Forums => General Discussion => Topic started by: paradigm on October 21, 2009, 09:34:01 PM
-
Sme is setup a server only and getting an ip address from an sbs 2003 server acting as a dhcp server ,
I can log on to the server manager from inside the network and also ssh to it from inside the network too ,
But it doesn't show in the sbs 2003 address leases and causes problams when trying to access sme from outside
The network (using mail , ftp , and ldap directory).
I think because the sbs2003 dhcp server doesnot show the ip address of sme server requests from outside do
not reach it .
Doing an nslookup command with the sme server's name in the sbs 2003 machine gives errors and doesn't resolve
thanks in advance.....
-
Sme is setup a server only and getting an ip address from an sbs 2003 server acting as a dhcp server ,
I think that unlikely, because SME server in server only mode has no option to be a DHCP client.
But it doesn't show in the sbs 2003 address leases and causes problams when trying to access sme from outside
This forum probably won't be very useful for investigating M$ SBS 2003 problems.
-
I think that unlikely, because SME server in server only mode has no option to be a DHCP client.
Should i use sme in server and gateway mode ?
I would like to use sme server for ftp email and ldap directory and leave dhcp to the sbs 2003 server
-
I would like to use sme server for ftp email and ldap directory and leave dhcp to the sbs 2003 server
no, you need only to assign a fixed ip address to SME and modify your windows' dns.
I would also suggest you to improve your network knowledge, because IMO you are playing with things and tools you don't know..
obviously, it's only a suggestion
-
Problem solved :
The guy who opened the ports on the router forgot to set rules on the firewall , now every thing works .
no, you need only to assign a fixed ip address to SME and modify your windows' dns.
I found a better way of dealing with dns problems an non windows clients , look here :
http://anothersysadmin.wordpress.com/2007/10/25/windows-2003-dhcpdns-server-and-non-windows-clients/
I would also suggest you to improve your network knowledge, because IMO you are playing with things and tools you don't know..
obviously, it's only a suggestion
Thank you for deciding for me what i know and don't know.....
-
Problem solved :
The guy who opened the ports on the router forgot to set rules on the firewall , now every thing works .
good
I found a better way of dealing with dns problems an non windows clients , look here :
http://anothersysadmin.wordpress.com/2007/10/25/windows-2003-dhcpdns-server-and-non-windows-clients/
interesting.. interesting enough to see that even simple tasks on M$ sw are difficult :-)
Thank you for deciding for me what i know and don't know.....
I apologize
-
No harm done , thanks for your help.