Something not Setup Right

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

I am having serveral problems with my new Windows 2003 server. I have my
file server set as PDC and DNS Server and have Active Directory installed on
it. I also have a Windows server 2003 Exchange server, as well as a Windows
NT 4.0 Proxy Server 2.0 server.

On the PDC, I have it pointing to itself for DNS server. I have 2
forwarders setup for the DNS' my ISP gave me.

Here is the list of problems I am having. I think they are all related to
something in the DNS not setup right b/c they all have to do with name
communication:

1) Get prompt for password when browsing Network Neighborhood sometimes on
XP machines. Sometimes get not accessible error. Sometimes it works fine.

2) Cannot print to a Dymo label printer. I believe this has to do with #1
b/c the printer is hooked directly to a workstation.

3) A client/server version of a software that connects to my Proxy server
cannot log into the Server portion on the Proxy server from the client.

4) Get Event ID errors 1053 & 1054 on XP machines.

5) On Windows 2000 machine, get Event ID 1000 - Windows cannot determine the
user or computer name. Return value 1722

What I have tried:

Adding in the PDC IP as my Primary DNS on my test XP machine. However, this
then causes a problem accessing the internet b/c it's not going to the proxy
server.

All workstations have joined the domain & all user accounts are in Active
Directory

So, I think that I am missing something that will fix all of this. Any
thoughts or suggestions are much appreciated.

Thanks,
Bridget

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

> Adding in the PDC IP as my Primary DNS on my test XP machine. However,
this
> then causes a problem accessing the internet b/c it's not going to the
proxy
> server.


If this XP machine is a member of the domain it MUST point to your AD DNS
server only.

> On the PDC, I have it pointing to itself for DNS server. I have 2
> forwarders setup for the DNS' my ISP gave me.


It has been a while since I worked with Proxy 2.0. You might try forwarding
to the Proxy server and test Internet resolution.

hth
DDS W 2k MVP MCSE

"Bridget" <Bridget@discussions.microsoft.com> wrote in message
news:8170F7CF-C6AF-4B3C-AE49-9D2BDD0E8DE1@microsoft.com...
> I am having serveral problems with my new Windows 2003 server. I have my
> file server set as PDC and DNS Server and have Active Directory installed
on
> it. I also have a Windows server 2003 Exchange server, as well as a
Windows
> NT 4.0 Proxy Server 2.0 server.
>
> On the PDC, I have it pointing to itself for DNS server. I have 2
> forwarders setup for the DNS' my ISP gave me.
>
> Here is the list of problems I am having. I think they are all related to
> something in the DNS not setup right b/c they all have to do with name
> communication:
>
> 1) Get prompt for password when browsing Network Neighborhood sometimes on
> XP machines. Sometimes get not accessible error. Sometimes it works
fine.
>
> 2) Cannot print to a Dymo label printer. I believe this has to do with #1
> b/c the printer is hooked directly to a workstation.
>
> 3) A client/server version of a software that connects to my Proxy server
> cannot log into the Server portion on the Proxy server from the client.
>
> 4) Get Event ID errors 1053 & 1054 on XP machines.
>
> 5) On Windows 2000 machine, get Event ID 1000 - Windows cannot determine
the
> user or computer name. Return value 1722
>
> What I have tried:
>
> Adding in the PDC IP as my Primary DNS on my test XP machine. However,
this
> then causes a problem accessing the internet b/c it's not going to the
proxy
> server.
>
> All workstations have joined the domain & all user accounts are in Active
> Directory
>
> So, I think that I am missing something that will fix all of this. Any
> thoughts or suggestions are much appreciated.
>
> Thanks,
> Bridget

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

Thanks. I have my PDC IP as my Primary DNS. Now, I'm just having that
internet problem. It is so slow that I think it is trying to use the PDC IP
as DNS & when it can't, it pulls my ISP DNS and finally works. But, it is
taking about 1-2 minutes for a page to load on a DSL line.

"Bridget" wrote:

> I am having serveral problems with my new Windows 2003 server. I have my
> file server set as PDC and DNS Server and have Active Directory installed on
> it. I also have a Windows server 2003 Exchange server, as well as a Windows
> NT 4.0 Proxy Server 2.0 server.
>
> On the PDC, I have it pointing to itself for DNS server. I have 2
> forwarders setup for the DNS' my ISP gave me.
>
> Here is the list of problems I am having. I think they are all related to
> something in the DNS not setup right b/c they all have to do with name
> communication:
>
> 1) Get prompt for password when browsing Network Neighborhood sometimes on
> XP machines. Sometimes get not accessible error. Sometimes it works fine.
>
> 2) Cannot print to a Dymo label printer. I believe this has to do with #1
> b/c the printer is hooked directly to a workstation.
>
> 3) A client/server version of a software that connects to my Proxy server
> cannot log into the Server portion on the Proxy server from the client.
>
> 4) Get Event ID errors 1053 & 1054 on XP machines.
>
> 5) On Windows 2000 machine, get Event ID 1000 - Windows cannot determine the
> user or computer name. Return value 1722
>
> What I have tried:
>
> Adding in the PDC IP as my Primary DNS on my test XP machine. However, this
> then causes a problem accessing the internet b/c it's not going to the proxy
> server.
>
> All workstations have joined the domain & all user accounts are in Active
> Directory
>
> So, I think that I am missing something that will fix all of this. Any
> thoughts or suggestions are much appreciated.
>
> Thanks,
> Bridget

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

Use this link:
http://support.microsoft.com/default.aspx?scid=kb;en-us;323380

Specifically the sections on removing the root DNS zone and configuring
forwarders. Where it describes setting up forwarders to the ISP, try using
the IP address of your proxy server instead then test internet resolution.

hth DDS W 2k MVP MCSE

"Bridget" <Bridget@discussions.microsoft.com> wrote in message
news:6F9F955A-1573-4F76-BDE0-62527D452183@microsoft.com...
> Thanks. I have my PDC IP as my Primary DNS. Now, I'm just having that
> internet problem. It is so slow that I think it is trying to use the PDC
IP
> as DNS & when it can't, it pulls my ISP DNS and finally works. But, it is
> taking about 1-2 minutes for a page to load on a DSL line.
>
> "Bridget" wrote:
>
> > I am having serveral problems with my new Windows 2003 server. I have
my
> > file server set as PDC and DNS Server and have Active Directory
installed on
> > it. I also have a Windows server 2003 Exchange server, as well as a
Windows
> > NT 4.0 Proxy Server 2.0 server.
> >
> > On the PDC, I have it pointing to itself for DNS server. I have 2
> > forwarders setup for the DNS' my ISP gave me.
> >
> > Here is the list of problems I am having. I think they are all related
to
> > something in the DNS not setup right b/c they all have to do with name
> > communication:
> >
> > 1) Get prompt for password when browsing Network Neighborhood sometimes
on
> > XP machines. Sometimes get not accessible error. Sometimes it works
fine.
> >
> > 2) Cannot print to a Dymo label printer. I believe this has to do with
#1
> > b/c the printer is hooked directly to a workstation.
> >
> > 3) A client/server version of a software that connects to my Proxy
server
> > cannot log into the Server portion on the Proxy server from the client.
> >
> > 4) Get Event ID errors 1053 & 1054 on XP machines.
> >
> > 5) On Windows 2000 machine, get Event ID 1000 - Windows cannot determine
the
> > user or computer name. Return value 1722
> >
> > What I have tried:
> >
> > Adding in the PDC IP as my Primary DNS on my test XP machine. However,
this
> > then causes a problem accessing the internet b/c it's not going to the
proxy
> > server.
> >
> > All workstations have joined the domain & all user accounts are in
Active
> > Directory
> >
> > So, I think that I am missing something that will fix all of this. Any
> > thoughts or suggestions are much appreciated.
> >
> > Thanks,
> > Bridget

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

This may be dumb question - I don't have a forward lookup zone that is just .
I only have one that is mydomain.local and something like
msdtc.mydomain.local. Please advise. Thanks!

"Bridget" wrote:

> Thanks. I have my PDC IP as my Primary DNS. Now, I'm just having that
> internet problem. It is so slow that I think it is trying to use the PDC IP
> as DNS & when it can't, it pulls my ISP DNS and finally works. But, it is
> taking about 1-2 minutes for a page to load on a DSL line.
>
> "Bridget" wrote:
>
> > I am having serveral problems with my new Windows 2003 server. I have my
> > file server set as PDC and DNS Server and have Active Directory installed on
> > it. I also have a Windows server 2003 Exchange server, as well as a Windows
> > NT 4.0 Proxy Server 2.0 server.
> >
> > On the PDC, I have it pointing to itself for DNS server. I have 2
> > forwarders setup for the DNS' my ISP gave me.
> >
> > Here is the list of problems I am having. I think they are all related to
> > something in the DNS not setup right b/c they all have to do with name
> > communication:
> >
> > 1) Get prompt for password when browsing Network Neighborhood sometimes on
> > XP machines. Sometimes get not accessible error. Sometimes it works fine.
> >
> > 2) Cannot print to a Dymo label printer. I believe this has to do with #1
> > b/c the printer is hooked directly to a workstation.
> >
> > 3) A client/server version of a software that connects to my Proxy server
> > cannot log into the Server portion on the Proxy server from the client.
> >
> > 4) Get Event ID errors 1053 & 1054 on XP machines.
> >
> > 5) On Windows 2000 machine, get Event ID 1000 - Windows cannot determine the
> > user or computer name. Return value 1722
> >
> > What I have tried:
> >
> > Adding in the PDC IP as my Primary DNS on my test XP machine. However, this
> > then causes a problem accessing the internet b/c it's not going to the proxy
> > server.
> >
> > All workstations have joined the domain & all user accounts are in Active
> > Directory
> >
> > So, I think that I am missing something that will fix all of this. Any
> > thoughts or suggestions are much appreciated.
> >
> > Thanks,
> > Bridget

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

> I only have one that is mydomain.local and something like
> msdtc.mydomain.local. Please advise. Thanks!


The "." zone may have been deleted already. It must be deleted so when you
right click on your DNS server, in the DNS snapin, the section to input the
IP addresses you want to forward to is not grayed out.

If your forwarders section is available, the "." zone is deleted, continue
by putting the IP address of your proxy server in as forwarders and test.

You may have to run ipconfig /flushdns followed by ipconfig /registerdns on
the testing client from a command prompt.

hth
DDS W 2k MVP MCSE



"Bridget" <Bridget@discussions.microsoft.com> wrote in message
news:58B5EA93-D7D3-4BD4-A40A-09C7048ACF54@microsoft.com...
> This may be dumb question - I don't have a forward lookup zone that is
just .
> I only have one that is mydomain.local and something like
> msdtc.mydomain.local. Please advise. Thanks!
>
> "Bridget" wrote:
>
> > Thanks. I have my PDC IP as my Primary DNS. Now, I'm just having that
> > internet problem. It is so slow that I think it is trying to use the
PDC IP
> > as DNS & when it can't, it pulls my ISP DNS and finally works. But, it
is
> > taking about 1-2 minutes for a page to load on a DSL line.
> >
> > "Bridget" wrote:
> >
> > > I am having serveral problems with my new Windows 2003 server. I have
my
> > > file server set as PDC and DNS Server and have Active Directory
installed on
> > > it. I also have a Windows server 2003 Exchange server, as well as a
Windows
> > > NT 4.0 Proxy Server 2.0 server.
> > >
> > > On the PDC, I have it pointing to itself for DNS server. I have 2
> > > forwarders setup for the DNS' my ISP gave me.
> > >
> > > Here is the list of problems I am having. I think they are all
related to
> > > something in the DNS not setup right b/c they all have to do with name
> > > communication:
> > >
> > > 1) Get prompt for password when browsing Network Neighborhood
sometimes on
> > > XP machines. Sometimes get not accessible error. Sometimes it works
fine.
> > >
> > > 2) Cannot print to a Dymo label printer. I believe this has to do
with #1
> > > b/c the printer is hooked directly to a workstation.
> > >
> > > 3) A client/server version of a software that connects to my Proxy
server
> > > cannot log into the Server portion on the Proxy server from the
client.
> > >
> > > 4) Get Event ID errors 1053 & 1054 on XP machines.
> > >
> > > 5) On Windows 2000 machine, get Event ID 1000 - Windows cannot
determine the
> > > user or computer name. Return value 1722
> > >
> > > What I have tried:
> > >
> > > Adding in the PDC IP as my Primary DNS on my test XP machine.
However, this
> > > then causes a problem accessing the internet b/c it's not going to the
proxy
> > > server.
> > >
> > > All workstations have joined the domain & all user accounts are in
Active
> > > Directory
> > >
> > > So, I think that I am missing something that will fix all of this.
Any
> > > thoughts or suggestions are much appreciated.
> > >
> > > Thanks,
> > > Bridget