Networking Forums

Networking Forums > Computer Networking > Windows Networking > can not get on to the web on domain controller

Reply
Thread Tools Display Modes

can not get on to the web on domain controller

 
 
Freddie
Guest
Posts: n/a

 
      07-22-2007, 09:30 PM
if I use DHCP on domain controler, I can get on to the web, but if I use the
local DNS or ISP dns I cant get on to the web it indicates page can not be
display,
using Local DNS address or ISP addtress, I can ping to gateway but it does
not let me get out to any other sites. it does not matter if I use IP or name
of any sites,
the Netdiag shows everything ok or I think it looks ok.
only changes I saw between static IP and DHCP is the winserver.
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.100.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.100.1
DNS Servers . . . . . . . . . . . : 192.168.100.2


I sure don't see anything in there
C:\Program Files\Support Tools>netdiag
.....................................

Computer Name: SERVER
DNS Host Name: server.XYANTTech.local
System info : Microsoft Windows Server 2003 (Build 3790)
Processor : x86 Family 15 Model 4 Stepping 3, GenuineIntel
List of installed hotfixes :
KB925902
KB927891
KB930178
KB931784
KB931836
KB932168
KB935966
Q147222


Netcard queries test . . . . . . . : Passed



Per interface results:

Adapter : Local

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : server
IP Address . . . . . . . . : 192.168.100.2
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.100.1
Dns Servers. . . . . . . . : 192.168.100.2


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenge
r Service', <20> 'WINS' names is missing.
No remote names have been found.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{B2E0E4FC-7C2E-49D9-8BA4-A08A4293D060}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation
Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server
'192.168.100.
2'.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{B2E0E4FC-7C2E-49D9-8BA4-A08A4293D060}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{B2E0E4FC-7C2E-49D9-8BA4-A08A4293D060}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully
any hope for me?

thanks
Freddie



 
Reply With Quote
 
 
 
 
Bill Grant
Guest
Posts: n/a

 
      07-22-2007, 11:58 PM
If you are running a domain, all domain members, including the domain
controller itself, should use the local DNS so that AD works properly.

To enable the local DNS to resolve "foreign" URLs, you can set your DNS
to forward to a public DNS service. The local client queries the local DNS,
the local DNS forwards the request to the public DNS server and returns the
reply it receives to the client.

"Freddie" <(E-Mail Removed)> wrote in message
news:8D6C250C-D2D8-4579-A943-(E-Mail Removed)...
> if I use DHCP on domain controler, I can get on to the web, but if I use
> the
> local DNS or ISP dns I cant get on to the web it indicates page can not be
> display,
> using Local DNS address or ISP addtress, I can ping to gateway but it does
> not let me get out to any other sites. it does not matter if I use IP or
> name
> of any sites,
> the Netdiag shows everything ok or I think it looks ok.
> only changes I saw between static IP and DHCP is the winserver.
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.100.2
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.100.1
> DNS Servers . . . . . . . . . . . : 192.168.100.2
>
>
> I sure don't see anything in there
> C:\Program Files\Support Tools>netdiag
> ....................................
>
> Computer Name: SERVER
> DNS Host Name: server.XYANTTech.local
> System info : Microsoft Windows Server 2003 (Build 3790)
> Processor : x86 Family 15 Model 4 Stepping 3, GenuineIntel
> List of installed hotfixes :
> KB925902
> KB927891
> KB930178
> KB931784
> KB931836
> KB932168
> KB935966
> Q147222
>
>
> Netcard queries test . . . . . . . : Passed
>
>
>
> Per interface results:
>
> Adapter : Local
>
> Netcard queries test . . . : Passed
>
> Host Name. . . . . . . . . : server
> IP Address . . . . . . . . : 192.168.100.2
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . : 192.168.100.1
> Dns Servers. . . . . . . . : 192.168.100.2
>
>
> AutoConfiguration results. . . . . . : Passed
>
> Default gateway test . . . : Passed
>
> NetBT name test. . . . . . : Passed
> [WARNING] At least one of the <00> 'WorkStation Service', <03>
> 'Messenge
> r Service', <20> 'WINS' names is missing.
> No remote names have been found.
>
> WINS service test. . . . . : Skipped
> There are no WINS servers configured for this interface.
>
>
> Global results:
>
>
> Domain membership test . . . . . . : Passed
>
>
> NetBT transports test. . . . . . . : Passed
> List of NetBt transports currently configured:
> NetBT_Tcpip_{B2E0E4FC-7C2E-49D9-8BA4-A08A4293D060}
> 1 NetBt transport currently configured.
>
>
> Autonet address test . . . . . . . : Passed
>
>
> IP loopback ping test. . . . . . . : Passed
>
>
> Default gateway test . . . . . . . : Passed
>
>
> NetBT name test. . . . . . . . . . : Passed
> [WARNING] You don't have a single interface with the <00> 'WorkStation
> Servi
> ce', <03> 'Messenger Service', <20> 'WINS' names defined.
>
>
> Winsock test . . . . . . . . . . . : Passed
>
>
> DNS test . . . . . . . . . . . . . : Passed
> PASS - All the DNS entries for DC are registered on DNS server
> '192.168.100.
> 2'.
>
>
> Redir and Browser test . . . . . . : Passed
> List of NetBt transports currently bound to the Redir
> NetBT_Tcpip_{B2E0E4FC-7C2E-49D9-8BA4-A08A4293D060}
> The redir is bound to 1 NetBt transport.
>
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{B2E0E4FC-7C2E-49D9-8BA4-A08A4293D060}
> The browser is bound to 1 NetBt transport.
>
>
> DC discovery test. . . . . . . . . : Passed
>
>
> DC list test . . . . . . . . . . . : Passed
>
>
> Trust relationship test. . . . . . : Skipped
>
>
> Kerberos test. . . . . . . . . . . : Passed
>
>
> LDAP test. . . . . . . . . . . . . : Passed
>
>
> Bindings test. . . . . . . . . . . : Passed
>
>
> WAN configuration test . . . . . . : Skipped
> No active remote access connections.
>
>
> Modem diagnostics test . . . . . . : Passed
>
> IP Security test . . . . . . . . . : Skipped
>
> Note: run "netsh ipsec dynamic show /?" for more detailed information
>
>
> The command completed successfully
> any hope for me?
>
> thanks
> Freddie
>
>
>



 
Reply With Quote
 
Freddie
Guest
Posts: n/a

 
      07-24-2007, 03:12 PM

Thanks
But As I mentioned if I use the local DNS (which is pointed to ISP's
DNS(forwarded))
I can not get I the web
But if I use the DHCP which is not the domain Controller DHCP (OLD SERVER
that is running DHCP) I get on the web,
so I don't think it is Static vs DHCP, But the local Domain controler being
block from acessing the web and DNS does not work.

Thnaks
again
Freddie
"Bill Grant" wrote:

> If you are running a domain, all domain members, including the domain
> controller itself, should use the local DNS so that AD works properly.
>
> To enable the local DNS to resolve "foreign" URLs, you can set your DNS
> to forward to a public DNS service. The local client queries the local DNS,
> the local DNS forwards the request to the public DNS server and returns the
> reply it receives to the client.
>
> "Freddie" <(E-Mail Removed)> wrote in message
> news:8D6C250C-D2D8-4579-A943-(E-Mail Removed)...
> > if I use DHCP on domain controler, I can get on to the web, but if I use
> > the
> > local DNS or ISP dns I cant get on to the web it indicates page can not be
> > display,
> > using Local DNS address or ISP addtress, I can ping to gateway but it does
> > not let me get out to any other sites. it does not matter if I use IP or
> > name
> > of any sites,
> > the Netdiag shows everything ok or I think it looks ok.
> > only changes I saw between static IP and DHCP is the winserver.
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.100.2
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.100.1
> > DNS Servers . . . . . . . . . . . : 192.168.100.2
> >
> >
> > I sure don't see anything in there
> > C:\Program Files\Support Tools>netdiag
> > ....................................
> >
> > Computer Name: SERVER
> > DNS Host Name: server.XYANTTech.local
> > System info : Microsoft Windows Server 2003 (Build 3790)
> > Processor : x86 Family 15 Model 4 Stepping 3, GenuineIntel
> > List of installed hotfixes :
> > KB925902
> > KB927891
> > KB930178
> > KB931784
> > KB931836
> > KB932168
> > KB935966
> > Q147222
> >
> >
> > Netcard queries test . . . . . . . : Passed
> >
> >
> >
> > Per interface results:
> >
> > Adapter : Local
> >
> > Netcard queries test . . . : Passed
> >
> > Host Name. . . . . . . . . : server
> > IP Address . . . . . . . . : 192.168.100.2
> > Subnet Mask. . . . . . . . : 255.255.255.0
> > Default Gateway. . . . . . : 192.168.100.1
> > Dns Servers. . . . . . . . : 192.168.100.2
> >
> >
> > AutoConfiguration results. . . . . . : Passed
> >
> > Default gateway test . . . : Passed
> >
> > NetBT name test. . . . . . : Passed
> > [WARNING] At least one of the <00> 'WorkStation Service', <03>
> > 'Messenge
> > r Service', <20> 'WINS' names is missing.
> > No remote names have been found.
> >
> > WINS service test. . . . . : Skipped
> > There are no WINS servers configured for this interface.
> >
> >
> > Global results:
> >
> >
> > Domain membership test . . . . . . : Passed
> >
> >
> > NetBT transports test. . . . . . . : Passed
> > List of NetBt transports currently configured:
> > NetBT_Tcpip_{B2E0E4FC-7C2E-49D9-8BA4-A08A4293D060}
> > 1 NetBt transport currently configured.
> >
> >
> > Autonet address test . . . . . . . : Passed
> >
> >
> > IP loopback ping test. . . . . . . : Passed
> >
> >
> > Default gateway test . . . . . . . : Passed
> >
> >
> > NetBT name test. . . . . . . . . . : Passed
> > [WARNING] You don't have a single interface with the <00> 'WorkStation
> > Servi
> > ce', <03> 'Messenger Service', <20> 'WINS' names defined.
> >
> >
> > Winsock test . . . . . . . . . . . : Passed
> >
> >
> > DNS test . . . . . . . . . . . . . : Passed
> > PASS - All the DNS entries for DC are registered on DNS server
> > '192.168.100.
> > 2'.
> >
> >
> > Redir and Browser test . . . . . . : Passed
> > List of NetBt transports currently bound to the Redir
> > NetBT_Tcpip_{B2E0E4FC-7C2E-49D9-8BA4-A08A4293D060}
> > The redir is bound to 1 NetBt transport.
> >
> > List of NetBt transports currently bound to the browser
> > NetBT_Tcpip_{B2E0E4FC-7C2E-49D9-8BA4-A08A4293D060}
> > The browser is bound to 1 NetBt transport.
> >
> >
> > DC discovery test. . . . . . . . . : Passed
> >
> >
> > DC list test . . . . . . . . . . . : Passed
> >
> >
> > Trust relationship test. . . . . . : Skipped
> >
> >
> > Kerberos test. . . . . . . . . . . : Passed
> >
> >
> > LDAP test. . . . . . . . . . . . . : Passed
> >
> >
> > Bindings test. . . . . . . . . . . : Passed
> >
> >
> > WAN configuration test . . . . . . : Skipped
> > No active remote access connections.
> >
> >
> > Modem diagnostics test . . . . . . : Passed
> >
> > IP Security test . . . . . . . . . : Skipped
> >
> > Note: run "netsh ipsec dynamic show /?" for more detailed information
> >
> >
> > The command completed successfully
> > any hope for me?
> >
> > thanks
> > Freddie
> >
> >
> >

>
>
>

 
Reply With Quote
 
Bill Grant
Guest
Posts: n/a

 
      07-25-2007, 02:42 AM
Then you really need to find out where the dns lookup is failing. If you
use a tool like nslookup, can you resolve public addresses from the DC
itself?

You say that you can get to the web using the config you get from DHCP.
What is the difference between that config and your static setup? In
particular, check the default gateway setting.

"Freddie" <(E-Mail Removed)> wrote in message
news:40A1AB3A-6AE1-45CE-A5FE-(E-Mail Removed)...
>
> Thanks
> But As I mentioned if I use the local DNS (which is pointed to ISP's
> DNS(forwarded))
> I can not get I the web
> But if I use the DHCP which is not the domain Controller DHCP (OLD SERVER
> that is running DHCP) I get on the web,
> so I don't think it is Static vs DHCP, But the local Domain controler
> being
> block from acessing the web and DNS does not work.
>
> Thnaks
> again
> Freddie
> "Bill Grant" wrote:
>
>> If you are running a domain, all domain members, including the domain
>> controller itself, should use the local DNS so that AD works properly.
>>
>> To enable the local DNS to resolve "foreign" URLs, you can set your
>> DNS
>> to forward to a public DNS service. The local client queries the local
>> DNS,
>> the local DNS forwards the request to the public DNS server and returns
>> the
>> reply it receives to the client.
>>
>> "Freddie" <(E-Mail Removed)> wrote in message
>> news:8D6C250C-D2D8-4579-A943-(E-Mail Removed)...
>> > if I use DHCP on domain controler, I can get on to the web, but if I
>> > use
>> > the
>> > local DNS or ISP dns I cant get on to the web it indicates page can not
>> > be
>> > display,
>> > using Local DNS address or ISP addtress, I can ping to gateway but it
>> > does
>> > not let me get out to any other sites. it does not matter if I use IP
>> > or
>> > name
>> > of any sites,
>> > the Netdiag shows everything ok or I think it looks ok.
>> > only changes I saw between static IP and DHCP is the winserver.
>> > DHCP Enabled. . . . . . . . . . . : No
>> > IP Address. . . . . . . . . . . . : 192.168.100.2
>> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> > Default Gateway . . . . . . . . . : 192.168.100.1
>> > DNS Servers . . . . . . . . . . . : 192.168.100.2
>> >
>> >
>> > I sure don't see anything in there
>> > C:\Program Files\Support Tools>netdiag
>> > ....................................
>> >
>> > Computer Name: SERVER
>> > DNS Host Name: server.XYANTTech.local
>> > System info : Microsoft Windows Server 2003 (Build 3790)
>> > Processor : x86 Family 15 Model 4 Stepping 3, GenuineIntel
>> > List of installed hotfixes :
>> > KB925902
>> > KB927891
>> > KB930178
>> > KB931784
>> > KB931836
>> > KB932168
>> > KB935966
>> > Q147222
>> >
>> >
>> > Netcard queries test . . . . . . . : Passed
>> >
>> >
>> >
>> > Per interface results:
>> >
>> > Adapter : Local
>> >
>> > Netcard queries test . . . : Passed
>> >
>> > Host Name. . . . . . . . . : server
>> > IP Address . . . . . . . . : 192.168.100.2
>> > Subnet Mask. . . . . . . . : 255.255.255.0
>> > Default Gateway. . . . . . : 192.168.100.1
>> > Dns Servers. . . . . . . . : 192.168.100.2
>> >
>> >
>> > AutoConfiguration results. . . . . . : Passed
>> >
>> > Default gateway test . . . : Passed
>> >
>> > NetBT name test. . . . . . : Passed
>> > [WARNING] At least one of the <00> 'WorkStation Service', <03>
>> > 'Messenge
>> > r Service', <20> 'WINS' names is missing.
>> > No remote names have been found.
>> >
>> > WINS service test. . . . . : Skipped
>> > There are no WINS servers configured for this interface.
>> >
>> >
>> > Global results:
>> >
>> >
>> > Domain membership test . . . . . . : Passed
>> >
>> >
>> > NetBT transports test. . . . . . . : Passed
>> > List of NetBt transports currently configured:
>> > NetBT_Tcpip_{B2E0E4FC-7C2E-49D9-8BA4-A08A4293D060}
>> > 1 NetBt transport currently configured.
>> >
>> >
>> > Autonet address test . . . . . . . : Passed
>> >
>> >
>> > IP loopback ping test. . . . . . . : Passed
>> >
>> >
>> > Default gateway test . . . . . . . : Passed
>> >
>> >
>> > NetBT name test. . . . . . . . . . : Passed
>> > [WARNING] You don't have a single interface with the <00>
>> > 'WorkStation
>> > Servi
>> > ce', <03> 'Messenger Service', <20> 'WINS' names defined.
>> >
>> >
>> > Winsock test . . . . . . . . . . . : Passed
>> >
>> >
>> > DNS test . . . . . . . . . . . . . : Passed
>> > PASS - All the DNS entries for DC are registered on DNS server
>> > '192.168.100.
>> > 2'.
>> >
>> >
>> > Redir and Browser test . . . . . . : Passed
>> > List of NetBt transports currently bound to the Redir
>> > NetBT_Tcpip_{B2E0E4FC-7C2E-49D9-8BA4-A08A4293D060}
>> > The redir is bound to 1 NetBt transport.
>> >
>> > List of NetBt transports currently bound to the browser
>> > NetBT_Tcpip_{B2E0E4FC-7C2E-49D9-8BA4-A08A4293D060}
>> > The browser is bound to 1 NetBt transport.
>> >
>> >
>> > DC discovery test. . . . . . . . . : Passed
>> >
>> >
>> > DC list test . . . . . . . . . . . : Passed
>> >
>> >
>> > Trust relationship test. . . . . . : Skipped
>> >
>> >
>> > Kerberos test. . . . . . . . . . . : Passed
>> >
>> >
>> > LDAP test. . . . . . . . . . . . . : Passed
>> >
>> >
>> > Bindings test. . . . . . . . . . . : Passed
>> >
>> >
>> > WAN configuration test . . . . . . : Skipped
>> > No active remote access connections.
>> >
>> >
>> > Modem diagnostics test . . . . . . : Passed
>> >
>> > IP Security test . . . . . . . . . : Skipped
>> >
>> > Note: run "netsh ipsec dynamic show /?" for more detailed
>> > information
>> >
>> >
>> > The command completed successfully
>> > any hope for me?
>> >
>> > thanks
>> > Freddie
>> >
>> >
>> >

>>
>>
>>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. Ace Fekay [MVP-DS, MCT] Windows Networking 1 01-10-2010 11:08 PM
Clients can't join domain-new Primary Domain Controller installed blinton25 Windows Networking 7 06-23-2008 09:58 PM
Domain Controller Omar Abid Windows Networking 4 07-15-2007 02:08 PM
Server 2003 Standard - Cannot browse domain with domain controller! davidw@dwynn.demon.co.uk Windows Networking 2 04-12-2006 04:28 PM
Moving a domain 2003 domain controller to a different subnet John zhang Windows Networking 1 07-27-2004 01:41 PM



1 2 3 4 5 6 7 8 9 10 11