Title: Message
|
What happens when you run NSLookup? Can you resolve names from your
listed DNS Servers?
How about NetDiag?
Sounds like perhaps DNS traffic might be being
blocked?
**********************
Charlie Kaiser
MCSE, CCNA
Systems
Engineer
Essex Credit / Brickwalk
510 595
5083
**********************
I
have a problem with my DNS over the WAN and VPN. Here is the
issue. For some reason DNS will not resolve names over the WAN, or
VPN. I can only connect to resources by IP address. This problem
started when I upgraded my network in January. We switched to a Cisco IP
phone system along with all Cisco gear (VPN concentrator, PIX firewall,
switches, routers...lots of money spent). We also upgraded our network at
the same time from W2k to Server 2003. We have a Point to Point T
between our sights and a T1 for internet access here. We have about 30
people who VPN into the network on the VPN concentrator. Our AD (I
actually run all IT for 3 companies, same owners) is one Root domain with 3
child domains 1 for each company. All common resources and user accounts
are in the root. Computer accounts and private resources are in each child
domain. The child domains share nothing. Due to the phone system we have
several V-LAN's one for voice, VPN, Guest, and computer
network.
When
I am at the other location I can't browse the network, or attach to mapped
drives from my logon script (they don't even appear). I can only attach
to resources if I create a new mapped drive by IP address. When I do an
IP config I get all the right DNS servers listed. I can only ping them
by IP address. The same situation happens when I VPN from home. We
had DNS only on the network. My Cisco vendor told me it's not their
gear. I added WINS to see if this would help...it did not. Any suggestions
on what I could have configured incorrectly? Could it be the Cisco
routers?
Thank
you for the help!
Todd
Graham
IT Manager
Urell Inc.
617-600-9355
[EMAIL PROTECTED]
|
