Re: get IPaddress
From: Doug Marks (anonymous_at_discussions.microsoft.com)
Date: 09/16/04
- Next message: Kevin D. Goodknecht Sr. [MVP]: "Re: The DNS server machine currently has no DNS domain name"
- Previous message: Piet: "The DNS server machine currently has no DNS domain name"
- In reply to: Ace Fekay [MVP]: "Re: get IPaddress"
- Next in thread: Ace Fekay [MVP]: "Re: get IPaddress"
- Reply: Ace Fekay [MVP]: "Re: get IPaddress"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 16 Sep 2004 05:52:50 -0700
This is neither a DNS or DC it is a simple application
server running the Siebel v7.0. Also, on the private LAN
configuration the checkbox "Register this connection's
addresses with the DNS" is unchecked. On the public NIC
this box is checked. The network named "VLAN" is the
private network.
As requested, ipconfig:
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : a0185-app0344-s
Primary DNS Suffix . . . . . . . :
gldc.ad.allstate.com
Node Type . . . . . . . . . . . . : Peer-Peer
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . :
gldc.ad.allstate.com
ad.allstate.com
allstate.com
Ethernet adapter VLAN:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Compaq NC3134
Fast Ethernet NIC #2
Physical Address. . . . . . . . . : 00-08-02-CD-CF-
B3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.200.44
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Ethernet adapter Corporate LAN:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Compaq NC3134
Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-08-02-CD-CF-
B2
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.66.70.218
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 10.66.70.1
DNS Servers . . . . . . . . . . . : 10.64.96.194
10.64.80.220
Primary WINS Server . . . . . . . : 10.64.80.220
Secondary WINS Server . . . . . . : 10.64.96.194
Ethernet adapter Loopback:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft
Loopback Adapter
Physical Address. . . . . . . . . : 02-00-4C-4F-4F-
50
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration IP Address. . . : 192.168.200.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Autoconfiguration IP Address. . . : 192.168.100.23
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
>-----Original Message-----
>In news:029201c49b50$af773290$a301280a@phx.gbl,
>Doug Marks <dma2i@allstate.com> made a post then I
commented below
>> The scenario is, a multihomed machine where the second
NIC
>> is in a private LAN using the 192.168... addresses. The
>> DNS name for this machine is a0185-app0344-s(using
>> 10.66.?.? class A network) the host file, for the
private
>> LAN) is set to resolve app0344-pn to 192.168.200.44. If
>> you ping "a0185-app0344-s" from inside the box it
resolves
>> to the 192.168. address, but from the outside it
resolves
>> the 10.66 address. I have found the same results via C#
>> code running the "GetIPAddress" function. The problem is
>> that if I ping or get the IP via code for "a0185-
app0344-
>> s" how can it resolve the private LAN IP of
192.168.200.44
>> when it is not associated with that machine name? This
>> really causes issues in one of our tools that checks IP
>> addresses because it runs as a service locally on each
>> server it always returns the private IP and I need the
>> public. ANY ideas???
>
>Since DNS is aware of the querying client's IP address,
and there are two
>records for this machine name under the zone, DNS tries
to give the best
>answer based on the querying machine's IP subnet.
>
>Is this server a DNS server or a DC or both? Is there a
reason this DNS, if
>it is a DC or DNS server, is multihomed? Just to point
out, (discussed a few
>times in this group), multihoming a DC/DNS, if it is
that, is very
>problematic, including with some machines that serves a
production app.
>There are steps you can follow on this DC or server,
including some registry
>changes to only force the internal IP to register into
DNS so only that
>record responds.
>
>If the machine is a NAT server, it would be beneficial
and alot less
>headaches to get a Linksys, Netgear, etc, router to
perform NAT for you and
>single home this server.
>
>If you can confirm my assumptions, or able to give us an
ipconfig /all, that
>would help towards a diagnosis. Thanks!
>
>--
>Regards,
>Ace
>
>Please direct all replies ONLY to the Microsoft public
newsgroups
>so all can benefit.
>
>This posting is provided "AS-IS" with no warranties or
guarantees
>and confers no rights.
>
>Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I,
MCT, MVP
>Microsoft Windows MVP - Windows Server - Directory
Services
>
>Security Is Like An Onion, It Has Layers
>HAM AND EGGS: A day's work for a chicken;
>A lifetime commitment for a pig.
>--
>=================================
>
>
>.
>
- Next message: Kevin D. Goodknecht Sr. [MVP]: "Re: The DNS server machine currently has no DNS domain name"
- Previous message: Piet: "The DNS server machine currently has no DNS domain name"
- In reply to: Ace Fekay [MVP]: "Re: get IPaddress"
- Next in thread: Ace Fekay [MVP]: "Re: get IPaddress"
- Reply: Ace Fekay [MVP]: "Re: get IPaddress"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
