Problem with multi-homed system

[Guest]

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win2000.setup (More info?)

Hi,

I've extended my server machine (W2k Server, computer name "Serv") by
implementing a second NIC in order to utilize a second computer as print
server. But the new configuration kills me: Ping only works on x.x.x.1, DHCP
service shows a fix IP of x.x.x.2, DNS service only reacts on x.x.x.1, I
can't login to my server from the second computer (W2k Pro, computer name
"Cli"). Whenever I want to login to the server's domain at Cli login dialog
I get an error message saying that the domain either is invalid or not
available. On the other hand, if I want to access Cli from Serv's Windows
Explorer using \\Cli\ I get an error message saying that the "login server"
is not available at the moment...

Please, can someone help me? I wasn't aware that multi-homing is that
difficult.

I want to decide which NIC to use for my LAN. The other NIC is supposed to
connect to the Internet using Dial-Up. Accordingly, I want to configure
DHCP/DNS to work on the first NIC only ("Binding..." in DHCP/DNS don't
actually seem to have any effect). I'm using Active Directory.

Thanks for any help!!

Axel Dahmen

 

[Guest]

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win2000.setup (More info?)

Multihoming isn't difficult.

With only partial IP information, I can only give a generic comment. The
IP addresses on each card must be on a seperate subnet.

"Axel Dahmen" <NO_SPAM@NoOneKnows.de> wrote in message
news:uOGPMnNHEHA.3696@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> I've extended my server machine (W2k Server, computer name "Serv") by
> implementing a second NIC in order to utilize a second computer as print
> server. But the new configuration kills me: Ping only works on x.x.x.1,
DHCP
> service shows a fix IP of x.x.x.2, DNS service only reacts on x.x.x.1, I
> can't login to my server from the second computer (W2k Pro, computer name
> "Cli"). Whenever I want to login to the server's domain at Cli login
dialog
> I get an error message saying that the domain either is invalid or not
> available. On the other hand, if I want to access Cli from Serv's Windows
> Explorer using \\Cli\ I get an error message saying that the "login
server"
> is not available at the moment...
>
> Please, can someone help me? I wasn't aware that multi-homing is that
> difficult.
>
> I want to decide which NIC to use for my LAN. The other NIC is supposed to
> connect to the Internet using Dial-Up. Accordingly, I want to configure
> DHCP/DNS to work on the first NIC only ("Binding..." in DHCP/DNS don't
> actually seem to have any effect). I'm using Active Directory.
>
> Thanks for any help!!
>
> Axel Dahmen
>
>

 

[Guest]

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win2000.setup (More info?)

Hello Rob,

the addresses are: 192.168.190.1, 192.168.190.2

For my testing I've only connected the inbound cable to the server. But Ping
only works if I put the cable into NIC #1. If I plug it into NIC #2, the
destination host is unreachable.

I assume there is no hardware error so far.

TIA,
Axel Dahmen

-----------------------------------------------
"Rob Elder MVP-Networking" <relder@thisisnotright.com> schrieb im
Newsbeitrag news:eTrt1XUHEHA.1608@TK2MSFTNGP11.phx.gbl...
> Multihoming isn't difficult.
>
> With only partial IP information, I can only give a generic comment. The
> IP addresses on each card must be on a seperate subnet.
>
> "Axel Dahmen" <NO_SPAM@NoOneKnows.de> wrote in message
> news:uOGPMnNHEHA.3696@TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > I've extended my server machine (W2k Server, computer name "Serv") by
> > implementing a second NIC in order to utilize a second computer as print
> > server. But the new configuration kills me: Ping only works on x.x.x.1,
> DHCP
> > service shows a fix IP of x.x.x.2, DNS service only reacts on x.x.x.1, I
> > can't login to my server from the second computer (W2k Pro, computer
name
> > "Cli"). Whenever I want to login to the server's domain at Cli login
> dialog
> > I get an error message saying that the domain either is invalid or not
> > available. On the other hand, if I want to access Cli from Serv's
Windows
> > Explorer using \\Cli\ I get an error message saying that the "login
> server"
> > is not available at the moment...
> >
> > Please, can someone help me? I wasn't aware that multi-homing is that
> > difficult.
> >
> > I want to decide which NIC to use for my LAN. The other NIC is supposed
to
> > connect to the Internet using Dial-Up. Accordingly, I want to configure
> > DHCP/DNS to work on the first NIC only ("Binding..." in DHCP/DNS don't
> > actually seem to have any effect). I'm using Active Directory.
> >
> > Thanks for any help!!
> >
> > Axel Dahmen
> >
> >
>
>

 

[Guest]

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win2000.setup (More info?)

They should be in different subnets, right now they are not.

--
Regards,

Marina
Microsoft SBS-MVP

"Axel Dahmen" <NO_SPAM@NoOneKnows.de> schreef in bericht
news:#noc#lYHEHA.1608@TK2MSFTNGP11.phx.gbl...
> Hello Rob,
>
> the addresses are: 192.168.190.1, 192.168.190.2
>
> For my testing I've only connected the inbound cable to the server. But
Ping
> only works if I put the cable into NIC #1. If I plug it into NIC #2, the
> destination host is unreachable.
>
> I assume there is no hardware error so far.
>
> TIA,
> Axel Dahmen
>
> -----------------------------------------------
> "Rob Elder MVP-Networking" <relder@thisisnotright.com> schrieb im
> Newsbeitrag news:eTrt1XUHEHA.1608@TK2MSFTNGP11.phx.gbl...
> > Multihoming isn't difficult.
> >
> > With only partial IP information, I can only give a generic comment.
The
> > IP addresses on each card must be on a seperate subnet.
> >
> > "Axel Dahmen" <NO_SPAM@NoOneKnows.de> wrote in message
> > news:uOGPMnNHEHA.3696@TK2MSFTNGP10.phx.gbl...
> > > Hi,
> > >
> > > I've extended my server machine (W2k Server, computer name "Serv") by
> > > implementing a second NIC in order to utilize a second computer as
print
> > > server. But the new configuration kills me: Ping only works on
x.x.x.1,
> > DHCP
> > > service shows a fix IP of x.x.x.2, DNS service only reacts on x.x.x.1,
I
> > > can't login to my server from the second computer (W2k Pro, computer
> name
> > > "Cli"). Whenever I want to login to the server's domain at Cli login
> > dialog
> > > I get an error message saying that the domain either is invalid or not
> > > available. On the other hand, if I want to access Cli from Serv's
> Windows
> > > Explorer using \\Cli\ I get an error message saying that the "login
> > server"
> > > is not available at the moment...
> > >
> > > Please, can someone help me? I wasn't aware that multi-homing is that
> > > difficult.
> > >
> > > I want to decide which NIC to use for my LAN. The other NIC is
supposed
> to
> > > connect to the Internet using Dial-Up. Accordingly, I want to
configure
> > > DHCP/DNS to work on the first NIC only ("Binding..." in DHCP/DNS don't
> > > actually seem to have any effect). I'm using Active Directory.
> > >
> > > Thanks for any help!!
> > >
> > > Axel Dahmen
> > >
> > >
> >
> >
>
>
>
>

 

[Guest]

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win2000.setup (More info?)

Hi Marina and Rob,

just for the sake of my curiosity: Why do they have to be different? What's
the reason Ping doesn't work on my second NIC when they are on the same
subnet? And the others? I'm very keen to know to avoid further configuration
problems.

Thanks for enlightening me!

Regards,
Axel Dahmen

--------------------------------------
"Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> schrieb im
Newsbeitrag news:%7Ddc.1225$%4.20750@typhoon.bart.nl...
> They should be in different subnets, right now they are not.
>
> --
> Regards,
>
> Marina
> Microsoft SBS-MVP
>
> "Axel Dahmen" <NO_SPAM@NoOneKnows.de> schreef in bericht
> news:#noc#lYHEHA.1608@TK2MSFTNGP11.phx.gbl...
> > Hello Rob,
> >
> > the addresses are: 192.168.190.1, 192.168.190.2
> >
> > For my testing I've only connected the inbound cable to the server. But
> Ping
> > only works if I put the cable into NIC #1. If I plug it into NIC #2, the
> > destination host is unreachable.
> >
> > I assume there is no hardware error so far.
> >
> > TIA,
> > Axel Dahmen
> >
> > -----------------------------------------------
> > "Rob Elder MVP-Networking" <relder@thisisnotright.com> schrieb im
> > Newsbeitrag news:eTrt1XUHEHA.1608@TK2MSFTNGP11.phx.gbl...
> > > Multihoming isn't difficult.
> > >
> > > With only partial IP information, I can only give a generic comment.
> The
> > > IP addresses on each card must be on a seperate subnet.
> > >
> > > "Axel Dahmen" <NO_SPAM@NoOneKnows.de> wrote in message
> > > news:uOGPMnNHEHA.3696@TK2MSFTNGP10.phx.gbl...
> > > > Hi,
> > > >
> > > > I've extended my server machine (W2k Server, computer name "Serv")
by
> > > > implementing a second NIC in order to utilize a second computer as
> print
> > > > server. But the new configuration kills me: Ping only works on
> x.x.x.1,
> > > DHCP
> > > > service shows a fix IP of x.x.x.2, DNS service only reacts on
x.x.x.1,
> I
> > > > can't login to my server from the second computer (W2k Pro, computer
> > name
> > > > "Cli"). Whenever I want to login to the server's domain at Cli login
> > > dialog
> > > > I get an error message saying that the domain either is invalid or
not
> > > > available. On the other hand, if I want to access Cli from Serv's
> > Windows
> > > > Explorer using \\Cli\ I get an error message saying that the "login
> > > server"
> > > > is not available at the moment...
> > > >
> > > > Please, can someone help me? I wasn't aware that multi-homing is
that
> > > > difficult.
> > > >
> > > > I want to decide which NIC to use for my LAN. The other NIC is
> supposed
> > to
> > > > connect to the Internet using Dial-Up. Accordingly, I want to
> configure
> > > > DHCP/DNS to work on the first NIC only ("Binding..." in DHCP/DNS
don't
> > > > actually seem to have any effect). I'm using Active Directory.
> > > >
> > > > Thanks for any help!!
> > > >
> > > > Axel Dahmen
> > > >
> > > >
> > >
> > >
> >
> >
> >
> >
>
>

 

[Guest]

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win2000.setup (More info?)

Because you're using the 2nd nic to connect to the external world. That's
why they have to be on a different subnet.

--
Regards,

Marina
Microsoft SBS-MVP

"Axel Dahmen" <NO_SPAM@NoOneKnows.de> schreef in bericht
news:e1C#5GpHEHA.2576@TK2MSFTNGP09.phx.gbl...
> Hi Marina and Rob,
>
> just for the sake of my curiosity: Why do they have to be different?
What's
> the reason Ping doesn't work on my second NIC when they are on the same
> subnet? And the others? I'm very keen to know to avoid further
configuration
> problems.
>
> Thanks for enlightening me!
>
> Regards,
> Axel Dahmen
>
> --------------------------------------
> "Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> schrieb im
> Newsbeitrag news:%7Ddc.1225$%4.20750@typhoon.bart.nl...
> > They should be in different subnets, right now they are not.
> >
> > --
> > Regards,
> >
> > Marina
> > Microsoft SBS-MVP
> >
> > "Axel Dahmen" <NO_SPAM@NoOneKnows.de> schreef in bericht
> > news:#noc#lYHEHA.1608@TK2MSFTNGP11.phx.gbl...
> > > Hello Rob,
> > >
> > > the addresses are: 192.168.190.1, 192.168.190.2
> > >
> > > For my testing I've only connected the inbound cable to the server.
But
> > Ping
> > > only works if I put the cable into NIC #1. If I plug it into NIC #2,
the
> > > destination host is unreachable.
> > >
> > > I assume there is no hardware error so far.
> > >
> > > TIA,
> > > Axel Dahmen
> > >
> > > -----------------------------------------------
> > > "Rob Elder MVP-Networking" <relder@thisisnotright.com> schrieb im
> > > Newsbeitrag news:eTrt1XUHEHA.1608@TK2MSFTNGP11.phx.gbl...
> > > > Multihoming isn't difficult.
> > > >
> > > > With only partial IP information, I can only give a generic comment.
> > The
> > > > IP addresses on each card must be on a seperate subnet.
> > > >
> > > > "Axel Dahmen" <NO_SPAM@NoOneKnows.de> wrote in message
> > > > news:uOGPMnNHEHA.3696@TK2MSFTNGP10.phx.gbl...
> > > > > Hi,
> > > > >
> > > > > I've extended my server machine (W2k Server, computer name "Serv")
> by
> > > > > implementing a second NIC in order to utilize a second computer as
> > print
> > > > > server. But the new configuration kills me: Ping only works on
> > x.x.x.1,
> > > > DHCP
> > > > > service shows a fix IP of x.x.x.2, DNS service only reacts on
> x.x.x.1,
> > I
> > > > > can't login to my server from the second computer (W2k Pro,
computer
> > > name
> > > > > "Cli"). Whenever I want to login to the server's domain at Cli
login
> > > > dialog
> > > > > I get an error message saying that the domain either is invalid or
> not
> > > > > available. On the other hand, if I want to access Cli from Serv's
> > > Windows
> > > > > Explorer using \\Cli\ I get an error message saying that the
"login
> > > > server"
> > > > > is not available at the moment...
> > > > >
> > > > > Please, can someone help me? I wasn't aware that multi-homing is
> that
> > > > > difficult.
> > > > >
> > > > > I want to decide which NIC to use for my LAN. The other NIC is
> > supposed
> > > to
> > > > > connect to the Internet using Dial-Up. Accordingly, I want to
> > configure
> > > > > DHCP/DNS to work on the first NIC only ("Binding..." in DHCP/DNS
> don't
> > > > > actually seem to have any effect). I'm using Active Directory.
> > > > >
> > > > > Thanks for any help!!
> > > > >
> > > > > Axel Dahmen
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
>
>

 

[Guest]

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win2000.setup (More info?)

> Because you're using the 2nd nic to connect to the external world. That's
> why they have to be on a different subnet.

????????? 8-0
Sorry, but I don't understand, I'm afraid... Internal/External connection is
supposed to be my concept, yes, but I haven't implemented any of this yet.
So far, both NICs are not dedicated at all. I'm going to use Dial-Up (ADSL)
which uses a different IP address on the NIC anyway for the time of
connection. I didn't create a dial-up connection yet. I just have two
sibling NICs, and when I plug the cross-link cable from my second computer
into one NIC, Ping works, but if I plug it into the second NIC, Ping doesn't
work. What if I'd connect a third computer, let's say a notebook, to this
second NIC. It shouldn't route, but it should still connect.

I'm baffled. Thanks for enlightening me.

TIA,
Axel Dahmen