From: "David Blair" 

Check my last reply to Rich. A case of a firewall that doesn't disable
itself even when it says it does.
"Geo."  wrote in message
news:3ebafa19$1{at}w3.nls.net...
> do you have more than one protocol loaded (perhaps tcp and IPX?). if so
then
> tcp is dead and it's using the other protocol. Try and ping 127.0.0.1 and
> see if that works.
>
> Geo.
>
> "David Blair"  wrote in message
> news:3eb9bed7{at}w3.nls.net...
> Figure this out.
>
> Terminal services on WIndows Server 2003 RC2 (haven't upgraded yet because
I
> have Office 2003 Beta 2 running and it tests against this release.) This
is
> on my home servier, which has developed a flakiness in the power supply in
> the last 2 days. It decided to crash this afternoon, and when I was able
to
> bring it up, it suddel;y stopped allowing me to sign in via Terminal
> Services- but only from ONE machine- another similarly configured machine
> (WIndows Server 2003 RC2.) I've been using the client for a while
> succesfsully. I can get to the server just fine from my XP Pro machine.
>
> The oddity seems not to be the server, but the one machine that can't sign
> in, though. I noticed I can't ping any machines from this machine (the one
> I'm typing the post from.) NO machine can ping THIS machine. Yet I can
share
> this machine's drives, it can pick up drives on other machines. It can get
> out to the Internet happily. I can use VNC to see the server. I can use
> Terminal Services to get sessions on THIS server just fine.
>
> I am not using a domain system at the moment.
>
> Summary:
>
> From problem server, which did NOT crash:
>
> 1. cannot be pinged
> 2. cannot ping others
> 3. cannot initiate Terminal Services session on other server after that
> server crashed though it could prior to crash.
> 4. can assign drives on other machines
> 5. can share drives with other machines.
>
> From the server which crashed:
>
> 1. cannot ping the problem server
> 2. can be pinged by other servers and PCs on the net
> 3. other machines can start Terminal Services sessions other than problem
> server
> 4. was able to provide Terminal Services session to problem server before
it
> crashed.
>
> Anyone have any ideas? I really need TS on this machine.
>
> Here is the error I get from the Terminal Services client:
> The machine is idle, so it isn't too busy. I've rebooted both machines.
>
> Thoughts?
>
>
>
>
>
>

--- BBBS/NT v4.01 Flag-4