Re: Vista patch breaks forwarding of port 445?

Mike <[email protected]> Fri, 14 Dec 2007 14:27:04 -0800 (PST)
Newsgroups gmane.network.ssh.windows
Message-ID <[email protected]>
That was one of the first things I checked and it wasn't selected.  I even tried a "telnet 10.0.0.222 445" and got no response, so there's nothing listening on that port, yet Vista won't let me use it.  Did Microsoft break this intentionally to make SMB "safer?"  I'd like to know if anyone else can reproduce the problem so I can be sure it's not unique to my machine. 

----- Original Message ----
From: "Welsh, Armand" <[email protected]>
To: [email protected]
Sent: Friday, December 14, 2007 7:53:49 AM
Subject: RE: Vista patch breaks forwarding of port 445?




 
DIV {
MARGIN:0px;}



After applying the patches, check that the patch did not 
bind the microsoft client service to the loopback adapter.  If it did, then 
you won't be able to bind to port 445, because the microsoft networking client 
service is already listening on the port.  When creating a loopback 
interface to use only this type of purpose, you should disable (or remove) all 
services, leaving only the TCP/IP protocol, and nothing else.  This will 
ensure you have a wide open interface, ready for 3rd party software 
bindings.

 

Armand




From: [email protected] 
[mailto:[email protected]] On Behalf Of Mike
Sent: Friday, 
December 14, 2007 6:49 AM
To: [email protected]
Subject: 
Vista patch breaks forwarding of port 445?






Yesterday I installed the latest set of Vista patches from Microsoft 
Update.  I also made a few other changes, like turning off User Account 
Control.  Immediately before this I was able to forward port 445 using "ssh 
-L 10.0.0.222:445:localhost:445 user@server" where 10.0.0.222 is a loopback 
adapter in Windows.  After installing the patches I got an error message 
saying port 445 could not be forwarded. So I used Windows Restore to rollback 
the patches and everything worked correctly again.  Looking through the 
patches I'd just installed I found this one addressing a SMB 
vulnerability:
http://www.microsoft.com/technet/security/bulletin/ms07-063.mspx

I'm 
guessing it was this one that screwed up the port forwarding.  Has anyone 
else ran into this issue?






Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try 
it now.





      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs