Topic: SME as DHCP client

[alfblack]

Greetings!

We have an existing network and I wanted to plug in SME. We have a separate DHCP server but SME didnt give the option of being a DHCP client.

So I plugged in a ip that is not yet in use (pinged it on a diffrent machine).

After the install. I couldnt ping the SME server and the SME didnt have access to the outside world.

Tried issuing the command ifconfig eth0 -dynamic up with no avail.

Any suggestions? Advice? pointers? TIA.

[cactus]

Greetings!

We have an existing network and I wanted to plug in SME. We have a separate DHCP server but SME didnt give the option of being a DHCP client.

So I plugged in a ip that is not yet in use (pinged it on a diffrent machine).

After the install. I couldnt ping the SME server and the SME didnt have access to the outside world.

Tried issuing the command ifconfig eth0 -dynamic up with no avail.

Any suggestions? Advice? pointers? TIA.

you should be able to configure your server with a DHCP address on the outside interface. When you try to setup your machine you are asked for a lot of settings, right after the screen for External Access Mode you are given the option to specify IP settings for the external IP settings (this goes fo rmy machine which is configured to be a dedicated gateway, I don't know how it reads for other otions such as server only mode). You can choose from the following:[list=1]

• Use DHCP (send account name as client identifier)
• Use DHCP (send ethernet address as client identifier)
• Use PPP of Ethernet (PPPoE)
• Use static IP address[/list:o]One of the first two should be suitable for you.

[CharlieBrady]

you should be able to configure your server with a DHCP address on the outside interface.

That's only useful if you have an outside interface. In server-only mode you do not.

So I plugged in a ip that is not yet in use (pinged it on a diffrent machine).

After the install. I couldnt ping the SME server ...

That indicates a connectivity problem somewhere. "netstat -i" will show you whether the server has actually seen any packets. "arp -a" will tell you which local machines have sent traffic that the server is able to see.

I doubt that using DHCP would have helped you (as long as you typed correctly) but you can temporarily try DHCP by doing:

ifdown eth0
dhclient eth0

[alfblack]

Greetings!

Man thanks for the replies. Sorry for the late one.

Wow CharlieBrady, you just showed me many commands I never used. I'll check those out.

Well, the machine is working find now. It took a bit more time before it could ping and be pinged.

So things are now good.