Any Active Directory Setup Experts here?

Joe Mamma

Well-known member
Joined
Mar 1, 2004
Messages
1,062
Location
Washington DC
I have two network adapters.
The both appear registered properly in DNS.
if I ping my pdc it returns the hex values for the address :
Code:
C:\>ping antares
Pinging antares.lan.obj-tec.com [fe80::290:47ff:fe02:c6a1] 
Reply from fe80::290:47ff:fe02:c6a1: time<1ms
but if I ping the ip address of either nic it returns correct:
Code:
C:\>ping -a 192.168.2.101
Pinging antares.lan.obj-tec.com [192.168.2.101] with 32 bytes of data:
Reply from 192.168.2.101: bytes=32 time<1ms TTL=128
heres my IPconfig -

Code:
Ethernet adapter Intel:
Connection-specific DNS Suffix . :
  IP Address. . . . . . . . . . . . : 192.168.2.102
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  IP Address. . . . . . . . . . . . : fe80::207:e9ff:fe53:8d2a%4
  Default Gateway . . . . . . . . . : 192.168.2.1
Ethernet adapter RealTek:
Connection-specific DNS Suffix . :
  IP Address. . . . . . . . . . . . : 192.168.2.101
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  IP Address. . . . . . . . . . . . : fe80::290:47ff:fe02:c6a1%5
  Default Gateway . . . . . . . . . : 192.168.2.1
Tunnel adapter Automatic Tunneling Pseudo-Interface:
  Connection-specific DNS Suffix . :
  IP Address. . . . . . . . . . . . : fe80::5efe:192.168.2.102%2
  Default Gateway . . . . . . . . . :
Tunnel adapter Automatic Tunneling Pseudo-Interface:
  Connection-specific DNS Suffix . :
  IP Address. . . . . . . . . . . . : fe80::5efe:192.168.2.101%2
  Default Gateway . . . . . . . . . :
any ideas?
 
PlausiblyDamp said:
Looks like you have IPv6 installed on both the client and server - hence the weird hex results.
so this is correct then? cool.

Yes I beleive IPv6 is installed as integrated into Server 2003 TCP/IP configuration now and not an add on option as it was previously.
 
Back
Top