Re: AD, DHCP or maybe DNS problem?

I uninstalled Norton totally from the desktop. If it can't connect to the
internet I can't get a virus :)

It looks that your Dns resolution is working well. So the only explanation
that I can remember at this moment is that there is something or some filter
that prevents you from going to the internet. Check Internet options or any
type of configuration internet related that you migh have in your pc.
--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Greg P" <gsp@xxxxxxxxxxxxxxxxx> wrote in message
news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@xxxxxxxxxxxxxxxx
Jorge,

Unfortunately I'm in the same spot that I started in, except we solved the
file sharing issue on Laptop 2 by lowering the Norton firewall. I still
can't access the internet on the desktop or laptop 2, even though they are
on
the dame domain as Laptop 1 which can access the internet. With that
being
said I'm not sure if you still think this is a DNS problem?

Well you said that now you have everything working except Internet, and
you also said that you don't have Proxy or any other thing that
prevents/restricts users to access to the internet, so you must have a DNS
resolution problem.

Do you have Forwarding enabled in the Dns server?

Yes, this is set up with the correct ip addresses.

Test the resolution on the DC - Go to command prompt and type ping
www.microsoft.com - check if returns the Ipaddress of the site
then go to the clients and check if the ping command returns the Ipaddress
of the site.

All resolve the IP address, all requests time out.

Right click on it and choose properties then you should have the "File and
Print Sharing for Microsoft Networks Selected"; however you should
disable/deselect this on the Public Interface (Security purposes).

The File and Print Sharing was selected previously. (there wasn't a
Public
Interface option for this nic, there are only 4 options in the properties
page, Client for MS Networks, Network Lad Balancing, File and Printer
Sharing, and TCP/IP)

Check also if is preventing Internet access or any other access to server
or Dns, etc. Best practices here are for test DISABLE the Norton Firewall
and test, in this way you can immediately check if this as relation with
your current problems.

I uninstalled Norton totally from the desktop. If it can't connect to the
internet I can't get a virus :)


"Jorge Silva" wrote:

In line



What is a multihomed DC?



Is a Domain controller with more than one Nic (Network Interface Card)
card



What do I need to change on my server to mave this work?



Well you said that now you have everything working except Internet, and
you
also said that you don't have Proxy or any other thing that
prevents/restricts users to access to the internet, so you must have a
DNS
resolution problem.



- Do you have Forwarding enabled in the Dns server? If no go to the Dns
console -> right click Dns server choose properties -> select forwarders
tab -> Select All other Domains -> got to the Selected domain's forwarder
Ipaddress list and place the ISP Dns server address -> click add ->
restart
Dns service.



Test the resolution on the DC - Go to command prompt and type ping
www.microsoft.com - check if returns the Ipaddress of the site, then go
to
the clients and check if the ping command returns the Ipaddress of the
site.



Are you saying I shouldn't have WINS and DNS on the same computer?



No. What I said was in a Multihomed DC you could have problems with Wins
and
Dns.


FYI I uninstalled WINS and see the same problem, do I need to remove
some
records somewhere?



You'll only need WINS if you're using any APP in your network that needs
NetBIOS resolution or if you have the need to browse over different
subnets
using for example Network Places.



As for configuring the DNS as you said I already had the interfaces set
to
only use the local Nic.



- Great


As for setting the binding order the internal Nic was at the top of the
list. How do I check to see if file sharing is only on that NIC?



- Right click on it and choose properties then you should have the "File
and
Print Sharing for Microsoft Networks Selected"; however you should
disable/deselect this on the Public Interface (Security purposes).


I had lowered the windows firewall but there was a Norton Firewall that
was
preventing Laptop 2 from Filesharing. That now works. So both the
desktop
and Laptop 2 have the same issues. They get an IP, can perform
Fielsharing
but can't connect to the internet.



Check also if is preventing Internet access or any other access to server
or
Dns, etc. Best practices here are for test DISABLE the Norton Firewall
and
test, in this way you can immediately check if this as relation with your
current problems.



--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Greg P" <gsp@xxxxxxxxxxxxxxxxx> wrote in message
news:25530004-70F9-484D-A87A-26A6B823685F@xxxxxxxxxxxxxxxx
Jorge,

What is a multihomed DC? What do I need to change on my server to mave
this
work? Are you saying I shouldn't have WINS and DNS on the same
computer?
FYI I uninstalled WINS and see the same problem, do I need to remove
some
records somewhere?

As for configuring the DNS as you said I already had the interfaces set
to
only use the local nic.

As for setting the binding order the internal nic was at the top of the
list. How do I check to see if file sharing is only on that NIC?

I had lowered the windows firewall but there was a Norton Firewall that
was
preventing Laptop 2 from Filesharing. That now works. So both the
desktop
and Laptop 2 have the same issues. They get an IP, can perform
Fielsharing
but can't connect to the internet.

Thanks,
Greg

"Jorge Silva" wrote:


- You shouldn't have a multihomed DC.
check:

Also, make sure the internal adapter is at the top of the binding
order
and
that File Sharing is only bound on the internal adapter.
http://support.microsoft.com/default.aspx?scid=kb;en-us;266771

Active Directory communication fails on multihomed domain controllers

http://support.microsoft.com/?id=272294

Name resolution and connectivity issues on a Routing and Remote Access
Server that also runs DNS or WINS

http://support.microsoft.com/kb/292822


- If the machines are running SP2 you need to open the FW to File
share
access.
- Configure the Dns server to listen only on internal adpter (Open Dns
server mmc console -> Right click on Dns server -> choose
properties ->
goto
interfaces tab -> choose only the following IP Addresses, and make
sure
that
you only have the internal interface there)


--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Greg P" <gsp@xxxxxxxxxxxxxxxxx> wrote in message
news:D1DAA442-DF0E-42DC-9725-02A55AFEF4AB@xxxxxxxxxxxxxxxx
Each client machine is running Win XP Pro.

No Proxy devices.

I can access the internet from the server.

Ipconfig on all 4 machines:

Win 2003 Server

Windows IP Configuration

Host Name . . . . . . . . . . . . : Nugget
Primary Dns Suffix . . . . . . . : sbs.net
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : sbs.net
austin.rr.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : austin.rr.com
Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller
Physical Address. . . . . . . . . : 00-XX-8D-DB-16-XX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : xxx.112.216.xxx
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . : 70.112.208.1
DHCP Server . . . . . . . . . . . : 10.37.160.1
DNS Servers . . . . . . . . . . . : 24.93.40.62
24.93.40.63
24.93.40.75
Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006
11:20:40
AM
Lease Expires . . . . . . . . . . : Thursday, June 08, 2006
1:20:40
PM

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI Fast
Ethernet
Adapt
er (rev.F)
Physical Address. . . . . . . . . : 00-xx-46-78-02-xx
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.10.1

Laptop 1

Windows IP Configuration

Host Name . . . . . . . . . . . . : Inspiron6000
Primary Dns Suffix . . . . . . . : sbs.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : sbs.net
sbs.net
sbs.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : sbs.net
Description . . . . . . . . . . . : Broadcom 440x 10/100
Integrated
Cont
roller
Physical Address. . . . . . . . . : 00-XX-43-79-BA-XX
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.10.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DHCP Server . . . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.1
Primary WINS Server . . . . . . . : 192.168.10.1
Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006
11:02:35
PM
Lease Expires . . . . . . . . . . : Monday, January 18, 2038
10:14:07 PM


Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : sbs.net
Description . . . . . . . . . . . : Intel(R) PRO/Wireless
2915ABG
Networ
k Connection
Physical Address. . . . . . . . . : 00-12-F0-49-8B-CC
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.10.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DHCP Server . . . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.1
Primary WINS Server . . . . . . . : 192.168.10.1
Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006
9:19:27
PM
Lease Expires . . . . . . . . . . : Monday, January 18, 2038
10:14:07 PM


Desktop 1

Windows IP Configuration

Windows IP Configuration

Host Name . . . . . . . . . . . . : GREGSDESKTOP
Primary Dns Suffix . . . . . . . : sbs.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : sbs.net
sbs.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : sbs.net
Description . . . . . . . . . . . : Intel(R) PRO/100 VE
Network
Connecti
on


.

Relevant Pages

  • Re: AD, DHCP or maybe DNS problem?
    ... Is a Domain controller with more than one Nic (Network Interface Card) card ... Well you said that now you have everything working except Internet, ... Do you have Forwarding enabled in the Dns server? ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.active_directory)
  • Re: External/Internal Resolution
    ... So how will this effect Resolution and LAN performance. ... >> I have two internet ISP connections, ... >> is the load and security on DNS resolution. ... should I have one DNS server for INTERNAL ...
    (microsoft.public.windows.server.dns)
  • Re: WinXP with WINS
    ... for Name Resolution we use WINS and for Internet Surfing we use ... We do not have internal DNS Server. ... in those PCs in which Internet Connection is provided. ... Name Resolution, the WinXP goes to DNS Server rather than WINS Server. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Multiple Domains and 1 is not working
    ... likely) in Internet Explore ... > If I ping either address: ALPHASITE.com points to the internal IP: ... but merely a DNS zone/domain name. ... You cannot have a DNS resolution point to both an internal ...
    (microsoft.public.windows.server.dns)
  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)