Koozali.org: home of the SME Server

Problems accessing @home Network

Jon Davis

Problems accessing @home Network
« on: March 12, 2000, 01:05:21 AM »
I have very easily installed the e-smith gateway v3.1. Wow how nice. I set it for a static IP
and hardcoded the other variables. I am using dual ethernet controllers and everything was found
automatically.

I can browse the web and can get to outside mail servers. I am using this as a home-based "firewall"
and proxy server for my multiple machines in my house.

However, when I try get at the private @home content that is usually located at "http://www", it
does not work. I cannot also get my mail which has the incoming and outgoing mail server set to
"mail"

Because I am not using this for business I don't have a domain name assigned to me or my company.

Should I put a specific domain name into one of the fields. I set the e-smith console "Web Server Name" to the
name of 192.168.1.1.

my machine name for @home has always been c63556-a. When you add in the domain information, the final
name ends up being c63556-a.brln1.ct.home.com.

Any suggestions would be appreciated.

Charlie Brady

RE: Problems accessing @home Network
« Reply #1 on: March 12, 2000, 04:32:17 AM »
Jon Davis wrote:

> However, when I try get at the private @home content that is
> usually located at "http://www", it does not work. I
> cannot also get my mail which has the incoming and outgoing
> mail server set to "mail"
...
> Should I put a specific domain name into one of the fields. I
> set the e-smith console "Web Server Name" to the name
> of 192.168.1.1.
>
> my machine name for @home has always been c63556-a. When you
> add in the domain information, the final name ends up being
> c63556-a.brln1.ct.home.com.

Your problem is misleading information from @home. The "www" and "mail" specifications are just shortcuts for "www in the default domain"
and they shouldn't be expecting you to have the same default domain
as everyone else. The information they give you with the account
will tell you somewhere what the correct default domain is - you will find that "www.cr.home.com" or something similar will work. Ditto for
"mail" etc.

Let us know how you get on.

Charlie

Justin

RE: Problems accessing @home Network
« Reply #2 on: March 12, 2000, 06:29:40 AM »
All you have to do is call your local @home support desk and ask them for the closest mail server to yourself. They usually will have no problem giving it to you. Charlie is right about the shortcuts they are using for the default settings.

Jon Davis

RE: Problems accessing @home Network
« Reply #3 on: March 12, 2000, 10:32:53 PM »
Thanks for your help. I fixed it from your hints. Since my machine name was c63556-a.brln1.ct.home.com, I made my default home page to be "www.brln1.ct.home.com" and and my mail SMTP and POP3 servers to "mail.brln1.ct.home.com". That pretty much seems to solve my problem. The javascript that controls whether or not the @home service recognizes me needed to be reset but seems to be working.

I also had to set my connection from being routed throught the @home proxy to a "Direct" connection. I will assume that I might get slower access now though.

Paddy Verberne

RE: Problems accessing @home Network
« Reply #4 on: March 17, 2000, 07:06:22 PM »
Guys,

Why choose a work-around when you can achieve the same result as those poor guys which don't use e-smith.

Try the following

System name:  CP347834-a (your hostname)
Domain name:  dbsch1.nb.nl.home.com (my default domain, change it to match yours)
Windows workgroup:  CP347834-a (your hostname)
Windows server name:  CP347834-a (your hostname)

When you have done this, let e-smith provide you with DHCP for your workstations. It may be possible that the standard DHCP-client which wants to obtain it's IP-address from an @home server doesn't work properly. Just replace the default DHCPCD in /sbin with a new one that you can download and compile. That should do the trick.

Now you should be able to use www, mail, news etc., etc... without any problems. Works for me!!!!!

Paddy Verberne

cliff miller

RE: Problems accessing @home Network
« Reply #5 on: May 11, 2000, 06:26:49 PM »
An idea to get the domain suffix information necessary to setup firewall / proxy servers - sybergen (Sygate) support site offers some cgi code to do this - the link is

http://www.sybergen.com/support/answers.htm#29

Perhaps e-smith could set up a similar page?

Thanks for a wonderful product!

- - - Cliff