Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: Jake on March 26, 2000, 09:56:19 AM

Title: unable to log on to @home network
Post by: Jake on March 26, 2000, 09:56:19 AM
I am using e-smith 4.0b3(Started outwith 3.1 but when I could not get this to work I went to 4.0).  My internal network is fine.  I can see my e-smith server just fine from all of my computers.  I have tried using both DHCP and a static ip address in the setup.  Both have failed.  When I use DHCP with my @home host name I get a time out saying that a vaild DHCP response was not made.  When I try a static ip address everything apears to be fine but the internet connection does not work.  Any ideas?  I am sure that I am using the right nics for the right connection and that they are both good.  I have even tried changing the settings so my internal network runs on eth1 instead of eht0.  This internal network was fine once I switched the network cables but no luck with @home.  I am currently using a linux box as a router that logs in to the @home using DHCP just fine.  I would like to swith to e-smith.

Thanks in advance
Title: RE: unable to log on to @home network
Post by: cOz on March 27, 2000, 12:46:45 AM
I'm having the same problem, I think it has to do with certian ports being blocked at the modem. I have a friend that works for @Home whom I will ask about which ports are blocked. please let me know if you find the answer, and I'll do the same.

cOz
Title: RE: unable to log on to @home network
Post by: Charlie Brady on March 27, 2000, 07:38:01 AM
Jake wrote:

> I am using e-smith 4.0b3(Started outwith 3.1 but when I could
> not get this to work I went to 4.0).  My internal network is
> fine.  I can see my e-smith server just fine from all of my
> computers.  I have tried using both DHCP and a static ip
> address in the setup.  Both have failed.  When I use DHCP with
> my @home host name I get a time out saying that a vaild DHCP
> response was not made.  When I try a static ip address
> everything apears to be fine but the internet connection does
> not work.  Any ideas?

Grab the latest update to the e-smith-base RPM. Joseph Morrison did a lot of work to get e-smith working correctly with @home and he'd be quite disappointed if you still have a problem with the latest update. Give it a go, and let us know how you get on.

Charlie
Title: RE: unable to log on to @home network
Post by: Paddy Verberne on March 28, 2000, 01:21:05 AM
Guys,

I've replied to this list before with a very short but for me successful list of things to do when installing E-smith 3.1 using @home. It works 100% for me (thanks people at E-smith). I'll repeat the procedure:

1. Install E-smith 3.1;
2. Replace the original dhcpcd in /sbin with the latest stable version you can get (e.g. at http://www.phystech.com/download/);
3. Configure everything and in the name and domain settings tab type
    System name: your computer name as defined at @home (e.g. cp12352-a)
    Domain name: default domain for your @home pc (e.g. amst.nh.nl.home.com)
    Windows workgroup: your computer name as defined at @home (e.g. cp12352-a)
    Windows server name: your computer name as defined at @home (e.g. cp12352-a)

That should do the trick. I've done this several times now and it never failed!!!!

Happy hunting.

Paddy
Title: RE: unable to log on to @home network
Post by: Paddy Verberne on March 28, 2000, 01:21:08 AM
Guys,

I've replied to this list before with a very short but for me successful list of things to do when installing E-smith 3.1 using @home. It works 100% for me (thanks people at E-smith). I'll repeat the procedure:

1. Install E-smith 3.1;
2. Replace the original dhcpcd in /sbin with the latest stable version you can get (e.g. at http://www.phystech.com/download/);
3. Configure everything and in the name and domain settings tab type
    System name: your computer name as defined at @home (e.g. cp12352-a)
    Domain name: default domain for your @home pc (e.g. amst.nh.nl.home.com)
    Windows workgroup: your computer name as defined at @home (e.g. cp12352-a)
    Windows server name: your computer name as defined at @home (e.g. cp12352-a)

That should do the trick. I've done this several times now and it never failed!!!!

Happy hunting.

Paddy
Title: RE: unable to log on to @home network
Post by: cOz on March 29, 2000, 11:05:03 AM
Once I installed 4.06b everyting worked fine (even the @Home DHCP)
Now I have to try to get my own mail server working and forget about that !@#%^& @home mail service - but that's another story.

P.S. Mac, BeOS, and Win3.11 are also quite happy with all services !!

what a great product !

cOz