Use nslookup with the d2 switch to see debugging information. This will tell you exactly what is being sent under the covers.
Edward E. Ziots Network Engineer Lifespan Organization Email: [EMAIL PROTECTED] Phone: 401-639-3505 MCSE, MCP+I, ME, CCA, Security +, Network + -----Original Message----- From: Ben Scott [mailto:[EMAIL PROTECTED] Sent: Friday, November 14, 2008 1:41 PM To: NT System Admin Issues Subject: Re: What could cause this VPN issue? On Fri, Nov 14, 2008 at 1:06 PM, Evan Brastow <[EMAIL PROTECTED]> wrote: > I have a weird problem and I'm not sure where to start troubleshooting it. In addition to everyone else's good suggestions: You state "... he can't even resolve his computer name to connect via RAdmin". What about if he tries connecting by IP address rather than name? I'd also try testing name resolution manually: Open a command prompt on the client. See if it can ping your DNS/WINS servers by IP address, then by name. Use NSLOOKUP to run DNS queries against the name's you are after. Try both unqualified and fully qualified variants for the queries. Also try variants using the default nameservers and specifying your nameserver IP addresses explicitly. For example: nslookup foo nslookup foo.example.com. nslookup foo 192.0.2.31 nslookup foo.example.com. 192.0.2.31 The periods at the end of the FQDNs are not typos. If using NetBIOS names, use NBTSTAT to check what you can. For example, listing the remote name table of one's WINS server is a good test. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
