Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: Scott Lewis on February 02, 2002, 12:20:39 PM
-
I have installed v 5.1.2, and have configured everythink like my setup on v5.0.
Now, I use DHCP to set an IP address for the PC on my home network, as the e-smith server is on 24/7.
Now, I have noticed, everytime I boot up the pc attached to the server, the e-smith server DOES not allocate a ip address. The only way to get it to allocate one is to reboot the server.
Any ideas on what maybe wrong.
Scott
PS> What has happened to the command - samba restart
It no longer seems to work?
-
I have this same problem. IT is very annoying
-
Read this thread and look for my response...
http://forums.contribs.org/index.php?topic=3267.msg11033#msg11033
-
I looked at the thread but no reel work through's. I also run Win XP Pro on my client PC's.
When I boot that PC, I get the error when I type ipconfig in a command prompt:-
Media State Unallocated (or something similar).
No matter what I do, eg ipconfig /renew or try and repair the connection, no way can I get the DHCP server to allocate me a IP address.
I have tried again with a fresh install no joy, even updated the dhcp with dhcp-3.0-6.i386.rpm but still no joy.
Any ideas,
Scott
-
Did you try to release all the IP's, don't do anything else (don't try to renew), and then reboot? Always works for me. What does /var/log/messages look like?
-
Yep, tried releasing ip's , and then rebooting. On reboot, no ip allocated.
I checked the var/log messages file, nothing in there to tell me there is an error.
I have reported this to the bugs department, and they have confirmed, it is a bug and they are going to lok into it, as they have also got the error on their pc's.
I will hold on for a few more days to see if it gets fixed, otherwise, I will go back to v5.0.
Scott
-
Any news on a fix for the DHCP issue yet - especially as bugs dept have found the issue with some of their PC's running Win XP.
I have temporary gone back to v5.0.3 that works great.
Scott
-
Hi Scott,
if you hear of a fix/update please pass it on. I'm having the same problem (after upgrading from 4.1.2). Have a mix of Win98, Win2k & Linux boxes (some of the Win98 PC's were OK UNTIL I realease their IP's and tried to renew....).
Have reverted to fixed IP's (a real pain) for now.
Trevor B
Scott Lewis wrote:
>
> Any news on a fix for the DHCP issue yet - especially as
> bugs dept have found the issue with some of their PC's
> running Win XP.
>
> I have temporary gone back to v5.0.3 that works great.
>
> Scott
-
The only way I got it to work is to upgrade from v5.0.3 to v5.1.2. A clean install of 5.1.2 does not work.
When you say you upgraded, I agther you missed upgrading to v5.0.3.
I would suggest do a backup of e-smith. Install v5.0.3, and then restore the files. Then do an upgrade to v5.1.2. This is the way I did it.
Hope this helps.
Scott
-
To close my issue out....
I removed all of the MASQ custom templates that I had (a full copy & then just changed 1 to fix a VPN issue - which is fixed in v5 anyway), and did:
/sbin/e-smith/signal-event remoteaccess-update
and for good measure
/sbin/e-smith/signal-event post-upgrade
All is working fine now (including my VPN into work).
Trevor B