Thanks to everyone for the responses.
I didn't get a chance to actually test this via the VPN at home last night.
I did attempt to ping the box as FQDN, as I have been doing all along from
another box in the office this morning
PING boxname.domain.local
This returned the same message.
NSLOOKUP gave me the IP and I pinged the IP. Which promptly responded with
results. I got interrupted and checked the FQDN again about 20 minutes
later. It now works.
When I attempted to get access to the box via the VPN, I had just pulled my
laptop out of my bag and started it from a cold start. Connected to the VPN
with those results. Next time, I'll NSLOOKUP to get the IP and PING it a
when Remote Desktop doesn't find the box.
It might be related to the box had not been restarted but the Active
Directory Controller had.
tracert, nbtstat, and netstat will be used next time I run into this as
well.
Tracy Pearson
PowerChurch Software
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
