Topic: Two ISP's - Two servers in domain . . how ?

[wyron]

Hi all
I'm in the (happy) situation of having two ISP's, one through DSL and one through a cable modem.
I have a primary server-gateway working through the DSL with a fixed ip, thus administering my web, mail and file services. All working seamlessly for several years with appropriate upgrading (currently 6.0.1-01).
The need has arisen for utilization of the other connection, since I'm starting administration of an external community website, only reachable (for administration) through the cable-thingy.
So I've installed a second server-gateway for that purpose, with a separate workstation set up to use that connection (the workstation must of course, additionally,  be a member of my home-domain, since I use it for other purposes too). The second server doesn't need to be accessible from the internet.
Now for the problem:
It doesn't present itself to the domain even though the gateway service is up and working flawlessly.
Its internal setup is with a fixed address on the lan-subnet, and the name is yyy.ideast.dk where the primary server is xxx.ideast.dk.
When I try to connect to http://yyy/server-manager/ the explorer returns: No route. Server not found.

The solution is perhaps simple, but I haven't been able to find anything on contribs to cover the subject, so I'm at a loss.

[gbaird]

I am not quite sure how you have setup your network but
more info would help

both your computers running sme ?

you need to be on the same subnet - like 192.168.1.* or the 2 computers cannot see each other in YOUR network you will have to connect over the internet for administartion make sure remote access is turned on in server-manager then you can use

https://www.yourserver.com/server-manager note the HTTPS

If both computers are in server/gateway mode you can plug both
into a network switch and use either for internal computers to connect to the internet just adjust your gateway address
but make sure you use the same subnet on your internal nic
not required but gives you both computers on the same network
that way you can do your administration inside of your home network by just using the hostname or ip address

a picture is an easier way to show this setup

|---Server1----cable
|
|---Switch---any other computers
|
|---Server2---dsl  


hope this helps

[Boris]

Wyron,
One of your servers is acting as DHCP and perhaps name server (DNS, WINS). I would assume it is the first one, but if not, make adjustments to the next example.
Lets use those addresses: xxx.ideast.dk –192.168.0.1 and yyy.ideast.dk 192.168.0.2
On your first server xxx.ideast.dk via server manager (hostnames and addresses) create new host yyy for domain ideast.dk and point to local LAN IP of the second server.
You can do the same on the second server as well (optional) in case if you ever use it as a primary gateway and name resolution server, but add the xxx name for the first server.
Make both servers in the same workgroup (domain) to simplify file sharing.
You will need to create the same user account(s) on the second server.

Now, on your workstation if you want to use cable to access to certain host(s) or networks create static routing (persistent) via second server as a gateway. If you want to use it for all the surfing, make it your default gateway.
I hope I didn’t loose you here J

[wyron]

Thanks, Boris, I've done just that, meaning that I've added the hostname (and ip) of my second server (yyy) to the hostnames of my first (xxx).
I don't need to use the second server for my domain services, only as a gateway to the net where I'm supposed to maintain the administration of a 'community' website (I've just been elected chairman on account of my (very doubtful) technical abilities).
Of course I haven't activated the DHCP or DNS services, but I'm in doubt as to how I treat the setting of another DNS proxy or serveraddress in the primary domain on it (yyy).
Do I leave that blank, or do I point it to my primary server (xxx) ?
Likewise, the user accounts are principally irrelevant, since I utilize that server only as a gateway to this specific net.
I mean, thats the primary object of the project, but then again, on the other hand, I wouldn't mind having a backup- or loadbalancing server at hand, if it were practical without too much fuss.
Once again, thxs, Boris, I hope to have clarified the position, and would very much like to hear any suggestions you might have to further this project or its derivatives.

[wyron]

Funny - now I've added the hostname on xxx, the hostname of yyy is resolved when i ping the ip-address.
Still no answer, though. It still is as if the yyy-server doesn't exist, except for the gateway-service, which runs smooth as honey.
Should I give up the idea of having two SME-servers running in my domain, sharing the workload, and just be satisfied with the fulfillment of the primary purpose ?

[Boris]

I am not sure what you call sharing the workload. You second SME (yyy) in this setup no more then just a NAT gateway. Any $30-40 residential gateway will do the same thing. The important part is to create routing table to point to that (second) gateway in order to access the cable network.

[wyron]

You're absolutely right, Boris. The primary need is fulfilled. And as for the hardware invested, the price is about right seeing that it was an old Pentium pro 180-machine I managed to save just before my wife delegated it to the scrapyard.
But try to imagine the situation that the cable connection allows an amount of traffic for free, say 5 Gigs a month, wouldn't it be smart to have it sharing the traffic-load of my primary domain, thus doubling the outbound bandwidth ?
A temporary ftp-ibay for remote file-sharing would be nice too, wouldn't it ?
But how to make it a 'member server' in the domain (using M$-language).

[Boris]

Have a load balancing of incoming requests via DNS to two different IPs, etc... sounds a bit overcomplicated to me.
Why not just create ftp on yyy server by itself?
MS member server? for syncing samba domain accounts for a couple of home users or youself only? Just manually create them.

Is it a goal to automate everything? Then I need a simple note, I don't power up a computer and lunch a word processor. I just use a pencil!

[wyron]

Have a load balancing of incoming requests via DNS to two different IPs, etc... sounds a bit overcomplicated to me.

All right - probably just dreaming there.

Why not just create ftp on yyy server by itself?

Been there, done that.

MS member server?

Perhaps you misunderstood ? I wouldn't dream of creating a M$-server, I just want to 'see' the yyy-server from my workstations.

for syncing samba domain accounts for a couple of home users or youself only? Just manually create them.

Playing at the creation of a cron job rsync'ing the proper files seem much more fun to me.

Is it a goal to automate everything?

Of course it is - that's the whole idea of having server services.

Then I need a simple note, I don't power up a computer and lunch a word processor. I just use a pencil!

How do you 'lunch' a word-processor ? And where's the fun in a pencil ?

[Boris]

I meant launch.
English is not my first language and spell check is not always helpful.
 

[wyron]

both your computers running sme ?

Of course

you need to be on the same subnet - like 192.168.1.* or the 2 computers cannot see each other in YOUR network you will have to connect over the internet for administartion make sure remote access is turned on in server-manager then you can use https://www.yourserver.com/server-manager note the HTTPS

Of course !

If both computers are in server/gateway mode you can plug both
into a network switch and use either for internal computers to connect to the internet just adjust your gateway address
but make sure you use the same subnet on your internal nic
not required but gives you both computers on the same network
that way you can do your administration inside of your home network by just using the hostname or ip address

Of course - only it doesn't work.

a picture is an easier way to show this setup

|---Server1----cable
|
|---Switch---any other computers
|
|---Server2---dsl  

hope this helps

My setup exactly, only the cable is on server 2, and the addition of the specification of server 2 as the gateway for the workstation from which to administer the external community website.
Like I've stated, the primary object is reached, I only need to incorporate server 2 as a natural extension of my local domain - and thats where my abilities are overreached. But I'll work it out eventually (I hope).

[wyron]

I meant launch.
English is not my first language and spell check is not always helpful.

You know what, Boris ? You're absolutely right. Spell check is a bastard, not only in English I can assure you !
But I think you're doing all right !
I just couldn't resist the temptation if you know what I mean (I wasn't aware of the fact that English isn't your first language) ?