Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Windows 2008 R2 - OS returns backup ip to application instead of production ip.

Proposed Answer Windows 2008 R2 - OS returns backup ip to application instead of production ip.

  • Wednesday, February 20, 2013 3:59 PM
     
     
    Sign In to Vote
    0

    Hi,

    An application makes api calls to OS get / connect to IP. The app uses port in the range 9986 ~ 9999.

    Issue :

    The application which runs on the server during startup/service restart  establishes connection over backup ip “eg:169.30.xxx.xx” over the port 9999 which is not expected. Ideally it should use the production IP “eg: 169.108.xxx.xx”.

    Background:

    The application uses few ports between 9986 – 9999. The application makes api calls to the OS to get the IP for communication. No particular ip’s have been hardcoded into application.

    Current work around:

    Backup NIC is disabled. While the backup NIC is disabled state, the application runs as expected over production ip. But, both the NICS are required for successfully connecting / backing up of the system.

    Server details:

    Type :  Virtual Machine

    OS Name:   Microsoft Windows Server 2008 R2 Enterprise

    OS Version:  6.1.7601 Service Pack 1 Build 7601

    System Type:  x64-based PC

    No. of NIC cards : 2

    Checked the following and found ok,

    1. Checked binding order (found ok – prod nic on top )
    2. Set the lower metric to prod nic and higher metric value to backup nic
    3. Disable “BFE” service
    4. Tried Modified routes in the routing
    5. Tried tcp/ip tuning (time out, tcp window etc) as per http://msdn.microsoft.com/en-us/library/ee377084.aspx  ( Issue still persists)

    Need quick help in fixing the issue. So, that the application uses only production ip for communication.

     

All Replies

  • Thursday, February 21, 2013 2:27 AM
     
     Proposed Answer
    Sign In to Vote
    0

    On a ipconfig /all does that IP is listed ? (you don't have a second ip configured on your prod nic??) (169.30.x.x)

    Under a netstat -ano does it's listening on 169.30.x.x. too? 

    In the bind order, the backup nic is first I guess ? Put the prod's nic first please.

    Do you use hyper-v ? both nic are the same type (not like a legacy's nic in example)

    MCP | MCTS 70-236: Exchange Server 2007, Configuring

    Twitter - @yagmoth555 ()
    Blog: http://www.jabea.net | http://blogs.technet.com/b/wikininjas/

     
  • Friday, February 22, 2013 9:43 AM
    Moderator
     
     Proposed Answer
    Sign In to Vote
    1

    Hi Mahesh,


    Based on my understanding, this virtual machine has two NICs and they connect to two different networks. This application is used to choose which network for communication. If the two networks are all function properly, it should choose the primary network (169.108.0.0). However, it chooses 169.30.0.0 instead. If there is any misunderstand, please feel free to let me know.


    If the above is true, would you please provide us ipconfig /all and route table.


    Also, I suspect that the issue is related to the application itself. If the app is developed by you, it is recommended to address the issue in our MSDN related forums for better assistance. Or you can contact the developer for help.


    Hope this helps.

    Jeremy Wu
    TechNet Community Support


     
  • Monday, February 25, 2013 6:13 AM
     
     
    Sign In to Vote
    0

    Hello Jeremy,

    Your understanding is exactly right.

    I did verify the route table and didn't find anything unusual.

    Here is the output :

    1) ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : xxx
       Primary Dns Suffix  . . . . . . . : yyy.AD.xxx.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : server.yyy.xxx.net
                                           xxx.net
                                           yyy.ad.xxx.com
                                           uk.xxx.com
                                           xxx.com
                                           ny.xxx.com
                                           xxx.com

    Ethernet adapter Production:

       Connection-specific DNS Suffix  . : server.yyy.xxx.net
       Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter
       Physical Address. . . . . . . . . : 00-50-56-B6-34-F1
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : yyy.93.xx.xxx(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.248.0
       Default Gateway . . . . . . . . . : yyy.93.xx.x
       DNS Servers . . . . . . . . . . . : yyy.93.xx.xx
                                           yyy.93.xx.xx
                                           yyy.93.xxx.xx
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Bkup:

       Connection-specific DNS Suffix  . : server.yyy.xxx.net
       Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter #3
       Physical Address. . . . . . . . . : 00-50-56-09-0D-33
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : yyy.30.xxx.xx(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.248.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled

    2) Route print :

    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0      xxx.93.48.1    xxx.93.55.134    261
            127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
            127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
      127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
         xxx.30.104.0    255.255.248.0         On-link     xxx.30.110.22    261
        xxx.30.110.22  255.255.255.255         On-link     xxx.30.110.22    261
       xxx.30.111.255  255.255.255.255         On-link     xxx.30.110.22    261
          xxx.93.48.0    255.255.248.0         On-link     xxx.93.55.134    261
        xxx.93.55.134  255.255.255.255         On-link     xxx.93.55.134    261
        xxx.93.55.255  255.255.255.255         On-link     xxx.93.55.134    261
            224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
            224.0.0.0        240.0.0.0         On-link     xxx.30.110.22    261
            224.0.0.0        240.0.0.0         On-link     xxx.93.55.134    261
      255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      255.255.255.255  255.255.255.255         On-link     xxx.30.110.22    261
      255.255.255.255  255.255.255.255         On-link     xxx.93.55.134    261
    ===========================================================================
    Persistent Routes:
      Network Address          Netmask  Gateway Address  Metric
              0.0.0.0          0.0.0.0      xxx.93.48.1  Default
    ===========================================================================

     
  • Monday, February 25, 2013 6:50 AM
     
     
    Sign In to Vote
    0

    Apart from setting metric on network adapters and changing the binding order (which i have already tried), Is there any other way of telling OS that "x is the primary adapter" and "y is the secondary adapter" ?

     
  • Tuesday, February 26, 2013 2:42 AM
    Moderator
     
     Proposed Answer
    Sign In to Vote
    0

    Hi Mahesh,


    Thanks for your reply.


    From the ipconfig /all and route table, I agree with that all seem to be OK.


    Also, as far as I know, binding order and metric are the methods to determine the primary connection.


    Therefore, as I mentioned before, I suspect that the issue may relate to the App itself. Would you please let us know more details about the App? What is the design? Does it work on other machines? If you do not mind, would you please share it?


    Thanks.

    Jeremy Wu
    TechNet Community Support



     
  • Thursday, February 28, 2013 2:39 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi Mahesh,


    Is there any update?


    Thanks.

    Jeremy Wu
    TechNet Community Support

     
  • Thursday, February 28, 2013 10:03 AM
     
     
    Sign In to Vote
    0

    Hello Jeremy,

    The app works well on other existing 2008 servers.

    While working on this, I found one hint previous day.

    The windows box is a VM, While i was going through the vmx file (hardware config file).. I found the same MAC address is assigned to both interface (I did remove / add nics earlier to assign static mac during server build). But, i am not sure if resolving this duplicate mac would fix my current issue. I will try out to fix / rule out the mac issue by tomorrow and. The virtual harware revision is : 8.

    vmx Ethernet config:

    ethernet0.present = "TRUE"

    ethernet0.virtualDev = "vmxnet3"

    ethernet0.networkName = "VMWARE PRD VLAN401"

    ethernet0.addressType = "vpx"

    ethernet0.generatedAddress = "00:50:56:a1:13:e9"

    ethernet0.pciSlotNumber = "192"

    ethernet0.address = "00:50:56:09:0D:33"

    ethernet1.present = "TRUE"

    ethernet1.virtualDev = "vmxnet3"

    ethernet1.pciSlotNumber = "224"

    ethernet1.startConnected = "TRUE"

    ethernet1.allowGuestConnectionControl = "TRUE"

    ethernet1.features = "1"

    ethernet1.wakeOnPcktRcv = "TRUE"

    ethernet1.addressType = "vpx"

    ethernet1.generatedAddress = "00:50:56:a1:13:ec"

    ethernet1.networkName = "VMWARE BKP VLAN607"

    ethernet1.address = "00:50:56:09:0D:33"

     
  • Friday, March 01, 2013 6:08 AM
     
     
    Sign In to Vote
    0

    I ruled the multiple mac address issue by clearing them through vmx file.

    Hard luck .. The issue is still the same.

    Any other guess ??