S
sithlord70
I am setting up or should I say improving a network at a small company.
They currently run a 2k server with Exchange. It is set up as a PDC but
they do not really use it that way in that they have been up until now
logging in locally on their XP Pro clients. The only real purpose for
the machine was for Exchange and even with that all they really use it
for is to share the calender. They POP all their email locally from
their public domain using Outlook. I want them to start logging into
the domain so I can set up policys and roaming profiles and such. Now
here is my dilema. To start I turned off the DHCP services on their
router and have activated the DNS and DHCP services on the Exchange
server. It all seems to work fine but a strange thing is happening.
While the DHCP is working fine, when I set the DNS and Name Server
scope options to point to the internal DNS server which is itself and
then the external DNS in that order, I am able to log onto the domain
from the client quickly but unable to connect to their external POP
server and I can access some but not all websites. Google strangely is
one that is not accessible. I then added the external DNS to the DNS
Forward option in DNS but that didn't help. Now if I reverse DNS and
Name Server scope options and put the internal DNS second and the
external DNS first, then logging onto the domain from the client
understandably takes forever because it apparently ignores the second
DNS entry which is now the internal one and spends 5 minutes trying to
resolve the internal DNS before finally logging in. Once in though now
the POP server and all websites are completely accessible. An Ipconfig
/all confirms that the client does get the DNS addresses via DHCP fine
but it appears that the client ignores the second DNS entry in the list
and always looks only to the first for resolution. Why is this
occuring. Not sure what I overlooked.
Also to note, the domain name of AD is the same as their public email
domain (Not my doing, the guy that set it up originally did that). It
may or may not have something to do with the POP server connection
issue but that would not explain the access problems to websites such
as Google.
Thanks in advance,
Adam
They currently run a 2k server with Exchange. It is set up as a PDC but
they do not really use it that way in that they have been up until now
logging in locally on their XP Pro clients. The only real purpose for
the machine was for Exchange and even with that all they really use it
for is to share the calender. They POP all their email locally from
their public domain using Outlook. I want them to start logging into
the domain so I can set up policys and roaming profiles and such. Now
here is my dilema. To start I turned off the DHCP services on their
router and have activated the DNS and DHCP services on the Exchange
server. It all seems to work fine but a strange thing is happening.
While the DHCP is working fine, when I set the DNS and Name Server
scope options to point to the internal DNS server which is itself and
then the external DNS in that order, I am able to log onto the domain
from the client quickly but unable to connect to their external POP
server and I can access some but not all websites. Google strangely is
one that is not accessible. I then added the external DNS to the DNS
Forward option in DNS but that didn't help. Now if I reverse DNS and
Name Server scope options and put the internal DNS second and the
external DNS first, then logging onto the domain from the client
understandably takes forever because it apparently ignores the second
DNS entry which is now the internal one and spends 5 minutes trying to
resolve the internal DNS before finally logging in. Once in though now
the POP server and all websites are completely accessible. An Ipconfig
/all confirms that the client does get the DNS addresses via DHCP fine
but it appears that the client ignores the second DNS entry in the list
and always looks only to the first for resolution. Why is this
occuring. Not sure what I overlooked.
Also to note, the domain name of AD is the same as their public email
domain (Not my doing, the guy that set it up originally did that). It
may or may not have something to do with the POP server connection
issue but that would not explain the access problems to websites such
as Google.
Thanks in advance,
Adam