B
Brice Behringer
Hello.
I've got a relatively new W2K domain. Remote machines are using a software
VPN to our SonicWALL firewall. When machines are remote, their file system
connectivity fails. Ping is successful, as is hard LMHOST file resolution.
Outlook works ok to the exchange server but is slow and hangy. When trying
to access an already mapped drive we're told "The network path is already in
use". When typing \\servername in the address box we're told "The server
could not be accessed". This issue resolves if we enter the domain's LAN
DNS server as the primary, but the machine still is slow 'cause it's
constantly checking with the domain server when it does anything. DOS
command Net View \\servername returns System Error 5 - Access is denied.
If we log on to the local machine's domain (i.e. NOT authenticating to the
domain) it all works quickly and solidly. I can enumerate shared folders,
access shared drives. Net View \\servername returns an enumerated list of
server published resources.
Other facts - Internal and External DNS spaces are the same. Nslookup to
the internal DNS server correctly returns the NAT address of my server and
domain name space. Nslookup to an external DNS server returns an entry for
the name space, but no IP address.
Here's what I'm thinking: Clearly we know this has something to do with
resolution. While it may, or may not be the problem, hard coding my
internal DNS server treats the symptoms - albeit painfully. I wonder if
there's not something in the NTFS Redirector Module that has gotten
confused. Does anybody have any ideas how to resolve?
I've already cleared and reinstalled all the networking services (Client for
MS Networks, TCP/IP, File/Printer sharing, DNE). I've disjoined and
rejoined the domain. I've also uninstalled the VPN client and am testing
from another office with a Box-To-Box VPN solution I know works.
Thanks for your help,
Brice Behringer
Sigma Information Group, Inc.
I've got a relatively new W2K domain. Remote machines are using a software
VPN to our SonicWALL firewall. When machines are remote, their file system
connectivity fails. Ping is successful, as is hard LMHOST file resolution.
Outlook works ok to the exchange server but is slow and hangy. When trying
to access an already mapped drive we're told "The network path is already in
use". When typing \\servername in the address box we're told "The server
could not be accessed". This issue resolves if we enter the domain's LAN
DNS server as the primary, but the machine still is slow 'cause it's
constantly checking with the domain server when it does anything. DOS
command Net View \\servername returns System Error 5 - Access is denied.
If we log on to the local machine's domain (i.e. NOT authenticating to the
domain) it all works quickly and solidly. I can enumerate shared folders,
access shared drives. Net View \\servername returns an enumerated list of
server published resources.
Other facts - Internal and External DNS spaces are the same. Nslookup to
the internal DNS server correctly returns the NAT address of my server and
domain name space. Nslookup to an external DNS server returns an entry for
the name space, but no IP address.
Here's what I'm thinking: Clearly we know this has something to do with
resolution. While it may, or may not be the problem, hard coding my
internal DNS server treats the symptoms - albeit painfully. I wonder if
there's not something in the NTFS Redirector Module that has gotten
confused. Does anybody have any ideas how to resolve?
I've already cleared and reinstalled all the networking services (Client for
MS Networks, TCP/IP, File/Printer sharing, DNE). I've disjoined and
rejoined the domain. I've also uninstalled the VPN client and am testing
from another office with a Box-To-Box VPN solution I know works.
Thanks for your help,
Brice Behringer
Sigma Information Group, Inc.