Re: 2 SBS on same network.

Thanks for the info...

Yes, have tried it and as you said, so many peeps have the scenario and I
was wondering..

Issues do happen when they have been running for a while, always seemed on
reboots (after patches).

Dhcp is the first issue which as you say easily solved by switching off dhcp
on one and manually configure clients for other. However our experiment was
putting other server in different IP/subnet. Interesting that they are both
in same IP and no serious issues..yet lol

The exercise had only one client connected to each server, the 14 days you
mention is interesting.. why do you mention 14 days ? It was after 2 weeks
that we experianced problems, clients couldn't logon and found a server had
shut down clients had problems accessing files. It was a bit time consuming
i.e trying same / different user names event logs on both servers had
references to the other and other server had references to other client...
that we dumped it all with the summary dont have 2 sbs even with different
IP...




"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:uTJwFwndGHA.3484@xxxxxxxxxxxxxxxxxxxxxxx
of course they're test boxes.

Both were installed as standalone boxes in standard manner, no
customisations to compensate for the intended sharing of IP space. The
only differences in the machine config are:
Server name
AD DNS and NETBIOS name
IP Address, same subnet, different IP
each is a fully configured 2 NIC SBS2003 Standard, start at boot from CD1,
finish the CIECW.

the servers were then connected to the same ethernet segment. One change
was made to compensate for this, DNS on each server was told to forward
queries for the AD DNS name of the other server to it.

Even the behaviour of DHCP is predictable. On startup each will attempt to
start it's DHCP service, if the DHCP service detects the other as active
it shuts down.

The config has, so far, no negative effect on any other service. I might
have to wait 14 days though (I don't expect so).

There is an expected problem with running DHCP clients. If the 'home'
server of the client is responsible for DHCP during client startup all is
fine. If however the 'other' server is responsible the client will try to
register in the wrong DNS. Manual IP settings on the client avoid this,
I'm thinking about ways it may be automated but I'm not sure I can wile
maintaining a single subnet/scope. It would seem that using two scopes
with a 25 (rather than 24) bit mask and DHCP reservations may avoid the
issue while increasing maintenance only slightly. I'm not going to go here
till the 14 days pass though.

So, when you suggested it wouldn't work, had you tried it? or was it just
wild speculation? Your statement only caused me to wish to look at
something which was on my list anyway, the question has been raised enough
times to warrant more than the thought 'yeah well, technically it should
be OK'. If you have tried it, and experienced a problem, I'm interested in
where I should be looking.

"Maxibo" <totallyanon@xxxxxxxxx> wrote in message
news:uyB63SmdGHA.4932@xxxxxxxxxxxxxxxxxxxxxxx
Hi SG..

2 SBS running happily ? All services ok, Have you done anything for them
to operate on same IP range ?

Are these just test servers.... lol


"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:%23BFve5gdGHA.5040@xxxxxxxxxxxxxxxxxxxxxxx
What specific issue would you like me to look at?

C:\Documents and Settings\Administrator>ping sbs1.org1.local

Pinging SBS1.Org1.local [192.168.16.2] with 32 bytes of data:

Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.16.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ping sbs2.org2.local

Pinging sbs2.org2.local [192.168.16.3] with 32 bytes of data:

Reply from 192.168.16.3: bytes=32 time=6ms TTL=128
Reply from 192.168.16.3: bytes=32 time<1ms TTL=128
Reply from 192.168.16.3: bytes=32 time<1ms TTL=128
Reply from 192.168.16.3: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.16.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 6ms, Average = 1ms


"Maxibo" <totallyanon@xxxxxxxxx> wrote in message
news:e%23I82MGdGHA.5116@xxxxxxxxxxxxxxxxxxxxxxx
May I just add.... have you done it?... Even on different lan / subnet
they
still find each other although not initially but when a server is
rebooted
it sees the other.

May I also ask, quote ' No, they do not have to be different
subnet/networks. ' , put one server on 192.168.16.2 and the other on
192.168.16.3 and watch the event logs and services...lol



"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:eg3h4rBdGHA.4276@xxxxxxxxxxxxxxxxxxxxxxx
No, they do not have to be different subnet/networks.

Theoretically, the domains could even have the same name, the SIDs
would
differentiate them. (This would be a major headache though, the SBS's
may
not complain but all the users would)

There is a specific SBS limitation. One SBS per AD forest. SBS also
supports only one AD domain per forest. SBS does not impose 'IP based
restrictions'.

The OP's biggest problem comes from DHCP and registration to the AD
DNS.
There is also a problem accessing SBS (1 and2) resources externally
if
the
office has a single public IP.

This sort of thing (combining 2 SBS networks on a single LAN segment)
is
getting asked enough I may have to throw a couple of test boxes
together

"Maxibo" <totallyanon@xxxxxxxxx> wrote in message
news:O5zOsEAdGHA.4312@xxxxxxxxxxxxxxxxxxxxxxx
Hi Clayton..

Bit more than not same domain, can't be on same net... have to have
totally different IP ranges and subnet..

Can you put the new company into a differnt hub / switch and then
each
server second network card into a seperate port in the router (if
you
have one)


"Clayton" <Clayton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C63A8439-FF12-473D-A611-F41191C717E5@xxxxxxxxxxxxxxxx
I have a client with one SBS 2003. Another company is going to be
moving
in
with the 1st client at the end of this month and they will be
bringing
their
SBS 2003. I am aware 2 SBS cannot belong on the same network,
however,
I
have
read that they can co-exist on the same net so long as they are on
separate
domains. I know I will have to work out the IP numbers and such,
and
also
have to turn off one of the DHCP servers. What I am concerned a
about
is
DNS.
The companies would definitely benefit being on the same network so
they
can
both take advantage of the high dollar printer/copiers. Should I be
concerned
about anything? especailly DNS.

Thanks















.

Relevant Pages

  • RE: Fax monitor incoming + outgoing calls?
    ... problem between the client computer and the SBS server. ... Client is using the internal IP address of the SBS server as the ... To the folder redirection GPO issue: ...
    (microsoft.public.windows.server.sbs)
  • RE: (Very) Slow browsing server shares - Net Work Monitor shows ca
    ... If this issue happen only when browse shared folders on SBS from one XP ... client computer, this will be a client side error. ... click to check the "Hide All Microsoft Services" ... Digitally sign communications (if server ...
    (microsoft.public.windows.server.sbs)
  • RE: No Client or Server Desktop Access Through RWW SBS 2003 SP2
    ... internal client Remote Desktop via RWW. ... Please perform the steps on the SBS and internal client computers: ... Click Remote tab, tick Enable Remote Desktop on this computer ... On the SBS server, click Start, click Run, type "regedit" (without the ...
    (microsoft.public.windows.server.sbs)
  • RE: trouble with shared fax service
    ... Thank you for posting in SBS newsgroup. ... install fax service on client computers. ... the SBS server or on the client workstation. ... and then choose 'Install' for the 'Fax Services' item. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... so we don't even know if dhcp is configured on ... Les Connor [SBS Community Member - SBS MVP] ... no internet connection from the server. ... dns suffix search list: MuellerElectrical.local ...
    (microsoft.public.windows.server.sbs)
Loading