Re: XP Pro not accessable via LAN or VPN

Thanx Steve,
I am resigned to the fact I need to travel down to the site to have a
good look at the problem. I literally have tried everything I can think
of including the above from another box on the remote LAN but no joy.
Its almost as though its not even turned on, but I can confirm it is. I
have also ran Dameware which couldnt find anything, and VNC..
The only connection I can sort of get is when I run Net View, which
returns the computer name. I took you suggestion on board & ran PortQry
with the following results:

C:\Documents and Settings\GaryB.mydomain>C:\PortQryV2\PortQry.exe -n
192.168.254.50 -o 139,445,3389

Querying target system called:

192.168.254.50

Attempting to resolve IP address to a name...

Failed to resolve IP address to name

querying...

TCP port 139 (netbios-ssn service): FILTERED

TCP port 445 (microsoft-ds service): FILTERED

TCP port 3389 (unknown service): FILTERED

Is that whats expected? I also tried to run the suite of PSTOOLs but
path couldnt be found!
G

.

Relevant Pages

  • DCPromo and VPN fails
    ... Querying target system called: ... Attempting to resolve IP address to a name... ... TCP port 135: ...
    (microsoft.public.windows.server.active_directory)
  • Re: NTP Problem
    ... Querying target system called: ... Attempting to resolve IP address to a name... ... TCP port 123 (unknown service): ...
    (microsoft.public.win2000.general)
  • Re: dcdiag - Starting test: KnowsOfRoleHolders - DsBindWithSpnEx() failed with error 1722
    ... I was able to resolve the remote DC's with the nslookup command. ... TCP port 1094 (unknown service): ... Are you able to use PORTQRY against the Schema master? ...
    (microsoft.public.windows.server.active_directory)
  • Re: rendom /prepare failed to bind to server
    ... Attempting to resolve name to IP address... ... TCP port 1753 (unknown service): NOT LISTENING ...
    (microsoft.public.windows.server.active_directory)