Thank you for posting the information.
Couple problems. See below where I noted the problems and possible fixes.
In
Daniel Tan said:
Nslookup:
Can't find server name for address 192.168.1.2:Non-existent domain
Default server : localhost
Address : 127.0.0.1
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : mp419b
Primary DNS Suffix . . . . . . . :
Your Primary DNS Suffix is missing Daniel. Is this machine a domain
controller? If it is, this condition is called a Disjointed Namespace and
this will cause major issues. If it is a domain controller, please see this
article on how to create a script to immediately fix this problem:
257623 - Domain COntroller's Domain Name Suffix Does Not Match Domain Name
[including script to fix it]:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;257623
more below...
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8029(AS) PCI Ethernet
Adapter #2
Physical Address. . . . . . . . . : 00-00-21-EB-0F-BC
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.6
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.2
Primary WINS Server . . . . . . . : 192.168.1.2
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8029(AS) PCI Ethernet
Adapter
Physical Address. . . . . . . . . : 00-00-21-ED-06-22
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 127.0.0.1
192.168.1.2
Remove the 127.0.0.1 address above. The ONLY address should show is
192.168.1.2. This is WHY you are getting domain not found in nslookup.
Primary WINS Server . . . . . . . : 192.168.1.2
PPP adapter ZTE ADSL:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 218.111.5.213
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 219.93.218.177
DNS Servers . . . . . . . . . . . : 202.188.0.133
202.188.1.5
Curious, why do you have two NICs in this machine if you have a DSL line ?
If you have the software installed for PPPoE, then you do not need two NICs
to setup NAT. The PPPoE connection (the one above) is the "outside"
connection.
Daniel, I would suggest to purchase a $39.00 (US currency) Linksys DSL/Cable
Router and connect that to the DSL modem. You can configure the router to
establish the PPPoE connection. This way you can remove the extra NIC from
your machine and your machine will not have to NAT for you because the
Linksys router will perform this function. It is the EASIEST way to do this.
Many many administrators use this method. It is very very affordable and
doing this will lessen the load on your Windows machine and let the WIndows
machine do what it knows best, be a domain controller or a server. It is
also much more secure to use the Linksys router since it will protect your
Windows machine.
--
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.