My win 2k server is pinging but is not accessible from client machines.
Displays '\\<Server Machine Name> The network name cannot be found'. This
problem is preventing any new machine to be added to the domain.

This is a simple, zero-cost, solution used to access Winndows (NT, 98,
2000, 2003, XP)TCP/IP networks  based laptop/notebook/computer at
Different Locations  (Home, School, Office, etc.) - assuming the
networks have different default gateways.

I have a W2K3 network with 2 DCs running DNS PRi and Sec with reverse lookup
zones.
Recently we decommissioned our main DC which i will call - SrvA(FSMO).
I transferred FSMO roles to SrvB. SrvC was brought on line and promoted to

If I right click on a zone and click new domain. Is that considered a zone?
What is the difference in right clicking "forward lookup zones" and creating
it from there?
thx all.

Is it possible to implement dynamic DNS with Windows 2000 Server DNS?
Thanks,
Eran

I have a few A records that I manually added go missing. They are static
IP's that are excluded from the DHCP scope. DNS is AD integrated in a W2k3
Domain.
It seems to only be the machine name that goes missing, not other A records

When I include the following two entries into my "hosts" file
   192.168.1.22    zzyzx
   192.168.1.22    zzyzx.com
the first hostname (the one without dots) is being resolved just fine,

I need to be able to have several workstations in my area allowed zone
transfers from our external DNS servers.  Currently I am testing with the
command below (example IP's) and always get the same error.
dnscmd 192.168.1.3 /ZoneResetSecondaries paultest.com /SecureList

Enviroment: 2 networks connected through VPN. Both networks are Windows 2003
based
on AD.
I have a problem that it thing might be solved with the right use of DNS. I

What a great newgroup!
One Win2k3 DC with AD integrated DNS.
straight, pre sp1.
the domain is  behind a hardware firewall box,

Does anyone know how to solve the following error message?
The DNS server encountered an invalid domain name in a packet from
192.33.4.12.  The packet is rejected.

For a temporary solution I was hoping to do use DNS to kind of not
allow users to go to certain websites.
Has anyone done this before?  If so how would I add something in DNS
to return an ip address to the user of 127.0.0.1 for websites like

My Win2K domain controller - call it abc.xyz.com - is running DNS for
the LAN.  From a client machine I can, for example, "ping abc" and get
resolution and responses.  But, when I "ping abc.xyz.com" the DNS
server cannot resolve this.

at present, i place the DNS records in our internet services provider.  but
they charged us.
now i own more and more domains.
i plan to migrate the DNS records to a new server(True IP) in my LAN.

Setup = Win2K forest, 2 DCs [say A and B] on root of domain and 2 DCs
[say C and D] on a child of that root domain. DC 'A' is the domain
naming operations master, AD throughout, no obvious replication
problems. Symptons are differing SOA serial numbers, i.e. not all DCs