dns problem

Posted on 2011-02-11
Last Modified: 2012-05-11
i have created one dhcp super scope as
scope 1 ip address
              subnet mask

scope 2 ip address
              subnet mash  255.255.0

Having windows server 2003 after migrated from Win NT .only one lan card installed in the server and single domain name (not fully quilified name )
clint pc not interconnected /access between both scopes ip
both clients pinging  and acess through ip only like \\ip Etc..
Clients not acess through host name like \\AMITHPC
and both subnet on same physical lan
Our DHCP configured as below:
Scope 1:
IP Range- to
exclude Range- to
Subnet -
Scope 2
IP Range- to
exclude Range- to
Subnet -
And both subnet on same physical LAN AND
Having windows server 2003 after migrated from Win NT and single domain name (not fully quilified name ) as     abc.domain

in dns forward lookupzone  A record for to 10.91.238..254  ip not update dynamically .
Question by:sachinsingh
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2

Author Comment

ID: 34869819
pls help
LVL 10

Expert Comment

ID: 34869901
are both subnets having the same problem? there will be no communication between two different subnets, unless you setup a static route.. preferably a persistent one  have you tried to configure one of the workstations with a static ip address with the correct dns entries? then try to ping the server using the computer name. have you tried pinging a workstation from the server?

Author Comment

ID: 34870517
Yes I have tried pinging workstation from server end both scope is pinging properly
LVL 10

Accepted Solution

cbmm earned 500 total points
ID: 34870520
is there a software firewall enabled on the server/workstation?

Author Closing Comment

ID: 35413139
yes problem is resolved

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I will assume you are running a non-server version of some sort of Windows throughout this article. There are many flavors of Windows since Windows Server 2000 - 2008, XP Home & Pro, Vista Home & Pro, and Windows 7 Starter, Home, Pro, Ultimate, etc.…
Resolve DNS query failed errors for Exchange
NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question