Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Windows Server General Help » 2003 server multihoming issue?
2003 server multihoming issue? [message #163535] Wed, 03 June 2009 06:03 Go to next message
JHman  is currently offline JHman
Messages: 19
Registered: July 2009
Junior Member
OK, so I'm training myself in AD and Windows networking with the help of a
virtual setup in VMWare workstation. But now I'm experiencing a small strange
issue which, although it isn't a showstopper in my training process, bothers
me because I don't understand it and I WANT to understand it. :) I suspect
it's pretty basic.


Situation: set up a windows 2003 SP2 server ("2003VM5") and two XP clients
("XPclient1" and "XPClient2"). Created two virtual LAN segments, connected to
two NICs in server 2003VM5. Each client, TCP/IP configured via DHCP, is
connected to one of the segments.

I have setup an "COE.NET" AD domain, a DHCP server with two scopes, and a
DNS server installed by the AD wizard.

NICs in server 2003VM: static IPs

172.22.0.10
255.255.254.0
(gateway empty)
DNS servers 172.22.0.10,172.22.2.10

172.22.2.10
255.255.254.0
(gateway empty)
DNS servers 172.22.2.10,172.22.0.10

DHCP two scopes:

scope 172.22.0.0
address range 172.22.0.1 - 172.22.1.254
exclusions 172.22.0.1 - 172.22.1.0
scope options:
router 172.22.0.10
DNS servers 172.22.0.10,172.22.2.10
DOMAIN NAME COE.NET

scope 172.22.2.0
address range 172.22.2.1 - 172.22.3.254
exclusions 172.22.2.1 - 172.22.3.0
scope options:
router 172.22.2.10
DNS servers 172.22.2.10,172.22.0.10
DOMAIN NAME COE.NET

(almost) Everything seems fine. The two XPClients have been joined to the
domain without problems, they both get leases from the proper scopes
("XPclient1"=172.22.1.1 and "XPClient2"=172.22.3.1) with TCP/IP settings
looking good. From both clients I can do a "ping 2003VM5" and get replies
after correct name resolution:

Pinging 2003VM5.COE.NET [172.22.0.10]
Pinging 2003VM5.COE.NET [172.22.2.10]

Both clients and both server IP's show up in the DNS forward lookup zone...
I really can't see anything wrong.

YET, when I ping XPClient2 from server 2003VM5:

=======================================================
C:\Documents and Settings\networkadmin>ping XPclient2

Pinging XPclient2.COE.NET [172.22.3.1] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
=======================================================

What's going on here? XPClient1 gives no trouble at all! I thought it might
have something to do with the multihoming. So I installed RRAS for "LAN
Routing", but no change.

Any suggestions, because I don't feel like continuing to experiment with
other subjects before this basic problem is solved (who knows what it might
cause later on)...

TIA
Re: 2003 server multihoming issue? [message #163536 is a reply to message #163535] Wed, 03 June 2009 06:19 Go to previous messageGo to next message
meiweb(nospam)  is currently offline meiweb(nospam)  Germany
Messages: 1307
Registered: July 2009
Senior Member
Hello JHman,

Yes, it belongs to the multihoming. There is no configuration applied that
the server also routes between the networks.

See here about:
http://articles.techrepublic.com.com/5100-10878_11-5844624.h tml

http://windowsitpro.com/article/articleid/79239/jsi-tip-7230 -how-do-i-configure-windows-server-2003-to-function-as-a-rou ter-for-my-lan.html

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> OK, so I'm training myself in AD and Windows networking with the help
> of a virtual setup in VMWare workstation. But now I'm experiencing a
> small strange issue which, although it isn't a showstopper in my
> training process, bothers me because I don't understand it and I WANT
> to understand it. :) I suspect it's pretty basic.
>
> Situation: set up a windows 2003 SP2 server ("2003VM5") and two XP
> clients ("XPclient1" and "XPClient2"). Created two virtual LAN
> segments, connected to two NICs in server 2003VM5. Each client, TCP/IP
> configured via DHCP, is connected to one of the segments.
>
> I have setup an "COE.NET" AD domain, a DHCP server with two scopes,
> and a DNS server installed by the AD wizard.
>
> NICs in server 2003VM: static IPs
>
> 172.22.0.10
> 255.255.254.0
> (gateway empty)
> DNS servers 172.22.0.10,172.22.2.10
> 172.22.2.10
> 255.255.254.0
> (gateway empty)
> DNS servers 172.22.2.10,172.22.0.10
> DHCP two scopes:
>
> scope 172.22.0.0
> address range 172.22.0.1 - 172.22.1.254
> exclusions 172.22.0.1 - 172.22.1.0
> scope options:
> router 172.22.0.10
> DNS servers 172.22.0.10,172.22.2.10
> DOMAIN NAME COE.NET
> scope 172.22.2.0
> address range 172.22.2.1 - 172.22.3.254
> exclusions 172.22.2.1 - 172.22.3.0
> scope options:
> router 172.22.2.10
> DNS servers 172.22.2.10,172.22.0.10
> DOMAIN NAME COE.NET
> (almost) Everything seems fine. The two XPClients have been joined to
> the domain without problems, they both get leases from the proper
> scopes ("XPclient1"=172.22.1.1 and "XPClient2"=172.22.3.1) with TCP/IP
> settings looking good. From both clients I can do a "ping 2003VM5" and
> get replies after correct name resolution:
>
> Pinging 2003VM5.COE.NET [172.22.0.10]
> Pinging 2003VM5.COE.NET [172.22.2.10]
> Both clients and both server IP's show up in the DNS forward lookup
> zone... I really can't see anything wrong.
>
> YET, when I ping XPClient2 from server 2003VM5:
>
> ======================================================= C:\Documents
> and Settings\networkadmin>ping XPclient2
>
> Pinging XPclient2.COE.NET [172.22.3.1] with 32 bytes of data:
>
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> =======================================================
> What's going on here? XPClient1 gives no trouble at all! I thought it
> might have something to do with the multihoming. So I installed RRAS
> for "LAN Routing", but no change.
>
> Any suggestions, because I don't feel like continuing to experiment
> with other subjects before this basic problem is solved (who knows
> what it might cause later on)...
>
> TIA
>
Re: 2003 server multihoming issue? [message #163540 is a reply to message #163536] Wed, 03 June 2009 06:56 Go to previous messageGo to next message
JHman  is currently offline JHman
Messages: 19
Registered: July 2009
Junior Member
Hi Meinolf,

thanks for your quick reaction!

The issue must be a little bit deeper, though. I checked the articles you
posted, but the configurations they point out ARE in effect at this moment.
Server 2003VM5 IS "configured as a router" for "LAN routing only" and "enable
IP routing" is checked.

Yet it MUST be something with routing. I did further tests and found out
that I can ping XPClient1 from XPclient2, but not XPClient2 from XPClient1
(just like I couldn'ty ping XPClient2 from server 2003VM5). Name resolution
is correct in both tests though. The ping test says "request timed out".

I must have some IP settings wrong...



"Meinolf Weber [MVP-DS]" wrote:

> Hello JHman,
>
> Yes, it belongs to the multihoming. There is no configuration applied that
> the server also routes between the networks.
>
> See here about:
> http://articles.techrepublic.com.com/5100-10878_11-5844624.h tml
>
> http://windowsitpro.com/article/articleid/79239/jsi-tip-7230 -how-do-i-configure-windows-server-2003-to-function-as-a-rou ter-for-my-lan.html
>
> Best regards
>
> Meinolf Weber
Re: 2003 server multihoming issue? [message #163541 is a reply to message #163535] Wed, 03 June 2009 06:57 Go to previous messageGo to next message
Dusko Savatovic  is currently offline Dusko Savatovic  Croatia
Messages: 323
Registered: July 2009
Senior Member
Did you disable firewalls on XP clients?

"JHman" <JHman@discussions.microsoft.com> wrote in message
news:CB86082E-4D1C-4EBE-8BF4-FFCDBF67E788@microsoft.com...
> OK, so I'm training myself in AD and Windows networking with the help of a
> virtual setup in VMWare workstation. But now I'm experiencing a small
> strange
> issue which, although it isn't a showstopper in my training process,
> bothers
> me because I don't understand it and I WANT to understand it. :) I
> suspect
> it's pretty basic.
>
>
> Situation: set up a windows 2003 SP2 server ("2003VM5") and two XP clients
> ("XPclient1" and "XPClient2"). Created two virtual LAN segments, connected
> to
> two NICs in server 2003VM5. Each client, TCP/IP configured via DHCP, is
> connected to one of the segments.
>
> I have setup an "COE.NET" AD domain, a DHCP server with two scopes, and a
> DNS server installed by the AD wizard.
>
> NICs in server 2003VM: static IPs
>
> 172.22.0.10
> 255.255.254.0
> (gateway empty)
> DNS servers 172.22.0.10,172.22.2.10
>
> 172.22.2.10
> 255.255.254.0
> (gateway empty)
> DNS servers 172.22.2.10,172.22.0.10
>
> DHCP two scopes:
>
> scope 172.22.0.0
> address range 172.22.0.1 - 172.22.1.254
> exclusions 172.22.0.1 - 172.22.1.0
> scope options:
> router 172.22.0.10
> DNS servers 172.22.0.10,172.22.2.10
> DOMAIN NAME COE.NET
>
> scope 172.22.2.0
> address range 172.22.2.1 - 172.22.3.254
> exclusions 172.22.2.1 - 172.22.3.0
> scope options:
> router 172.22.2.10
> DNS servers 172.22.2.10,172.22.0.10
> DOMAIN NAME COE.NET
>
> (almost) Everything seems fine. The two XPClients have been joined to the
> domain without problems, they both get leases from the proper scopes
> ("XPclient1"=172.22.1.1 and "XPClient2"=172.22.3.1) with TCP/IP settings
> looking good. From both clients I can do a "ping 2003VM5" and get replies
> after correct name resolution:
>
> Pinging 2003VM5.COE.NET [172.22.0.10]
> Pinging 2003VM5.COE.NET [172.22.2.10]
>
> Both clients and both server IP's show up in the DNS forward lookup
> zone...
> I really can't see anything wrong.
>
> YET, when I ping XPClient2 from server 2003VM5:
>
> =======================================================
> C:\Documents and Settings\networkadmin>ping XPclient2
>
> Pinging XPclient2.COE.NET [172.22.3.1] with 32 bytes of data:
>
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> =======================================================
>
> What's going on here? XPClient1 gives no trouble at all! I thought it
> might
> have something to do with the multihoming. So I installed RRAS for "LAN
> Routing", but no change.
>
> Any suggestions, because I don't feel like continuing to experiment with
> other subjects before this basic problem is solved (who knows what it
> might
> cause later on)...
>
> TIA
Re: 2003 server multihoming issue? [message #163543 is a reply to message #163541] Wed, 03 June 2009 07:10 Go to previous messageGo to next message
JHman  is currently offline JHman
Messages: 19
Registered: July 2009
Junior Member
I think I'm going to throw myself off some bridge...

I was absolutely convinced that I had done everything to make my clients
identical, but somewhere along the way I had only DISabled it on XPclient1,
or only ENabled it on XPClient2. :( (because yes, that was the issue!!)

I deserve a lot of spanking for this one.


"Dusko Savatovic" wrote:

> Did you disable firewalls on XP clients?
>
Re: 2003 server multihoming issue? [message #163552 is a reply to message #163543] Wed, 03 June 2009 08:06 Go to previous message
Dusko Savatovic  is currently offline Dusko Savatovic  Croatia
Messages: 323
Registered: July 2009
Senior Member
Don't worry,

I embarrased myself with this one exactly in front of a full class of
students.
You can now try firewall exercises.
enable selectively:
ping (but without file sharing)
remote admin
remote desktop

Good luck with your training
DuskoS

"JHman" <JHman@discussions.microsoft.com> wrote in message
news:78FD816E-7992-454F-9010-24DDB05EB9EC@microsoft.com...
>I think I'm going to throw myself off some bridge...
>
> I was absolutely convinced that I had done everything to make my clients
> identical, but somewhere along the way I had only DISabled it on
> XPclient1,
> or only ENabled it on XPClient2. :( (because yes, that was the issue!!)
>
> I deserve a lot of spanking for this one.
>
>
> "Dusko Savatovic" wrote:
>
>> Did you disable firewalls on XP clients?
>>
Previous Topic:Is there a command to dump various process information shown in ta
Next Topic:It appears that by default UAC for Server 2008 is OFF by default?
Goto Forum:
  


Current Time: Sat Aug 19 05:13:16 EDT 2017

Total time taken to generate the page: 0.04909 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software