How do I specify which IP address or Network Card that Windows Server 2003 should listen on?

Thanks for your response, there actually isn't any VLAN or NAT going on to segregate the traffic. The reason the IP addresses are on separate NICs is only for statistics and metering (i.e. trending customer bandwidth vs. management bandwidth). The reason for this is that due to the nature of the services we provide, we are prone to being the target of DDoS attacks. I also would like to be able to specify the IP that SNMP listens on so that I can track in my database exactly which addresses I should be targeting. For some reason SNMP always just seems to pick up the first IP address on the first network card in the system. Any thoughts on that?

Are they all on the same subnet?

Generally speaking...

Interface-specific services usually have configuration settings to specify the interface.  

Non-interface-specific services will usually grab the first-bound address in the subnet the service's configured address resides in, regardless of interface.   If you don't specify any addresses for such a service, it will grab the first-bound address on the first-bound interface.  Or, if it's a routable protocol, it will grab the interface and address that has the shortest path to the target address, which might be the one with the default route (gateway).

So are you saying that the Windows SNMP service listener (the service that accepts SNMP requests) is interface specific then? If so, can I specify the interface it should listen on instead of allowing it to just bind to the first one available?

Thanks, Jason

No, I'm saying it's not.  It doesn't have configuration settings to bind it to a specific interface.

Are your customer IP's and management IP's on separate subnets?  Is/are your SNMP management server(s) on (a) management-subnet address(es) or on (a) customer-subnet address(es)?  Have you specified what the management host(s) is/are?

Any application, unless it has the capability to chose from an assigned ip would only pass on a request to OS for available IP addresses. Now there are different applications that'd listen to which IP address you want to assign it to (for example, licensing based on IP address).

In short the logic has to be in the application, otherwise, it is first come basis.

Cheers,
rsivanandan

the IP's are on the same subnet

j

I think that my question is being misunderstood so I'm going to try and explain it again using an example... I have a server in Dallas, TX with Windows Server 2003 Standard Edition on it. This server is connected to the internet by two network adapters (the network configuration is listed in the code snippet section). My goal is, from my remote machine in Cleveland, OH to make SNMP requests to IP 69.12.15.131. The problem with this is that the SNMP service on the server is ONLY responding to requests sent to 69.12.25.2

I know that I can change the port that SNMP listens on by modifying the services file but what I need to do is to change the IP address that SNMP is listening on. I have a theory that I may be able to use IPSec to do this but I am in the midst of performing that experiment now. Also, these two network cards are connected to the same fiber on the same switch (although in this specific case one of the cards has an IP on a separate subnet, this is not the case for other servers with the same problem).

Any help or thoughts are greatly appreciated!

Thanks, Jason

Windows IP Configuration
 
   Host Name . . . . . . . . . . . . : DFW860-JQ22CC1
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
 
Ethernet adapter Management WAN:
 
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
   Physical Address. . . . . . . . . : 00-15-C5-FB-AB-C8
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 69.12.15.131
   Subnet Mask . . . . . . . . . . . : 255.255.255.224
   Default Gateway . . . . . . . . . : 69.12.15.129
   DNS Servers . . . . . . . . . . . : 64.81.127.2
                                       69.12.12.50
 
Ethernet adapter Hosting WAN:
 
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2
   Physical Address. . . . . . . . . : 00-15-C5-FB-AB-C7
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 69.12.25.2
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IP Address. . . . . . . . . . . . : 69.12.15.130
   Subnet Mask . . . . . . . . . . . : 255.255.255.224
   Default Gateway . . . . . . . . . : 69.12.25.1
   DNS Servers . . . . . . . . . . . : 64.81.127.2
                                       69.12.12.50

                                              

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:

Additionally, netstat is showing snmp.exe listening on 0.0.0.0