Weird issues win2k3

I am having some very weird problems with my Windows 2003
server. I seem to have lost local internet connectivity. I
cannot even ping external addresses. The weird part is that
I am going through a router, and all other nodes on the
network are able to get out.
It gets even weirder because I can go to a remote location
and get into the server with remote desktop. (Still can't
get out on the internet).
Exchange wont start due to the lack of a connection.
I have access to my LAN.
I cannot access AD users/computers, it says no domain
controller exists.
This box is set up for DNS, Primary DC,IIS6.0, FTP,
Exchange (with pop3 and SMTP)
Everything seems to work from the outside... except for
exchange.
Event viewer has a bunch of stuff about the exchange
services and things not starting, but nothing I wouldn't
expect with this kind of problem.
Does anyone have any ideas?
Never seen this behavior before.

If this is a D.C. running DNS:

1. It should point to itself for DNS

2. Forwarders should be configured to use the ISP's DNS servers for
external name resolution.

3. The router's internal IP address should be the D.C.'s default gateway.

Failure of any combination of the above could account for your problem.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Rich Burgess" <(E-Mail Removed)> wrote in message
news:225fb01c45d1d$32fddff0$(E-Mail Removed)...
> I am having some very weird problems with my Windows 2003
> server. I seem to have lost local internet connectivity. I
> cannot even ping external addresses. The weird part is that
> I am going through a router, and all other nodes on the
> network are able to get out.
> It gets even weirder because I can go to a remote location
> and get into the server with remote desktop. (Still can't
> get out on the internet).
> Exchange wont start due to the lack of a connection.
> I have access to my LAN.
> I cannot access AD users/computers, it says no domain
> controller exists.
> This box is set up for DNS, Primary DC,IIS6.0, FTP,
> Exchange (with pop3 and SMTP)
> Everything seems to work from the outside... except for
> exchange.
> Event viewer has a bunch of stuff about the exchange
> services and things not starting, but nothing I wouldn't
> expect with this kind of problem.
> Does anyone have any ideas?
> Never seen this behavior before.

1. I had the dns entries in tcp/ip properties blank (it
asks if you intended for the local to be the primary dns)
But I also tried entering the local IP manually for the
primary DNS.
2. in the DNS forwarders I selected all other dns domains
and entered the DNS address for my ISP.
3. In tcp/ip properties, under default gateway, the address
is static and the default gateway is the routers internal
address.

Static ip: 192.168.1.2
Subnet: 255.255.255.0
Default gateway: 192.168.1.1

All of this was configured before, except for the forwarder
entry in the DNS, and everything was running fine...
but even with the forwarder, nothing changes.


What else could I be missing?


>-----Original Message-----
>If this is a D.C. running DNS:
>
>1. It should point to itself for DNS
>
>2. Forwarders should be configured to use the ISP's DNS
servers for
>external name resolution.
>
>3. The router's internal IP address should be the D.C.'s
default gateway.
>
>Failure of any combination of the above could account for
your problem.
>
>Doug Sherman
>MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>
>"Rich Burgess" <(E-Mail Removed)> wrote in
message
>news:225fb01c45d1d$32fddff0$(E-Mail Removed)...
>> I am having some very weird problems with my Windows 2003
>> server. I seem to have lost local internet connectivity. I
>> cannot even ping external addresses. The weird part is that
>> I am going through a router, and all other nodes on the
>> network are able to get out.
>> It gets even weirder because I can go to a remote location
>> and get into the server with remote desktop. (Still can't
>> get out on the internet).
>> Exchange wont start due to the lack of a connection.
>> I have access to my LAN.
>> I cannot access AD users/computers, it says no domain
>> controller exists.
>> This box is set up for DNS, Primary DC,IIS6.0, FTP,
>> Exchange (with pop3 and SMTP)
>> Everything seems to work from the outside... except for
>> exchange.
>> Event viewer has a bunch of stuff about the exchange
>> services and things not starting, but nothing I wouldn't
>> expect with this kind of problem.
>> Does anyone have any ideas?
>> Never seen this behavior before.
>
>
>.
>

OK, with primary DNS manually configured to point to 192.168.1.2, use
Aministrative Tools/Services and restart the Netlogon service. Then see if
you can connect to AD Users and Computers.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Rich Burgess" <(E-Mail Removed)> wrote in message
news:226de01c45d23$4150cf30$(E-Mail Removed)...
> 1. I had the dns entries in tcp/ip properties blank (it
> asks if you intended for the local to be the primary dns)
> But I also tried entering the local IP manually for the
> primary DNS.
> 2. in the DNS forwarders I selected all other dns domains
> and entered the DNS address for my ISP.
> 3. In tcp/ip properties, under default gateway, the address
> is static and the default gateway is the routers internal
> address.
>
> Static ip: 192.168.1.2
> Subnet: 255.255.255.0
> Default gateway: 192.168.1.1
>
> All of this was configured before, except for the forwarder
> entry in the DNS, and everything was running fine...
> but even with the forwarder, nothing changes.
>
>
> What else could I be missing?
>
>
> >-----Original Message-----
> >If this is a D.C. running DNS:
> >
> >1. It should point to itself for DNS
> >
> >2. Forwarders should be configured to use the ISP's DNS
> servers for
> >external name resolution.
> >
> >3. The router's internal IP address should be the D.C.'s
> default gateway.
> >
> >Failure of any combination of the above could account for
> your problem.
> >
> >Doug Sherman
> >MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >
> >"Rich Burgess" <(E-Mail Removed)> wrote in
> message
> >news:225fb01c45d1d$32fddff0$(E-Mail Removed)...
> >> I am having some very weird problems with my Windows 2003
> >> server. I seem to have lost local internet connectivity. I
> >> cannot even ping external addresses. The weird part is that
> >> I am going through a router, and all other nodes on the
> >> network are able to get out.
> >> It gets even weirder because I can go to a remote location
> >> and get into the server with remote desktop. (Still can't
> >> get out on the internet).
> >> Exchange wont start due to the lack of a connection.
> >> I have access to my LAN.
> >> I cannot access AD users/computers, it says no domain
> >> controller exists.
> >> This box is set up for DNS, Primary DC,IIS6.0, FTP,
> >> Exchange (with pop3 and SMTP)
> >> Everything seems to work from the outside... except for
> >> exchange.
> >> Event viewer has a bunch of stuff about the exchange
> >> services and things not starting, but nothing I wouldn't
> >> expect with this kind of problem.
> >> Does anyone have any ideas?
> >> Never seen this behavior before.
> >
> >
> >.
> >

This still doesn't seem to help anything.
I am getting the same message:

Naming information cannot be located for the following
reason:
The server is not operational.

What is the next step?


>-----Original Message-----
>OK, with primary DNS manually configured to point to
192.168.1.2, use
>Aministrative Tools/Services and restart the Netlogon
service. Then see if
>you can connect to AD Users and Computers.
>
>Doug Sherman
>MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>
>"Rich Burgess" <(E-Mail Removed)> wrote
in message
>news:226de01c45d23$4150cf30$(E-Mail Removed)...
>> 1. I had the dns entries in tcp/ip properties blank (it
>> asks if you intended for the local to be the primary
dns)
>> But I also tried entering the local IP manually for the
>> primary DNS.
>> 2. in the DNS forwarders I selected all other dns
domains
>> and entered the DNS address for my ISP.
>> 3. In tcp/ip properties, under default gateway, the
address
>> is static and the default gateway is the routers
internal
>> address.
>>
>> Static ip: 192.168.1.2
>> Subnet: 255.255.255.0
>> Default gateway: 192.168.1.1
>>
>> All of this was configured before, except for the
forwarder
>> entry in the DNS, and everything was running fine...
>> but even with the forwarder, nothing changes.
>>
>>
>> What else could I be missing?
>>
>>
>> >-----Original Message-----
>> >If this is a D.C. running DNS:
>> >
>> >1. It should point to itself for DNS
>> >
>> >2. Forwarders should be configured to use the ISP's
DNS
>> servers for
>> >external name resolution.
>> >
>> >3. The router's internal IP address should be the
D.C.'s
>> default gateway.
>> >
>> >Failure of any combination of the above could account
for
>> your problem.
>> >
>> >Doug Sherman
>> >MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>> >
>> >"Rich Burgess" <(E-Mail Removed)>
wrote in
>> message
>> >news:225fb01c45d1d$32fddff0$(E-Mail Removed)...
>> >> I am having some very weird problems with my
Windows 2003
>> >> server. I seem to have lost local internet
connectivity. I
>> >> cannot even ping external addresses. The weird part
is that
>> >> I am going through a router, and all other nodes on
the
>> >> network are able to get out.
>> >> It gets even weirder because I can go to a remote
location
>> >> and get into the server with remote desktop. (Still
can't
>> >> get out on the internet).
>> >> Exchange wont start due to the lack of a connection.
>> >> I have access to my LAN.
>> >> I cannot access AD users/computers, it says no
domain
>> >> controller exists.
>> >> This box is set up for DNS, Primary DC,IIS6.0, FTP,
>> >> Exchange (with pop3 and SMTP)
>> >> Everything seems to work from the outside... except
for
>> >> exchange.
>> >> Event viewer has a bunch of stuff about the exchange
>> >> services and things not starting, but nothing I
wouldn't
>> >> expect with this kind of problem.
>> >> Does anyone have any ideas?
>> >> Never seen this behavior before.
>> >
>> >
>> >.
>> >
>
>
>.
>

Was this recenlty upgraded? Your Exchange not starting has nothing to do
with not being able to get to the internet. It has to do with the fact that
it cannot find your internal domain and find a Global Catalog Server. This
is most likely a DNS issue as stated in previous posts. When you go into DNS
manager do you see your zone for your internal domain? What is the name of
your intenal domain? How long has it been running like this? Under your zone
in DNS do you see all the other DNS folders like _msdcs, _sites, _tcp, _udp?
If not this is most likely the reason for AD to fail. Basically the box has
no idea where AD is even though it is the DC. Try running ipconfig
/registerdns and see what kind of errors you get.

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

"Rich Burgess" <(E-Mail Removed)> wrote in message
news:2284501c45d38$c88508d0$(E-Mail Removed)...
> This still doesn't seem to help anything.
> I am getting the same message:
>
> Naming information cannot be located for the following
> reason:
> The server is not operational.
>
> What is the next step?
>
>
> >-----Original Message-----
> >OK, with primary DNS manually configured to point to
> 192.168.1.2, use
> >Aministrative Tools/Services and restart the Netlogon
> service. Then see if
> >you can connect to AD Users and Computers.
> >
> >Doug Sherman
> >MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >
> >"Rich Burgess" <(E-Mail Removed)> wrote
> in message
> >news:226de01c45d23$4150cf30$(E-Mail Removed)...
> >> 1. I had the dns entries in tcp/ip properties blank (it
> >> asks if you intended for the local to be the primary
> dns)
> >> But I also tried entering the local IP manually for the
> >> primary DNS.
> >> 2. in the DNS forwarders I selected all other dns
> domains
> >> and entered the DNS address for my ISP.
> >> 3. In tcp/ip properties, under default gateway, the
> address
> >> is static and the default gateway is the routers
> internal
> >> address.
> >>
> >> Static ip: 192.168.1.2
> >> Subnet: 255.255.255.0
> >> Default gateway: 192.168.1.1
> >>
> >> All of this was configured before, except for the
> forwarder
> >> entry in the DNS, and everything was running fine...
> >> but even with the forwarder, nothing changes.
> >>
> >>
> >> What else could I be missing?
> >>
> >>
> >> >-----Original Message-----
> >> >If this is a D.C. running DNS:
> >> >
> >> >1. It should point to itself for DNS
> >> >
> >> >2. Forwarders should be configured to use the ISP's
> DNS
> >> servers for
> >> >external name resolution.
> >> >
> >> >3. The router's internal IP address should be the
> D.C.'s
> >> default gateway.
> >> >
> >> >Failure of any combination of the above could account
> for
> >> your problem.
> >> >
> >> >Doug Sherman
> >> >MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >> >
> >> >"Rich Burgess" <(E-Mail Removed)>
> wrote in
> >> message
> >> >news:225fb01c45d1d$32fddff0$(E-Mail Removed)...
> >> >> I am having some very weird problems with my
> Windows 2003
> >> >> server. I seem to have lost local internet
> connectivity. I
> >> >> cannot even ping external addresses. The weird part
> is that
> >> >> I am going through a router, and all other nodes on
> the
> >> >> network are able to get out.
> >> >> It gets even weirder because I can go to a remote
> location
> >> >> and get into the server with remote desktop. (Still
> can't
> >> >> get out on the internet).
> >> >> Exchange wont start due to the lack of a connection.
> >> >> I have access to my LAN.
> >> >> I cannot access AD users/computers, it says no
> domain
> >> >> controller exists.
> >> >> This box is set up for DNS, Primary DC,IIS6.0, FTP,
> >> >> Exchange (with pop3 and SMTP)
> >> >> Everything seems to work from the outside... except
> for
> >> >> exchange.
> >> >> Event viewer has a bunch of stuff about the exchange
> >> >> services and things not starting, but nothing I
> wouldn't
> >> >> expect with this kind of problem.
> >> >> Does anyone have any ideas?
> >> >> Never seen this behavior before.
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

Hmmm. If DNS is properly configured, forwarders are enabled, and your
default gateway is correct, then failure to access the Internet has to be
TCP/IP filtering, firewall settings or some other function which is blocking
traffic.

However, I am much more concerned that Active Directory does not seem to be
functioning correctly. I had thought that perhaps your SRV resource records
were not properly registered in DNS. Make sure Dynamic Updates is enabled.
See:

http://support.microsoft.com/default...b;en-us;241505

dcdiag and netdiag may be able to help isolate this problem.

Possibly, the issue is with Exchange Server. See:

http://www.microsoft.com/technet/sup...Ver=6.5.0000.0

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Rich Burgess" <(E-Mail Removed)> wrote in message
news:2284501c45d38$c88508d0$(E-Mail Removed)...
> This still doesn't seem to help anything.
> I am getting the same message:
>
> Naming information cannot be located for the following
> reason:
> The server is not operational.
>
> What is the next step?
>
>
> >-----Original Message-----
> >OK, with primary DNS manually configured to point to
> 192.168.1.2, use
> >Aministrative Tools/Services and restart the Netlogon
> service. Then see if
> >you can connect to AD Users and Computers.
> >
> >Doug Sherman
> >MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >
> >"Rich Burgess" <(E-Mail Removed)> wrote
> in message
> >news:226de01c45d23$4150cf30$(E-Mail Removed)...
> >> 1. I had the dns entries in tcp/ip properties blank (it
> >> asks if you intended for the local to be the primary
> dns)
> >> But I also tried entering the local IP manually for the
> >> primary DNS.
> >> 2. in the DNS forwarders I selected all other dns
> domains
> >> and entered the DNS address for my ISP.
> >> 3. In tcp/ip properties, under default gateway, the
> address
> >> is static and the default gateway is the routers
> internal
> >> address.
> >>
> >> Static ip: 192.168.1.2
> >> Subnet: 255.255.255.0
> >> Default gateway: 192.168.1.1
> >>
> >> All of this was configured before, except for the
> forwarder
> >> entry in the DNS, and everything was running fine...
> >> but even with the forwarder, nothing changes.
> >>
> >>
> >> What else could I be missing?
> >>
> >>
> >> >-----Original Message-----
> >> >If this is a D.C. running DNS:
> >> >
> >> >1. It should point to itself for DNS
> >> >
> >> >2. Forwarders should be configured to use the ISP's
> DNS
> >> servers for
> >> >external name resolution.
> >> >
> >> >3. The router's internal IP address should be the
> D.C.'s
> >> default gateway.
> >> >
> >> >Failure of any combination of the above could account
> for
> >> your problem.
> >> >
> >> >Doug Sherman
> >> >MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >> >
> >> >"Rich Burgess" <(E-Mail Removed)>
> wrote in
> >> message
> >> >news:225fb01c45d1d$32fddff0$(E-Mail Removed)...
> >> >> I am having some very weird problems with my
> Windows 2003
> >> >> server. I seem to have lost local internet
> connectivity. I
> >> >> cannot even ping external addresses. The weird part
> is that
> >> >> I am going through a router, and all other nodes on
> the
> >> >> network are able to get out.
> >> >> It gets even weirder because I can go to a remote
> location
> >> >> and get into the server with remote desktop. (Still
> can't
> >> >> get out on the internet).
> >> >> Exchange wont start due to the lack of a connection.
> >> >> I have access to my LAN.
> >> >> I cannot access AD users/computers, it says no
> domain
> >> >> controller exists.
> >> >> This box is set up for DNS, Primary DC,IIS6.0, FTP,
> >> >> Exchange (with pop3 and SMTP)
> >> >> Everything seems to work from the outside... except
> for
> >> >> exchange.
> >> >> Event viewer has a bunch of stuff about the exchange
> >> >> services and things not starting, but nothing I
> wouldn't
> >> >> expect with this kind of problem.
> >> >> Does anyone have any ideas?
> >> >> Never seen this behavior before.
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

Actaully I have been working on this problem a lot last
night, and came to basically the same area. I found that
DNS is having problems.
It does not have the extra records ( _msdcs, _sites,
_tcp, _udp)
Which would make sense as to why everything is failing.
DNS will not restart and has tons of errors about AD not
being started or found.
I have tried wiping my zones and creating new ones, even
reinstalling DNS, but every time I reinstall I get an
installation error that one of DNS's components didnt
start in a timely fashion.
I am kind of at a loss here, and I am trying to avoid
reinstalling the OS.
Any ideas what could be wrong here? How do I get the AD
related records back?
I tried the registerdns switch with ipconfig, and I am
still waiting to get back errors.... But I assume i will
get the same errors I have already gotten about the AD
not being present.





>-----Original Message-----
>Was this recenlty upgraded? Your Exchange not starting
has nothing to do
>with not being able to get to the internet. It has to do
with the fact that
>it cannot find your internal domain and find a Global
Catalog Server. This
>is most likely a DNS issue as stated in previous posts.
When you go into DNS
>manager do you see your zone for your internal domain?
What is the name of
>your intenal domain? How long has it been running like
this? Under your zone
>in DNS do you see all the other DNS folders like _msdcs,
_sites, _tcp, _udp?
>If not this is most likely the reason for AD to fail.
Basically the box has
>no idea where AD is even though it is the DC. Try
running ipconfig
>/registerdns and see what kind of errors you get.
>
>--
>Scott Harding
>MCSE, MCSA, A+, Network+
>Microsoft MVP - Windows NT Server
>
>"Rich Burgess" <(E-Mail Removed)> wrote
in message
>news:2284501c45d38$c88508d0$(E-Mail Removed)...
>> This still doesn't seem to help anything.
>> I am getting the same message:
>>
>> Naming information cannot be located for the following
>> reason:
>> The server is not operational.
>>
>> What is the next step?
>>
>>
>> >-----Original Message-----
>> >OK, with primary DNS manually configured to point to
>> 192.168.1.2, use
>> >Aministrative Tools/Services and restart the Netlogon
>> service. Then see if
>> >you can connect to AD Users and Computers.
>> >
>> >Doug Sherman
>> >MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>> >
>> >"Rich Burgess" <(E-Mail Removed)> wrote
>> in message
>> >news:226de01c45d23$4150cf30$(E-Mail Removed)...
>> >> 1. I had the dns entries in tcp/ip properties blank
(it
>> >> asks if you intended for the local to be the primary
>> dns)
>> >> But I also tried entering the local IP manually for
the
>> >> primary DNS.
>> >> 2. in the DNS forwarders I selected all other dns
>> domains
>> >> and entered the DNS address for my ISP.
>> >> 3. In tcp/ip properties, under default gateway, the
>> address
>> >> is static and the default gateway is the routers
>> internal
>> >> address.
>> >>
>> >> Static ip: 192.168.1.2
>> >> Subnet: 255.255.255.0
>> >> Default gateway: 192.168.1.1
>> >>
>> >> All of this was configured before, except for the
>> forwarder
>> >> entry in the DNS, and everything was running
fine...
>> >> but even with the forwarder, nothing changes.
>> >>
>> >>
>> >> What else could I be missing?
>> >>
>> >>
>> >> >-----Original Message-----
>> >> >If this is a D.C. running DNS:
>> >> >
>> >> >1. It should point to itself for DNS
>> >> >
>> >> >2. Forwarders should be configured to use the
ISP's
>> DNS
>> >> servers for
>> >> >external name resolution.
>> >> >
>> >> >3. The router's internal IP address should be the
>> D.C.'s
>> >> default gateway.
>> >> >
>> >> >Failure of any combination of the above could
account
>> for
>> >> your problem.
>> >> >
>> >> >Doug Sherman
>> >> >MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>> >> >
>> >> >"Rich Burgess" <(E-Mail Removed)>
>> wrote in
>> >> message
>> >> >news:225fb01c45d1d$32fddff0$(E-Mail Removed)...
>> >> >> I am having some very weird problems with my
>> Windows 2003
>> >> >> server. I seem to have lost local internet
>> connectivity. I
>> >> >> cannot even ping external addresses. The weird
part
>> is that
>> >> >> I am going through a router, and all other nodes
on
>> the
>> >> >> network are able to get out.
>> >> >> It gets even weirder because I can go to a remote
>> location
>> >> >> and get into the server with remote desktop.
(Still
>> can't
>> >> >> get out on the internet).
>> >> >> Exchange wont start due to the lack of a
connection.
>> >> >> I have access to my LAN.
>> >> >> I cannot access AD users/computers, it says no
>> domain
>> >> >> controller exists.
>> >> >> This box is set up for DNS, Primary DC,IIS6.0,
FTP,
>> >> >> Exchange (with pop3 and SMTP)
>> >> >> Everything seems to work from the outside...
except
>> for
>> >> >> exchange.
>> >> >> Event viewer has a bunch of stuff about the
exchange
>> >> >> services and things not starting, but nothing I
>> wouldn't
>> >> >> expect with this kind of problem.
>> >> >> Does anyone have any ideas?
>> >> >> Never seen this behavior before.
>> >> >
>> >> >
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>
>
>.
>

I tried running dcdiag (fix and test)
and it returned LDAP connection failed with error 58.
any ideas?



>-----Original Message-----
>Hmmm. If DNS is properly configured, forwarders are
enabled, and your
>default gateway is correct, then failure to access the
Internet has to be
>TCP/IP filtering, firewall settings or some other
function which is blocking
>traffic.
>
>However, I am much more concerned that Active Directory
does not seem to be
>functioning correctly. I had thought that perhaps your
SRV resource records
>were not properly registered in DNS. Make sure Dynamic
Updates is enabled.
>See:
>
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;241505
>
>dcdiag and netdiag may be able to help isolate this
problem.
>
>Possibly, the issue is with Exchange Server. See:
>
>http://www.microsoft.com/technet/sup...e/result.aspx?
ProdName=Exchange&LCID=1033&EvtID=1005&EvtSrc=MSEx changeSA
&ProdVer=6.5.0000.0
>
>Doug Sherman
>MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>
> "Rich Burgess" <(E-Mail Removed)> wrote
in message
>news:2284501c45d38$c88508d0$(E-Mail Removed)...
>> This still doesn't seem to help anything.
>> I am getting the same message:
>>
>> Naming information cannot be located for the following
>> reason:
>> The server is not operational.
>>
>> What is the next step?
>>
>>
>> >-----Original Message-----
>> >OK, with primary DNS manually configured to point to
>> 192.168.1.2, use
>> >Aministrative Tools/Services and restart the Netlogon
>> service. Then see if
>> >you can connect to AD Users and Computers.
>> >
>> >Doug Sherman
>> >MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>> >
>> >"Rich Burgess" <(E-Mail Removed)> wrote
>> in message
>> >news:226de01c45d23$4150cf30$(E-Mail Removed)...
>> >> 1. I had the dns entries in tcp/ip properties blank
(it
>> >> asks if you intended for the local to be the primary
>> dns)
>> >> But I also tried entering the local IP manually for
the
>> >> primary DNS.
>> >> 2. in the DNS forwarders I selected all other dns
>> domains
>> >> and entered the DNS address for my ISP.
>> >> 3. In tcp/ip properties, under default gateway, the
>> address
>> >> is static and the default gateway is the routers
>> internal
>> >> address.
>> >>
>> >> Static ip: 192.168.1.2
>> >> Subnet: 255.255.255.0
>> >> Default gateway: 192.168.1.1
>> >>
>> >> All of this was configured before, except for the
>> forwarder
>> >> entry in the DNS, and everything was running
fine...
>> >> but even with the forwarder, nothing changes.
>> >>
>> >>
>> >> What else could I be missing?
>> >>
>> >>
>> >> >-----Original Message-----
>> >> >If this is a D.C. running DNS:
>> >> >
>> >> >1. It should point to itself for DNS
>> >> >
>> >> >2. Forwarders should be configured to use the
ISP's
>> DNS
>> >> servers for
>> >> >external name resolution.
>> >> >
>> >> >3. The router's internal IP address should be the
>> D.C.'s
>> >> default gateway.
>> >> >
>> >> >Failure of any combination of the above could
account
>> for
>> >> your problem.
>> >> >
>> >> >Doug Sherman
>> >> >MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>> >> >
>> >> >"Rich Burgess" <(E-Mail Removed)>
>> wrote in
>> >> message
>> >> >news:225fb01c45d1d$32fddff0$(E-Mail Removed)...
>> >> >> I am having some very weird problems with my
>> Windows 2003
>> >> >> server. I seem to have lost local internet
>> connectivity. I
>> >> >> cannot even ping external addresses. The weird
part
>> is that
>> >> >> I am going through a router, and all other nodes
on
>> the
>> >> >> network are able to get out.
>> >> >> It gets even weirder because I can go to a remote
>> location
>> >> >> and get into the server with remote desktop.
(Still
>> can't
>> >> >> get out on the internet).
>> >> >> Exchange wont start due to the lack of a
connection.
>> >> >> I have access to my LAN.
>> >> >> I cannot access AD users/computers, it says no
>> domain
>> >> >> controller exists.
>> >> >> This box is set up for DNS, Primary DC,IIS6.0,
FTP,
>> >> >> Exchange (with pop3 and SMTP)
>> >> >> Everything seems to work from the outside...
except
>> for
>> >> >> exchange.
>> >> >> Event viewer has a bunch of stuff about the
exchange
>> >> >> services and things not starting, but nothing I
>> wouldn't
>> >> >> expect with this kind of problem.
>> >> >> Does anyone have any ideas?
>> >> >> Never seen this behavior before.
>> >> >
>> >> >
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>
>
>.
>

Dunno - try netdiag /fix. See:

http://support.microsoft.com/default...b;en-us;260371

You can try manually creating the zones, but if you cannot get netlogon or
netdiag to auto populate them, there is something wrong with the DNS or a
related service. Make sure the DHCP Client service is started - this is
necessary for dynamic updates even with a static IP.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Rich Burgess" <(E-Mail Removed)> wrote in message
news:22e9101c45dd5$49d72430$(E-Mail Removed)...
> I tried running dcdiag (fix and test)
> and it returned LDAP connection failed with error 58.
> any ideas?
>
>
>
> >-----Original Message-----
> >Hmmm. If DNS is properly configured, forwarders are
> enabled, and your
> >default gateway is correct, then failure to access the
> Internet has to be
> >TCP/IP filtering, firewall settings or some other
> function which is blocking
> >traffic.
> >
> >However, I am much more concerned that Active Directory
> does not seem to be
> >functioning correctly. I had thought that perhaps your
> SRV resource records
> >were not properly registered in DNS. Make sure Dynamic
> Updates is enabled.
> >See:
> >
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;241505
> >
> >dcdiag and netdiag may be able to help isolate this
> problem.
> >
> >Possibly, the issue is with Exchange Server. See:
> >
> >http://www.microsoft.com/technet/sup...e/result.aspx?
> ProdName=Exchange&LCID=1033&EvtID=1005&EvtSrc=MSEx changeSA
> &ProdVer=6.5.0000.0
> >
> >Doug Sherman
> >MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >
> > "Rich Burgess" <(E-Mail Removed)> wrote
> in message
> >news:2284501c45d38$c88508d0$(E-Mail Removed)...
> >> This still doesn't seem to help anything.
> >> I am getting the same message:
> >>
> >> Naming information cannot be located for the following
> >> reason:
> >> The server is not operational.
> >>
> >> What is the next step?
> >>
> >>
> >> >-----Original Message-----
> >> >OK, with primary DNS manually configured to point to
> >> 192.168.1.2, use
> >> >Aministrative Tools/Services and restart the Netlogon
> >> service. Then see if
> >> >you can connect to AD Users and Computers.
> >> >
> >> >Doug Sherman
> >> >MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >> >
> >> >"Rich Burgess" <(E-Mail Removed)> wrote
> >> in message
> >> >news:226de01c45d23$4150cf30$(E-Mail Removed)...
> >> >> 1. I had the dns entries in tcp/ip properties blank
> (it
> >> >> asks if you intended for the local to be the primary
> >> dns)
> >> >> But I also tried entering the local IP manually for
> the
> >> >> primary DNS.
> >> >> 2. in the DNS forwarders I selected all other dns
> >> domains
> >> >> and entered the DNS address for my ISP.
> >> >> 3. In tcp/ip properties, under default gateway, the
> >> address
> >> >> is static and the default gateway is the routers
> >> internal
> >> >> address.
> >> >>
> >> >> Static ip: 192.168.1.2
> >> >> Subnet: 255.255.255.0
> >> >> Default gateway: 192.168.1.1
> >> >>
> >> >> All of this was configured before, except for the
> >> forwarder
> >> >> entry in the DNS, and everything was running
> fine...
> >> >> but even with the forwarder, nothing changes.
> >> >>
> >> >>
> >> >> What else could I be missing?
> >> >>
> >> >>
> >> >> >-----Original Message-----
> >> >> >If this is a D.C. running DNS:
> >> >> >
> >> >> >1. It should point to itself for DNS
> >> >> >
> >> >> >2. Forwarders should be configured to use the
> ISP's
> >> DNS
> >> >> servers for
> >> >> >external name resolution.
> >> >> >
> >> >> >3. The router's internal IP address should be the
> >> D.C.'s
> >> >> default gateway.
> >> >> >
> >> >> >Failure of any combination of the above could
> account
> >> for
> >> >> your problem.
> >> >> >
> >> >> >Doug Sherman
> >> >> >MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >> >> >
> >> >> >"Rich Burgess" <(E-Mail Removed)>
> >> wrote in
> >> >> message
> >> >> >news:225fb01c45d1d$32fddff0$(E-Mail Removed)...
> >> >> >> I am having some very weird problems with my
> >> Windows 2003
> >> >> >> server. I seem to have lost local internet
> >> connectivity. I
> >> >> >> cannot even ping external addresses. The weird
> part
> >> is that
> >> >> >> I am going through a router, and all other nodes
> on
> >> the
> >> >> >> network are able to get out.
> >> >> >> It gets even weirder because I can go to a remote
> >> location
> >> >> >> and get into the server with remote desktop.
> (Still
> >> can't
> >> >> >> get out on the internet).
> >> >> >> Exchange wont start due to the lack of a
> connection.
> >> >> >> I have access to my LAN.
> >> >> >> I cannot access AD users/computers, it says no
> >> domain
> >> >> >> controller exists.
> >> >> >> This box is set up for DNS, Primary DC,IIS6.0,
> FTP,
> >> >> >> Exchange (with pop3 and SMTP)
> >> >> >> Everything seems to work from the outside...
> except
> >> for
> >> >> >> exchange.
> >> >> >> Event viewer has a bunch of stuff about the
> exchange
> >> >> >> services and things not starting, but nothing I
> >> wouldn't
> >> >> >> expect with this kind of problem.
> >> >> >> Does anyone have any ideas?
> >> >> >> Never seen this behavior before.
> >> >> >
> >> >> >
> >> >> >.
> >> >> >
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >