| Author |
Message |
Mark Dutton
Guest
|
 Posted:
Tue Jan 18, 2005 11:27 pm Post subject:
Slow Network and Other Issues -- W2K & XP |
|
|
I would like to think I have a pretty simple network with one W2K server and
about 10 XP Pro workstations and no remote locations. When I first
installed everything were went smoothly. Now after a few months I seem to
have nothing but problems. Things like logins can sometimes be extremely
slow, loading word and excell files takes for ever to load, and waht would
seem like simple things take forerver. I get errors messages in worstations
logs that the domain can't be found and other various messages. their Even
surfung a newwork mapeed drive can take a few minutes to browse. At this
point I don't know if it server or workstation related. All seems network
related.
I have begin to questioned my orginal instattion of AD and DNS. The more I
have read here the more I belive everyhting is somehow realted to this, but
the more I read about AD and DNS the more it clouds things. I clearer
understanding of AD and DNS. Maybe I am putting to much into this.
Here is what I did and what I have when I installed W2K:
The Server: srv01 192.168.0.10 running DHCP (no WINS)
Worksations 192.168.0.100-150
A Linksys Router connected to broadband cable doing NAT 192.168.0.1
DNS mydomain.local
We have a domain for our company "mydomain.com", so in the setup for AD I
used mydomain.local.
Server is DNS looks like: srv01.mydomain.local.
One thing I noticed with a couple of artciles here is I don't belive I have
our DNS forwarded and pointed to our ISP. The workstations get their DNS (I
am using the address from the cable provider) addresses from the DHCP. I
never could get the workstations to "browse" the net unless I did it this
way. Now I feel I may have caused my current problems. If I do need to do
this, how do I?
I don't feel that it is an sort of hardware issue.. my machines consist of
2.6-.3.0 P4's with 512MB-1GB of RAM. Server is also a killer box and runs
great
Any suggestions on where to start or some sort of a direction wouldl be
GREATLY appreicated!
I am a one man IT department and I just don't have anyone to bounce things
off of.
Thanks!!!
.. |
|
| Back to top |
|
 |
Doug Sherman [MVP]
Guest
|
| Posted:
Tue Jan 18, 2005 11:50 pm Post subject:
Re: Slow Network and Other Issues -- W2K & XP |
|
|
You have correctly identified the problem. You must configure the
workstations to point to 192.168.0.10 for DNS. The server also must point
only to itself for DNS.
In order to enable resolution of Internet names, you need to configure
Forwarders:
On the server, open the DNS console. Right click on the server and select
Properties. Click the Forwarders tab, check the Enable forwarders box,
enter the IP address of your ISP's DNS server and click Add. If these
options are not avalaible, expand the Forward Lookup Zones and delete the
"." zone.
Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
"Mark Dutton" <not.available@online> wrote in message
news:uWnn$LY$EHA.3368@TK2MSFTNGP10.phx.gbl...
| Quote: | I would like to think I have a pretty simple network with one W2K server
and
about 10 XP Pro workstations and no remote locations. When I first
installed everything were went smoothly. Now after a few months I seem to
have nothing but problems. Things like logins can sometimes be extremely
slow, loading word and excell files takes for ever to load, and waht would
seem like simple things take forerver. I get errors messages in
worstations
logs that the domain can't be found and other various messages. their Even
surfung a newwork mapeed drive can take a few minutes to browse. At this
point I don't know if it server or workstation related. All seems network
related.
I have begin to questioned my orginal instattion of AD and DNS. The more
I
have read here the more I belive everyhting is somehow realted to this,
but
the more I read about AD and DNS the more it clouds things. I clearer
understanding of AD and DNS. Maybe I am putting to much into this.
Here is what I did and what I have when I installed W2K:
The Server: srv01 192.168.0.10 running DHCP (no WINS)
Worksations 192.168.0.100-150
A Linksys Router connected to broadband cable doing NAT 192.168.0.1
DNS mydomain.local
We have a domain for our company "mydomain.com", so in the setup for AD I
used mydomain.local.
Server is DNS looks like: srv01.mydomain.local.
One thing I noticed with a couple of artciles here is I don't belive I
have
our DNS forwarded and pointed to our ISP. The workstations get their DNS
(I
am using the address from the cable provider) addresses from the DHCP. I
never could get the workstations to "browse" the net unless I did it this
way. Now I feel I may have caused my current problems. If I do need to
do
this, how do I?
I don't feel that it is an sort of hardware issue.. my machines consist
of
2.6-.3.0 P4's with 512MB-1GB of RAM. Server is also a killer box and runs
great
Any suggestions on where to start or some sort of a direction wouldl be
GREATLY appreicated!
I am a one man IT department and I just don't have anyone to bounce things
off of.
Thanks!!!
.
|
|
|
| Back to top |
|
|
Mark Dutton
Guest
|
| Posted:
Wed Jan 19, 2005 12:40 am Post subject:
Re: Slow Network and Other Issues -- W2K & XP |
|
|
Thanks Doug! I thought I was losing my mind.. what little I have left :-)
OK.. made those changes and changes to DHCP against the workstations..
How can I tell that I have the server pointing to itself in DNS (where do I
look?)
Thanks for the help!!!
Mark
"Doug Sherman [MVP]" <dsherman@nospam.tampabay.rr.com> wrote in message
news:%23UNY2YY$EHA.1400@TK2MSFTNGP11.phx.gbl...
| Quote: | You have correctly identified the problem. You must configure the
workstations to point to 192.168.0.10 for DNS. The server also must point
only to itself for DNS.
In order to enable resolution of Internet names, you need to configure
Forwarders:
On the server, open the DNS console. Right click on the server and select
Properties. Click the Forwarders tab, check the Enable forwarders box,
enter the IP address of your ISP's DNS server and click Add. If these
options are not avalaible, expand the Forward Lookup Zones and delete the
"." zone.
Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
"Mark Dutton" <not.available@online> wrote in message
news:uWnn$LY$EHA.3368@TK2MSFTNGP10.phx.gbl...
I would like to think I have a pretty simple network with one W2K server
and
about 10 XP Pro workstations and no remote locations. When I first
installed everything were went smoothly. Now after a few months I seem
to
have nothing but problems. Things like logins can sometimes be extremely
slow, loading word and excell files takes for ever to load, and waht
would
seem like simple things take forerver. I get errors messages in
worstations
logs that the domain can't be found and other various messages. their
Even
surfung a newwork mapeed drive can take a few minutes to browse. At this
point I don't know if it server or workstation related. All seems network
related.
I have begin to questioned my orginal instattion of AD and DNS. The more
I
have read here the more I belive everyhting is somehow realted to this,
but
the more I read about AD and DNS the more it clouds things. I clearer
understanding of AD and DNS. Maybe I am putting to much into this.
Here is what I did and what I have when I installed W2K:
The Server: srv01 192.168.0.10 running DHCP (no WINS)
Worksations 192.168.0.100-150
A Linksys Router connected to broadband cable doing NAT 192.168.0.1
DNS mydomain.local
We have a domain for our company "mydomain.com", so in the setup for AD I
used mydomain.local.
Server is DNS looks like: srv01.mydomain.local.
One thing I noticed with a couple of artciles here is I don't belive I
have
our DNS forwarded and pointed to our ISP. The workstations get their DNS
(I
am using the address from the cable provider) addresses from the DHCP. I
never could get the workstations to "browse" the net unless I did it this
way. Now I feel I may have caused my current problems. If I do need to
do
this, how do I?
I don't feel that it is an sort of hardware issue.. my machines consist
of
2.6-.3.0 P4's with 512MB-1GB of RAM. Server is also a killer box and
runs
great
Any suggestions on where to start or some sort of a direction wouldl be
GREATLY appreicated!
I am a one man IT department and I just don't have anyone to bounce
things
off of.
Thanks!!!
.
|
|
|
| Back to top |
|
|
Doug Sherman [MVP]
Guest
|
| Posted:
Wed Jan 19, 2005 2:56 am Post subject:
Re: Slow Network and Other Issues -- W2K & XP |
|
|
On the server, Right click My Network Places and select Properties. Right
click the Local Area Connection and select Properties. Highlight TCP/IP and
click the Properties button. Make sure that the server has a manually
entered IP address - this address or 127.0.0.1 should also be entered in the
Preferred DNS server line.
Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
"Mark Dutton" <not.available@online> wrote in message
news:%23Wdao0Y$EHA.1408@TK2MSFTNGP10.phx.gbl...
| Quote: | Thanks Doug! I thought I was losing my mind.. what little I have left
:-)
OK.. made those changes and changes to DHCP against the workstations..
How can I tell that I have the server pointing to itself in DNS (where do
I
look?)
Thanks for the help!!!
Mark
"Doug Sherman [MVP]" <dsherman@nospam.tampabay.rr.com> wrote in message
news:%23UNY2YY$EHA.1400@TK2MSFTNGP11.phx.gbl...
You have correctly identified the problem. You must configure the
workstations to point to 192.168.0.10 for DNS. The server also must
point
only to itself for DNS.
In order to enable resolution of Internet names, you need to configure
Forwarders:
On the server, open the DNS console. Right click on the server and
select
Properties. Click the Forwarders tab, check the Enable forwarders box,
enter the IP address of your ISP's DNS server and click Add. If these
options are not avalaible, expand the Forward Lookup Zones and delete
the
"." zone.
Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
"Mark Dutton" <not.available@online> wrote in message
news:uWnn$LY$EHA.3368@TK2MSFTNGP10.phx.gbl...
I would like to think I have a pretty simple network with one W2K
server
and
about 10 XP Pro workstations and no remote locations. When I first
installed everything were went smoothly. Now after a few months I seem
to
have nothing but problems. Things like logins can sometimes be
extremely
slow, loading word and excell files takes for ever to load, and waht
would
seem like simple things take forerver. I get errors messages in
worstations
logs that the domain can't be found and other various messages. their
Even
surfung a newwork mapeed drive can take a few minutes to browse. At
this
point I don't know if it server or workstation related. All seems
network
related.
I have begin to questioned my orginal instattion of AD and DNS. The
more
I
have read here the more I belive everyhting is somehow realted to this,
but
the more I read about AD and DNS the more it clouds things. I clearer
understanding of AD and DNS. Maybe I am putting to much into this.
Here is what I did and what I have when I installed W2K:
The Server: srv01 192.168.0.10 running DHCP (no WINS)
Worksations 192.168.0.100-150
A Linksys Router connected to broadband cable doing NAT 192.168.0.1
DNS mydomain.local
We have a domain for our company "mydomain.com", so in the setup for AD
I
used mydomain.local.
Server is DNS looks like: srv01.mydomain.local.
One thing I noticed with a couple of artciles here is I don't belive I
have
our DNS forwarded and pointed to our ISP. The workstations get their
DNS
(I
am using the address from the cable provider) addresses from the DHCP.
I
never could get the workstations to "browse" the net unless I did it
this
way. Now I feel I may have caused my current problems. If I do need
to
do
this, how do I?
I don't feel that it is an sort of hardware issue.. my machines
consist
of
2.6-.3.0 P4's with 512MB-1GB of RAM. Server is also a killer box and
runs
great
Any suggestions on where to start or some sort of a direction wouldl be
GREATLY appreicated!
I am a one man IT department and I just don't have anyone to bounce
things
off of.
Thanks!!!
.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in