Re: XP Pro not accessable via LAN or VPN
- From: "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 18 Jan 2006 12:47:11 -0600
If you can not ping the machine by name or at least IP address it seems you
have some IP filtering going on somewhere. It may also help to try and use
tracert to the computers IP to see if you can detect if the hang up is the
computer or a router/firewall in the path. You could also try using portqry
which is a command line port scanner from your computer specifying the IP
address of the remote computer you can not access to see if you can see any
ports open on that computer from your computer as per example below. You
need to establish basic connectivity before we can consider other problems.
I would also run the support tool netdiag on your computer and the computer
you can not access looking for any problems and post the results here in a
reply if possible and also post the results of netstat -an on the remote
computer [to verify if ports 139/445/3389 are active or not]. You said that
you ruled out Windows Firewall but ipsec policies could also be an issue and
netdiag will show if an ipsec policy is assigned. If the remote computer is
behind a firewall have it booted into safe mode with networking to see if
that makes a difference which will boot into bare bones mode disabling most
start up applications and services that may be blocking access. --- Steve
http://support.microsoft.com/default.aspx?scid=kb;en-us;310099&sd=tech ---
portqry
D:\Documents and Settings\Steve>portqry -n 192.168.1.105 -o 139,445,3389
Querying target system called:
192.168.1.105
Attempting to resolve IP address to a name...
IP address resolved to SERVER1-2000
querying...
TCP port 139 (netbios-ssn service): LISTENING
TCP port 445 (microsoft-ds service): LISTENING
TCP port 3389 (unknown service): LISTENING
"gstar" <gary.brett@xxxxxxxxx> wrote in message
news:1137581822.535788.268260@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi Steven & thanx for your reply,
> I cannot even ping them from machines on their local LAN/trusted
> domain. We have a VPN setup site to site so should be no drama there,
> but that would not affect the local PCs anyway would it?
> The site is 150 miles or so away so I asked a local user to enable
> remote desktop but it states that the default C$ needs enabling, which
> it already is. From an affected machine they can also ping other LAN
> PCs and perform day to day LAN tasks without a problem.
>
> Any advice appreciated on this.
>
> Thanx
> G
>
.
- References:
- XP Pro not accessable via LAN or VPN
- From: gstar
- Re: XP Pro not accessable via LAN or VPN
- From: Steven L Umbach
- Re: XP Pro not accessable via LAN or VPN
- From: gstar
- XP Pro not accessable via LAN or VPN
- Prev by Date: Re: System administrator has set policies...
- Next by Date: Re: Administrator Lost Password HELP
- Previous by thread: Re: XP Pro not accessable via LAN or VPN
- Next by thread: Re: XP Pro not accessable via LAN or VPN
- Index(es):
Relevant Pages
|
