Announcement

Collapse
No announcement yet.

cannot access natted network on Hyper-V

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

  • cannot access natted network on Hyper-V

    2008r2 Hyper-V HOST - in domain on 192.168.1.0/24

    Exchange 2k3 on natted 10.1.0.0/24 network domain

    Exchange and DC for it placed on internal network of this host and routing and remote access is on for NAT existance.

    1. 10.1.0.0 machines can browse internet.

    2. can telnet Exchange server 10.1.0.3 25 from HOST 192.168.1.50

    3. cannot telnet Exchange server from other 192.169.1.0 machines.

    What was tried:

    In Routing and Remote access of Host I enabled Inbound filters on 192.168.1.50 interface (that is Management and VMs interface for the lab purpose).

    Probably I missing something here...
    I choose:
    FILTER ACTION:
    Drop all packets except those that meet the criteria below:
    Source address 192.168.1.0 Mask 255.255.255.0
    Destination address: 10.1.0.0 Mask 255.255.255.0
    Protocol: ANY (first tried TCP 25, when this didn't work tried ANY)

    I am out of ideas...

    What I am missing.

    Thanks.
    "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

  • #2
    Re: cannot access natted network on Hyper-V

    solved by
    adding the route to a client on the 192.168.1.x:
    route add 10.1.0.0 mask 255.255.255.0 192.168.1.50
    "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

    Comment


    • #3
      Re: cannot access natted network on Hyper-V

      Just stick -p at the end of that route to make it persistant and save re-entering it after every reboot
      Tom Jones
      MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
      PhD, MSc, FIAP, MIITT
      IT Trainer / Consultant
      Ossian Ltd
      Scotland

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

      Comment


      • #4
        Re: cannot access natted network on Hyper-V

        Ossian,
        now I would like to enable email traffic from internet to Exch2003 that resides on 10.1.0.0

        1. I can access e-mail from this server by OWA client on 192.168.1.0
        2. I can send messages to Internet from it

        MX record in zone file points to Public address of the firewall. Port 25 was open for
        192.168.1.x address when tested Exchange on 192.168.1.0 and it worked.

        Now my exchange is on 10.1.0.0 I am not sure what to do.

        Thx.
        "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

        Comment


        • #5
          Re: cannot access natted network on Hyper-V

          So what is the problem -- Outlook?
          Tom Jones
          MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
          PhD, MSc, FIAP, MIITT
          IT Trainer / Consultant
          Ossian Ltd
          Scotland

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

          Comment


          • #6
            Re: cannot access natted network on Hyper-V

            I need to enable mail traffic from internet to Ex2003 - 10.1.0.3 through Firewall 192.168.1.1

            Initial routing problem - access Exchange on 10..x.x.x from 192.x.x.x solved.

            On firewall should I map host address or Exchange itself to Public address of Firewall?
            Last edited by mla; 2nd November 2010, 21:08.
            "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

            Comment

            Working...
            X