Re: setting up a remote location (another netbios domain, maybe)...

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Sites aren't the same as domains, 2 different things.

--
I hope that the information above helps you
Good Luck

Jorge Silva
MCSA
Systems Administrator

"Eric" <egiblock@xxxxxxxxx> wrote in message news:1162572883.367734.67020@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
i guess it's just my lack of knowledge when it comes to networking
across wan sites....

what the main goal is, is to have multiple locations in Network
Neighborhood (ie Headquarters, site1, site2, etc....) My understanding
was to have a dc at each location, and then different domain names (or
netbios names) at each site to seperate the two places..

as far as duplicate names for computers, we have a particular naming
convention here, so there will be no name duplication.



Jorge Silva wrote:
Inline
> 1. i don't know if it's old thinking, but the seperation of networks
> inside network neighborhood, wouldn't this constitute a different
> domain ??
> ie: current domain at site 1 = company.us (netbios =
> comp-us-ohio)
The question wasn't about domain defenition but rather about why do you
think that you need 2 different domains instead of just one?

> 2. there are 6 machines at the remote office.
IMHO 6 machines are few machines to justify a DC at remote location, if you
have a reliable WAN link I think that will be suff to handle logons and name
resolution.

> 3. network visibility, the options to file share between locations.
Network visibility? can you explain better this?
file share between locations - are you saying that the users need to share
local resources or they need to access to some file server?
As for exchange you can access using OWA, RPC over HTTP, POP client etc...
With these protocols you don't need to use direct connection to exchange
overloading the wan link.
However If you're using SQL, you might have ither issues, but as long as
your DB doesn't become bigger then 2GB (in MSDE 2000) or 4GB in SQL Express,
you can always use replication between SQL and MSDE at Branch site to sync
DBs, have a look at MS site for subscriptions, publications, configurations
for SQL.

--
I hope that the information above helps you
Good Luck

Jorge Silva
MCSA
Systems Administrator

<egiblock@xxxxxxxxx> wrote in message
news:1162476494.891088.262180@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> 1. i don't know if it's old thinking, but the seperation of networks
> inside network neighborhood, wouldn't this constitute a different
> domain ??
> ie: current domain at site 1 = company.us (netbios =
> comp-us-ohio)
>
> 2. there are 6 machines at the remote office
>
> 3. network visibility, the options to file share between locations.
>
> 4. we have a vpn between locations through cisco routers. the link is
> slow and we are working on getting the speed upgraded, but the link
> itself is reliable.
>
>
>
> Jorge Silva wrote:
>> Hi
>> Ok...
>> Before I start you must understand that only you have all the >> information
>> needed to perform your AD design according with your needs...
>> Assuming that you're talking about the same company and that you want >> to
>> have a better control on these workgroup machines in the remote
>> office....
>> My first question for you would be Why???
>>
>> 1 - Why you think that you need and additional Domain, because in most
>> scenarios 1 domain can handle just fine....
>> 2 - How many Machines do you have in that remote office.
>> 3 - What apps , and what recent needs did you have to make you >> consider
>> an
>> additional domain.
>> 4 - Do you have a reliable WAN link.
>> --
>> I hope that the information above helps you
>> Good Luck
>>
>> Jorge Silva
>> MCSA
>> Systems Administrator
>>
>> <egiblock@xxxxxxxxx> wrote in message
>> news:1162475168.428440.155400@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> > right now we have two locations.. i've simplified the names for
>> > desctition and security purposes...
>> >
>> > ohio = mydomain.us (netbios: mydom-us-ohio)
>> >
>> > iowa = workgroup: company2
>> >
>> >
>> > mydomain.us has 2 domain controllers, exchange 2003 that handles all >> > of
>> > the email in the organization (including the remote site)
>> >
>> >
>> >
>> > we want to install a domain controller at the remote location in >> > iowa.
>> > convert 'workgroup' to a domain (netbios: mydom-us-iowa)
>> >
>> >
>> > what is the best way to go here ?
>> >
>> > i'll answer any configuration questions that i can here..
>> >
>> >
>> > thanks
>> >
>


.

Relevant Pages

  • Re: [SLE] SUSE = Ubuntu?
    ... and 3) work on my distributed network package--- mostly compilation, tweak, ... The headless machines are assigned my three tasks... ... Each task is run on a remote machine, passing its X output back to the ... SSH starts a background process with X11 ...
    (SuSE)
  • Re: Suggestions for remote admin of linux machines
    ... ]pleased with the methods for remote administration that have come to ... So just do it, by command line and scripts, via the network. ... The only problem is that the machines may need on site if they crash ... ]Solution #3: KVM over IP. ...
    (comp.os.linux.networking)
  • Re: Suggestions for remote admin of linux machines
    ... ]pleased with the methods for remote administration that have come to ... So just do it, by command line and scripts, via the network. ... The only problem is that the machines may need on site if they crash ... ]Solution #3: KVM over IP. ...
    (comp.os.linux.misc)
  • Re: Remote Assistance User Acceptance exclusion
    ... way to Remote assistance. ... that doesn't really answer the question in a network infrastructure ... >> more practical for me to manage these machines remotely then to have to go ... >>> SBS Rocks! ...
    (microsoft.public.windows.server.sbs)
  • Re: vpn - can see all remote computers except 1
    ... Posting on MS newsgroup will benefit all readers and you may get more help. ... I can ping all machines on their network via IP address. ... I can find all machines from windows explorer> My Netwrok Places> Search ... I can ping this machine by IP, I can connect to it via remote desktop, I ...
    (microsoft.public.win2000.networking)