Re: IP resolution on virtual dedicated server
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Wed, 9 Apr 2008 01:59:53 -0500
"EDWARD HYMAN" <EdwardH@xxxxxxxxxxxxxxxxx> wrote in message
news:uW3EP5cmIHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
Herb,
ipconfig/full info:
Windows IP Configuration
Host Name . . . . . . . . . . . . : techiechatnet
Primary Dns Suffix . . . . . . . :
Ethernet adapter Local Area Connection:
IP Address. . . . . . . . . . . . : 69.65.105.219
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 69.65.105.211
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 69.65.115.1
The default gateway above is INCORRECT or the Subnet
MASK is incorrect or the station has been given IP addresses
on the WRONG network.
A client must be on the same "subnet" with it's Default Gateway --
the default gateway is the Router (of last resort) that sends traffic
from the client to OTHER (sub)networks.
Can you ping the DNS server or the gateway above?
DNS Servers . . . . . . . . . . . : 205.177.13.2
205.234.103.204
The DNS servers LOOK very suspicious -- and if you have the
routing problem above then they are unreachable which would be
fatal even if they are correct.
They look suspicious because they MIGHT be "external" and not
the ones that are holding the INTERNAL ZONE for the Domain.
Also you have a (slight) problem in that you have failed to set the
"Primary DNS Suffix" in the SYSTEM Control Panel.
NetBIOS over Tcpip. . . . . . . . : Disabled
If you want BROWSING to work (not the problem you reported)
then you will need ALL machines to enable NetBIOS and if you
wish it to work across routers then you will need all to register with
WINS (this includes ESPECIALLY DCs.)
dcdiag.exe info:
Domain Controller Diagnosis
You must run DCDiag on (or against) a DC, not an ordinary workstation.
Performing initial setup:
***Error: techiechatnet is not a DC. Must specify /s:<Domain Controller>
or
/n:<Naming Context> or nothing to use the local machine.
Your assistance is much appreciated.
Ed
--
Edward Hyman
EMail: e.hyman@xxxxxxxxxxxxxxxx
"Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message
news:u8IpWGbmIHA.2504@xxxxxxxxxxxxxxxxxxxxxxx
"EDWARD HYMAN" <EdwardH@xxxxxxxxxxxxxxxxx> wrote in message
news:eLoGViamIHA.3780@xxxxxxxxxxxxxxxxxxxxxxx
> I am attempting to establish my domain name on my virtual dedicated
> server.
> I cannot get the DNS to resolve to my assigned IPs. > Assistance would
be
> most appreciated.
Virtual Servers are conceptually JUST LIKE any other servers.
Post your full IPConfig /all (unedited) and check your DCDiag for
no FAIL or WARN errors.
DCs and all domain clients MUST use strictly the INTERNAL (for
them) DNS Server (set) which can both accept the DYNAMIC
registration for their domain and resolve that domain for them.
.
- References:
- IP resolution on virtual dedicated server
- From: EDWARD HYMAN
- Re: IP resolution on virtual dedicated server
- From: Herb Martin
- Re: IP resolution on virtual dedicated server
- From: EDWARD HYMAN
- IP resolution on virtual dedicated server
- Prev by Date: Re: Exam 70-291
- Next by Date: DNS tests - need to confirm all is OK
- Previous by thread: Re: IP resolution on virtual dedicated server
- Next by thread: Ping fails to resolve name but nslookup OK
- Index(es):