Koozali.org: home of the SME Server

Internal IP address problem

ferretboy

Internal IP address problem
« on: December 16, 2005, 01:25:27 AM »
Hi everyone

Right, before I start, let me explain that I am a total SME noob (although I have been reading these forums for ages), and as such I may need things explaining to me in rather basic terminology (I am confortable with computing and *nix terms though...)

I have decided to setup an SME server in my home office to supply email, PDC and file sharing services to my computer systems. The server is setup in 'server only' mode, as I already have a router providing gateway, DHCP and firewall functions and is situated behind this router - on my LAN.

The problem I have is with assigning the servers internal IP address. My router has the option to either assign using DHCP or SDHCP (static DHCP, where I provide the MAC address of the system and the router automatically gives that system the same local IP each time). My other computer systems are automatically assigned a local address by DHCP in the range 192.168.0.100 - 192.168.0.199, however I have been unable to discover an option in the SME software to allow it to recieve a DHCP address - Is this possible? If not then my second option would be to use SDHCP to assign the same local address to the server each time (probably best) by giving the router the MAC address of the server NIC, but how do I determine the MAC address of the server NIC from within SME?

I have also tried giving the server (through the config system) a local address outside of the scope of my DHCP server (eg. 192.168.0.205 or 192.168.1.9) but I am still unable to access the server from other systems on the network...

Any idea's would be greatfully appreciated, as I really need to get this setup and at least supplying PDC functions ASAP.

Cheers

Marc Faulkner
_________________________________________
Marc Faulkner - "Accept me as I am, it is me, it is true and honest " - Jack Kramer

We make a living by what we get, we make a difference by what we give.

Offline timm

  • *
  • 14
  • +0/-0
    • http://www.dreyercycle.com
Internal IP address problem
« Reply #1 on: December 16, 2005, 01:59:58 AM »
I'm with 'ya..I LOVE the SME product.  Its great and I'd much rather give the community that developed this $$$ than the big Micro$oft.

I set up mine with a static IP on the network behind the router/firewall.  It works great with the exception of the mail issues I am working out.  The router has a limited range for DHCP, but the server is outside of that range.  I forward the needed ports to the server and it works great. I can use the domain name and it still works great when the DNS points it back to our LAN.

-Tim
...

ferretboy

Internal IP address problem
« Reply #2 on: December 16, 2005, 02:04:10 AM »
Hi Tim

I agree, I would much rather support an Open Source project than line Gates' pockets any more. You have your server setup exactly how I would like mine, but for some reason when I do that i can still not access the server from any client PC  :-(

Cheers though - at least I know it is possible  :-)

thethinman

Internal IP address problem
« Reply #3 on: December 16, 2005, 02:04:38 AM »
Hi Marc,
You should be able to set the server's IP address outside the scope of your router DHCP server.  You will run into problems if the SME server's DHCP server is also running which I believe is the default setup.  You need to turn off the SME DHCP server.

To determine your server NICs MAC/HW address just use the ifconfig command at the command prompt.  This will give you what you need.

ferretboy

Internal IP address problem
« Reply #4 on: December 16, 2005, 02:07:12 AM »
Thanks  :-)

I have already disabled the DHCP server in SME, but I reckon my problem probably lies with a setting on my router - I'll do a hard reset and try reconfiging it all. I don't mean to sound thick, but how do I access the command prompt from within SME?  :-?

Cheers again

thethinman

Internal IP address problem
« Reply #5 on: December 16, 2005, 02:15:49 AM »
Hi Marc,
You can access the command prompt or console very easily if you have a monitor and keyboard directly attached to the server.  It automatically boots to the console.

If you don't have a monitor and keyboard attached you can SSH into the server using an application like Putty.  You need to enable secure shell access in "remote access" section of server-manager web interface.  Of course, the first option might be your only choice if you can't access the server-manager panel.

ferretboy

Internal IP address problem
« Reply #6 on: December 16, 2005, 02:20:32 AM »
Cheers  :-)

I somehow missed the fact that it booted to the console  :roll:

Im just trying a few more ideas before I try SDHCP. I will let you know how I go on

Thanks for your help

thethinman

Internal IP address problem
« Reply #7 on: December 16, 2005, 02:28:27 AM »
Hi Marc,
If you login at the console with the admin username you can access the server configuration menu.  If you login with root username you get the command prompt.  They both use the same password.  You probably already know this but I thought I'd mention it just in case.

Good luck.

ferretboy

Internal IP address problem
« Reply #8 on: December 16, 2005, 02:40:45 AM »
Thanks  :-D

Problem solved!!!

How embarrasing, I hadn't plugged the server into the router! :roll:  :lol: )

Thanks for all of your help anyway, I owe you a  :pint: