Vista call home feature

  • Thread starter Thread starter Will
  • Start date Start date
W

Will

Does anybody know which port vista uses to call back to the MSFT servers ?
I'm not really happy with the fact that Vista calls home to MSFT everytime
windows starts once vista is released I will buy it, and I will leave this
function intact in order to activate the product however after that I intend
to block the port it uses to call home. Does anyone know which port it uses
?
 
I was thinking about the possibility of writing a program that listens on
that port and pretends it is Microsoft's servers. Assuming you knew exactly
what was send and received, and the response from their servers, it couldn't
be that difficult. You would need a program to spy on those ports while it
is activating to find what is send and received.

Uh oh, why am I talking about this in public? Anyway, I'm sure they must
have a code that it returns that is tied with the day it was generated
because apparently you can't activate your computer when the system clock is
set wrong.

Robert Firth
http://www.winvistainfo.org
 
Thats an interesting concept. I was just thinking of stopping it from
calling home technically if the computer is activated it should be good to
go without it having the ability to call home to MSFT, if it was used as an
offline computer it wouldn't have the ability to call home either and
shouldn't be effected
The only exeption to this would be when you install updates.
I don't intend to patch it or run applications that stop it from calling
home I just want to set the port number as blocked in my router
configuration that way I can easily allow communication on that port inorder
to get updates
 
Ah, well, I bet you the port they use will be the same port you connect to
the internet with, just a wild guess. Because of that, disabling that port
could prevent you from connecting to the internet. At least, that is what I
would do if I was Microsoft.

Robert Firth
http://www.winvistainfo.org
 
That's not Will's talking about Kevin.
This is about SPP-the child of WGA N. Not about WGA or OGA itself.
need to read the article ya linked.
That's OGA; not OGA N. lol
too funny.

Jeff
 
Kevin,

That's ok.
WGA/OGA doesn't phone home itself. It just resides on your pc;and interacts
if you go to a WGA/OGA download.
SPP and WGA N on the other hand;are the programs;that phone home at every
bootup-(or at least try to).
There's no OGA N; YET-lol. and it seems, as was stated at the end of
that linked article; that WGA N is no longer on MSFT's servers.
Yanked.
Let's hope MSFT wakes up about SPP.
Probably not, and most people won't care;or don't even know that they've
agreed to let MSFT search their pc;at every bootup ;by using Vista.
And;just like WGA N; when it starts shutting down legit customers;which; it
will, people may wake up.
But;again;probably not.
But hey; it's got a cool gui.!! LOL

Jeff
 
Will said:
Does anybody know which port vista uses to call back to the MSFT servers ?
I'm not really happy with the fact that Vista calls home to MSFT everytime
windows starts once vista is released I will buy it, and I will leave this
function intact in order to activate the product however after that I
intend to block the port it uses to call home. Does anyone know which port
it uses ?

Just unplug the Speak 'n Spell.

Jon
 
Ok, although I'm not officially supporting what you want to do, I have some
answers I think.

Well, maybe not about phoning home, but...

Windows Activation:
Connection: TCP->Https
IP: 65.54.183.202
Port, local: 51708
Port, remote (their server): 443

Windows Update:
Connection: TCP->Https
IP: 207.46.254.94
Port, local: 51757
Port, remote (their server): 443

I hope this is useful.

Robert Firth
http://www.winvistainfo.org
 
Yes thats the info I was after
Well the main items of interest anyway
this will allow me to disable communications in my router settings there are
probably quite a few more I need to disable but I'm scanning for them so
I'll find them sooner or later

Ps I don't intend to do anything illegal with this information I just want
to tame the call home feature a little, well at least so that I decide when
my pc contacts MSFT instead of it happening in the background without my
knowledge.
This under the privacy laws of the country I live in, is quite legal
 
By the way, what you want to do is a very very bad idea. If you do something
that trips an activation (I've done that before playing with the registry),
you may end up unable to activate... of course this is still assuming the
'phone home feature' uses the same port as activation. Something to think
about.

Robert Firth
http://www.winvistainfo.org
 
Will said:
Thats an interesting concept. I was just thinking of stopping it from
calling home technically if the computer is activated it should be good
to go without it having the ability to call home to MSFT, if it was used
as an offline computer it wouldn't have the ability to call home either
and shouldn't be effected

Yes, but it is not offline and it can easily
detect that fact and disable Vista from running.

Steve
 
Robert said:
Ah, well, I bet you the port they use will be the same port you connect
to the internet with, just a wild guess. Because of that, disabling that
port could prevent you from connecting to the internet. At least, that
is what I would do if I was Microsoft.

You don't disable the port, you disabling getting
to the destination address.

Steve
 
Thats fine I don't intend tampering with the software all these ports can
easily be blocked in my router settings and can easily be undone if I need
to reactivate
 
Robert Firth said:
Ok, although I'm not officially supporting what you want to do, I have
some answers I think.

Well, maybe not about phoning home, but...

Windows Activation:
Connection: TCP->Https
IP: 65.54.183.202
Port, local: 51708
Port, remote (their server): 443

65.54.183.202 resolves to login.live.com. Are you sure this is correct IP?
 
Yeah, I noticed that. I found it quite curious. I'll have to check again,
but during activation my computer sent many many many large packets to that
IP address. I think it was the only IP it was sending packets to at the
time, and I wasn't doing anything else at the time.

Robert Firth
http://www.winvistainfo.org
 
Back
Top