Connecting through same domain, different network

I want two computers that are a part of the same domain to be able to
connect to each other, even though they're on different networks.

This was possible, or at least seemed to be, through Windows 2000 Advance
Server, and I'm wondering how to do it through Windows Server 2003 Standard
Edition




-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

Functinality across networks is achieved with a Router. It you don't have a
Router or haven't setup a Windows machine to act as a Router then you are
wasting your time.

299810 - HOW TO: Configure Windows 2000 to Be a Router
http://support.microsoft.com/default...b;en-us;299810

In the other thread you said that one of the Networks was not supposed to
get to the Internet. That is accomplished by whatever device makes the
Internet possible and has no relationship to having both networks see each
other.

BUT....as I recall from the other thread,..one of your networks runs Public
IP#s and the other runs Private IP#s. This means your Publicly addressed
Network probably already see the Internet directly on its own via a simple
Router,...that's not a real good idea but that is another topic. Your
Privately addressed Network will not be able to contact the Internet because
Private IP Blocks are not compatible with the Internet.
Any Internet Host out there will not be able to respond back to any request
from a machine or device running a Privte IP#. Private addressed Networks
require either a NAT Server or a Proxy Server to function with the Internet.

As an extra measure, your Router between the Publicly addresses Network and
the Internet should be configured to disallow any traffic involving in any
way the official RFC Private Address Blocks. These Blocks are:

10.0.0.0 -- 10.255.255.255
172.16.0.0 -- 172.31.255.255
192.168.0.0 -- 192.168.255.255

It should also include 127.0.0.0 -- 127.255.255.255

Thes blocks should be for *any* direction regaurdless if it is the Source or
Destination IP#.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Apollyon" <(E-Mail Removed)> wrote in message
news:40bd84b3$(E-Mail Removed)...
> I want two computers that are a part of the same domain to be able to
> connect to each other, even though they're on different networks.
>
> This was possible, or at least seemed to be, through Windows 2000 Advance
> Server, and I'm wondering how to do it through Windows Server 2003
Standard
> Edition
>
>
>
>
> -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
> http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
> -----== Over 100,000 Newsgroups - 19 Different Servers! =-----

Alright, I understand that ... And that makes sense. I actually should've
realized that already :P

But the real problem I'm facing right now is that the routing doesn't seem
to work.

I enabled LAN Routing, I have the four interfaces in General (Local Area
Connection, Local Area Connection 2, Loopback, Internal) ... Is there some
other step I'm supposed to take? The article seemed to suggest just enabling
LAN Routing was enough.

--
Apollyon

"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> Functinality across networks is achieved with a Router. It you don't have
a
> Router or haven't setup a Windows machine to act as a Router then you are
> wasting your time.
>
> 299810 - HOW TO: Configure Windows 2000 to Be a Router
> http://support.microsoft.com/default...b;en-us;299810
>
> In the other thread you said that one of the Networks was not supposed to
> get to the Internet. That is accomplished by whatever device makes the
> Internet possible and has no relationship to having both networks see each
> other.
>
> BUT....as I recall from the other thread,..one of your networks runs
Public
> IP#s and the other runs Private IP#s. This means your Publicly addressed
> Network probably already see the Internet directly on its own via a simple
> Router,...that's not a real good idea but that is another topic. Your
> Privately addressed Network will not be able to contact the Internet
because
> Private IP Blocks are not compatible with the Internet.
> Any Internet Host out there will not be able to respond back to any
request
> from a machine or device running a Privte IP#. Private addressed Networks
> require either a NAT Server or a Proxy Server to function with the
Internet.
>
> As an extra measure, your Router between the Publicly addresses Network
and
> the Internet should be configured to disallow any traffic involving in any
> way the official RFC Private Address Blocks. These Blocks are:
>
> 10.0.0.0 -- 10.255.255.255
> 172.16.0.0 -- 172.31.255.255
> 192.168.0.0 -- 192.168.255.255
>
> It should also include 127.0.0.0 -- 127.255.255.255
>
> Thes blocks should be for *any* direction regaurdless if it is the Source
or
> Destination IP#.
>
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "Apollyon" <(E-Mail Removed)> wrote in message
> news:40bd84b3$(E-Mail Removed)...
> > I want two computers that are a part of the same domain to be able to
> > connect to each other, even though they're on different networks.
> >
> > This was possible, or at least seemed to be, through Windows 2000
Advance
> > Server, and I'm wondering how to do it through Windows Server 2003
> Standard
> > Edition
> >
> >
> >
> >
> > -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
> > http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
> > -----== Over 100,000 Newsgroups - 19 Different Servers! =-----
>
>




-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

All Clients must use the "Router" as the Default Gateway. They use the IP#
that directly faces them.

Other than that you'd have to clarify "...doesn't work...".

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Apollyon" <(E-Mail Removed)> wrote in message
news:40be4454$(E-Mail Removed)...
> Alright, I understand that ... And that makes sense. I actually should've
> realized that already :P
>
> But the real problem I'm facing right now is that the routing doesn't seem
> to work.
>
> I enabled LAN Routing, I have the four interfaces in General (Local Area
> Connection, Local Area Connection 2, Loopback, Internal) ... Is there some
> other step I'm supposed to take? The article seemed to suggest just
enabling
> LAN Routing was enough.
>
> --
> Apollyon
>
> "Phillip Windell" <@.> wrote in message
> news:(E-Mail Removed)...
> > Functinality across networks is achieved with a Router. It you don't
have
> a
> > Router or haven't setup a Windows machine to act as a Router then you
are
> > wasting your time.
> >
> > 299810 - HOW TO: Configure Windows 2000 to Be a Router
> > http://support.microsoft.com/default...b;en-us;299810
> >
> > In the other thread you said that one of the Networks was not supposed
to
> > get to the Internet. That is accomplished by whatever device makes the
> > Internet possible and has no relationship to having both networks see
each
> > other.
> >
> > BUT....as I recall from the other thread,..one of your networks runs
> Public
> > IP#s and the other runs Private IP#s. This means your Publicly
addressed
> > Network probably already see the Internet directly on its own via a
simple
> > Router,...that's not a real good idea but that is another topic. Your
> > Privately addressed Network will not be able to contact the Internet
> because
> > Private IP Blocks are not compatible with the Internet.
> > Any Internet Host out there will not be able to respond back to any
> request
> > from a machine or device running a Privte IP#. Private addressed
Networks
> > require either a NAT Server or a Proxy Server to function with the
> Internet.
> >
> > As an extra measure, your Router between the Publicly addresses Network
> and
> > the Internet should be configured to disallow any traffic involving in
any
> > way the official RFC Private Address Blocks. These Blocks are:
> >
> > 10.0.0.0 -- 10.255.255.255
> > 172.16.0.0 -- 172.31.255.255
> > 192.168.0.0 -- 192.168.255.255
> >
> > It should also include 127.0.0.0 -- 127.255.255.255
> >
> > Thes blocks should be for *any* direction regaurdless if it is the
Source
> or
> > Destination IP#.
> >
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> > "Apollyon" <(E-Mail Removed)> wrote in message
> > news:40bd84b3$(E-Mail Removed)...
> > > I want two computers that are a part of the same domain to be able to
> > > connect to each other, even though they're on different networks.
> > >
> > > This was possible, or at least seemed to be, through Windows 2000
> Advance
> > > Server, and I'm wondering how to do it through Windows Server 2003
> > Standard
> > > Edition
> > >
> > >
> > >
> > >
> > > -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
> > > http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
> > > -----== Over 100,000 Newsgroups - 19 Different Servers! =-----
> >
> >
>
>
>
>
> -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
> http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
> -----== Over 100,000 Newsgroups - 19 Different Servers! =-----

Okay that was the problem, yes.

Once I changed the default gateway of the computer, one computer could ping
the other.

Kind of a question on the same topic ... I can connect to the computer by
saying \\netbiosname but I can't see it when I'm browsing in the Domain ...
Just curious if that's indicative of some kind of problem or just a side
effect of the NetBIOS protocol not being routable?

--
Apollyon

"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> All Clients must use the "Router" as the Default Gateway. They use the IP#
> that directly faces them.
>
> Other than that you'd have to clarify "...doesn't work...".
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "Apollyon" <(E-Mail Removed)> wrote in message
> news:40be4454$(E-Mail Removed)...
> > Alright, I understand that ... And that makes sense. I actually
should've
> > realized that already :P
> >
> > But the real problem I'm facing right now is that the routing doesn't
seem
> > to work.
> >
> > I enabled LAN Routing, I have the four interfaces in General (Local Area
> > Connection, Local Area Connection 2, Loopback, Internal) ... Is there
some
> > other step I'm supposed to take? The article seemed to suggest just
> enabling
> > LAN Routing was enough.
> >
> > --
> > Apollyon
> >
> > "Phillip Windell" <@.> wrote in message
> > news:(E-Mail Removed)...
> > > Functinality across networks is achieved with a Router. It you don't
> have
> > a
> > > Router or haven't setup a Windows machine to act as a Router then you
> are
> > > wasting your time.
> > >
> > > 299810 - HOW TO: Configure Windows 2000 to Be a Router
> > > http://support.microsoft.com/default...b;en-us;299810
> > >
> > > In the other thread you said that one of the Networks was not supposed
> to
> > > get to the Internet. That is accomplished by whatever device makes
the
> > > Internet possible and has no relationship to having both networks see
> each
> > > other.
> > >
> > > BUT....as I recall from the other thread,..one of your networks runs
> > Public
> > > IP#s and the other runs Private IP#s. This means your Publicly
> addressed
> > > Network probably already see the Internet directly on its own via a
> simple
> > > Router,...that's not a real good idea but that is another topic.
Your
> > > Privately addressed Network will not be able to contact the Internet
> > because
> > > Private IP Blocks are not compatible with the Internet.
> > > Any Internet Host out there will not be able to respond back to any
> > request
> > > from a machine or device running a Privte IP#. Private addressed
> Networks
> > > require either a NAT Server or a Proxy Server to function with the
> > Internet.
> > >
> > > As an extra measure, your Router between the Publicly addresses
Network
> > and
> > > the Internet should be configured to disallow any traffic involving in
> any
> > > way the official RFC Private Address Blocks. These Blocks are:
> > >
> > > 10.0.0.0 -- 10.255.255.255
> > > 172.16.0.0 -- 172.31.255.255
> > > 192.168.0.0 -- 192.168.255.255
> > >
> > > It should also include 127.0.0.0 -- 127.255.255.255
> > >
> > > Thes blocks should be for *any* direction regaurdless if it is the
> Source
> > or
> > > Destination IP#.
> > >
> > >
> > > --
> > >
> > > Phillip Windell [MCP, MVP, CCNA]
> > > www.wandtv.com
> > >
> > >
> > > "Apollyon" <(E-Mail Removed)> wrote in message
> > > news:40bd84b3$(E-Mail Removed)...
> > > > I want two computers that are a part of the same domain to be able
to
> > > > connect to each other, even though they're on different networks.
> > > >
> > > > This was possible, or at least seemed to be, through Windows 2000
> > Advance
> > > > Server, and I'm wondering how to do it through Windows Server 2003
> > > Standard
> > > > Edition
> > > >
> > > >
> > > >
> > > >
> > > > -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
> > > > http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
> > > > -----== Over 100,000 Newsgroups - 19 Different Servers! =-----
> > >
> > >
> >
> >
> >
> >
> > -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
> > http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
> > -----== Over 100,000 Newsgroups - 19 Different Servers! =-----
>
>




-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

Netbios "name" broadcast don't cross Routers. You have to use a WINS
Server. Net'Hood is a separate thing. It is based on a list stored on the
one machine that is "elected" as the master browser. Net'Hood only shows
what's in this list and has no bearing on whether the particular machine is
accessable or not. For the master browser to keep a good current list you
must run a WINS Server and probably should make sure that "Netbios over
TCP/IP" is enabled on all the effected machines.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Apollyon" <(E-Mail Removed)> wrote in message
news:40be5718$(E-Mail Removed)...
> Okay that was the problem, yes.
>
> Once I changed the default gateway of the computer, one computer could
ping
> the other.
>
> Kind of a question on the same topic ... I can connect to the computer by
> saying \\netbiosname but I can't see it when I'm browsing in the Domain
....
> Just curious if that's indicative of some kind of problem or just a side
> effect of the NetBIOS protocol not being routable?
>
> --
> Apollyon
>
> "Phillip Windell" <@.> wrote in message
> news:(E-Mail Removed)...
> > All Clients must use the "Router" as the Default Gateway. They use the
IP#
> > that directly faces them.
> >
> > Other than that you'd have to clarify "...doesn't work...".
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> > "Apollyon" <(E-Mail Removed)> wrote in message
> > news:40be4454$(E-Mail Removed)...
> > > Alright, I understand that ... And that makes sense. I actually
> should've
> > > realized that already :P
> > >
> > > But the real problem I'm facing right now is that the routing doesn't
> seem
> > > to work.
> > >
> > > I enabled LAN Routing, I have the four interfaces in General (Local
Area
> > > Connection, Local Area Connection 2, Loopback, Internal) ... Is there
> some
> > > other step I'm supposed to take? The article seemed to suggest just
> > enabling
> > > LAN Routing was enough.
> > >
> > > --
> > > Apollyon
> > >
> > > "Phillip Windell" <@.> wrote in message
> > > news:(E-Mail Removed)...
> > > > Functinality across networks is achieved with a Router. It you don't
> > have
> > > a
> > > > Router or haven't setup a Windows machine to act as a Router then
you
> > are
> > > > wasting your time.
> > > >
> > > > 299810 - HOW TO: Configure Windows 2000 to Be a Router
> > > > http://support.microsoft.com/default...b;en-us;299810
> > > >
> > > > In the other thread you said that one of the Networks was not
supposed
> > to
> > > > get to the Internet. That is accomplished by whatever device makes
> the
> > > > Internet possible and has no relationship to having both networks
see
> > each
> > > > other.
> > > >
> > > > BUT....as I recall from the other thread,..one of your networks runs
> > > Public
> > > > IP#s and the other runs Private IP#s. This means your Publicly
> > addressed
> > > > Network probably already see the Internet directly on its own via a
> > simple
> > > > Router,...that's not a real good idea but that is another topic.
> Your
> > > > Privately addressed Network will not be able to contact the Internet
> > > because
> > > > Private IP Blocks are not compatible with the Internet.
> > > > Any Internet Host out there will not be able to respond back to any
> > > request
> > > > from a machine or device running a Privte IP#. Private addressed
> > Networks
> > > > require either a NAT Server or a Proxy Server to function with the
> > > Internet.
> > > >
> > > > As an extra measure, your Router between the Publicly addresses
> Network
> > > and
> > > > the Internet should be configured to disallow any traffic involving
in
> > any
> > > > way the official RFC Private Address Blocks. These Blocks are:
> > > >
> > > > 10.0.0.0 -- 10.255.255.255
> > > > 172.16.0.0 -- 172.31.255.255
> > > > 192.168.0.0 -- 192.168.255.255
> > > >
> > > > It should also include 127.0.0.0 -- 127.255.255.255
> > > >
> > > > Thes blocks should be for *any* direction regaurdless if it is the
> > Source
> > > or
> > > > Destination IP#.
> > > >
> > > >
> > > > --
> > > >
> > > > Phillip Windell [MCP, MVP, CCNA]
> > > > www.wandtv.com
> > > >
> > > >
> > > > "Apollyon" <(E-Mail Removed)> wrote in message
> > > > news:40bd84b3$(E-Mail Removed)...
> > > > > I want two computers that are a part of the same domain to be able
> to
> > > > > connect to each other, even though they're on different networks.
> > > > >
> > > > > This was possible, or at least seemed to be, through Windows 2000
> > > Advance
> > > > > Server, and I'm wondering how to do it through Windows Server 2003
> > > > Standard
> > > > > Edition
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
> > > > > http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
> > > > > -----== Over 100,000 Newsgroups - 19 Different Servers! =-----
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
> > > http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
> > > -----== Over 100,000 Newsgroups - 19 Different Servers! =-----
> >
> >
>
>
>
>
> -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
> http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
> -----== Over 100,000 Newsgroups - 19 Different Servers! =-----