Announcement

Collapse
No announcement yet.

NLB in exchange 2003 front end server

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • NLB in exchange 2003 front end server

    I am trying to build NLB in exchange 2003 frontend servers. Whenever i add the cluster ip the connection to network is lost, like the machine wont be able to connect to DNS or gateway. I have added the record in DNS aslo, waiting for a solution

    Thanks,
    Binil

  • #2
    Re: NLB in exchange 2003 front end server

    How many nics do you have in the sever?
    Are you using unicast or multicast?

    Michael
    Michael Armstrong
    www.m80arm.co.uk
    MCITP: EA, MCTS, MCSE 2003, MCSA 2003: Messaging, CCA, VCP 3.5, 4, 5, VCAP5-DCD, VCAP5-DCA, ITIL, MCP, PGP Certified Technician

    ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

    Comment


    • #3
      Re: NLB in exchange 2003 front end server

      have you set each NIC with its own IP address and "The Team" with an IP of its own? Does the DNS record point to "The Team"?


      Tom
      For my own and your protection, I do not provide support by private message under any circumstances. All such messages will be deleted and ignored.

      Anything you say will be misquoted and used against you

      Comment


      • #4
        Re: NLB in exchange 2003 front end server

        Originally posted by m80arm View Post
        How many nics do you have in the sever?
        Are you using unicast or multicast?

        Michael
        I have 3 nics totally. out of which 2 iam using. One for Public and one for Private.

        Comment


        • #5
          Re: NLB in exchange 2003 front end server

          Originally posted by m80arm View Post
          How many nics do you have in the sever?
          Are you using unicast or multicast?

          Michael
          I m using Unicast.

          Comment


          • #6
            Re: NLB in exchange 2003 front end server

            For unicast NLB, this is the setting I used,

            VLAN 2: NLB -> if you are not goign to use a dedicated switch use seperate VLAN so it won't flood the whole ports on the swith.
            VLAN 1: WAN

            Make sure VLAN1 and VLAN2 can talk to each others.

            Machine A, NIC 1 -> use it for unicast nlb : VLAN 2
            Machine A, NIC 2 -> use it for communication between FE, BE and RDP: VLAN1

            Machine B, NIC 1 -> use it for unicast nlb : VLAN 2
            Machine B, NIC 2 -> use it for communication between FE, BE and RDP : VLAN1

            Machine C, NIC 1 -> use it for unicast nlb : VLAN 2
            Machine C, NIC 2 -> use it for communication between FE, BE and RDP : VLAN1

            I am using all FE servers for outgoing, so each NIC 2 need external IPs and SPF records. (BE servers do not send emails to out side)

            M$ does not recommand using NIC load balancing/fail over for NLB.

            If you want to use multi cast, you use only one nic on each machine, and add virtual MAC address to the ARP table on your switch.

            Good luck
            Last edited by hyeongkim; 24th March 2007, 04:39. Reason: syntax error
            MCP, MCSA+messaging, MCDBA, OCA.

            Comment

            Working...
            X