Re: port 4125 closed on my server ?
From: Matthew Huynh \(MSFT\) (mhuynh_at_online.microsoft.com)
Date: 03/05/04
- Next message: Oliver R: "Lost Drive M:"
- Previous message: Trevor Daniel: "Exchange Not Workng after install"
- In reply to: Jéjé: "Re: port 4125 closed on my server ?"
- Next in thread: Jéjé: "Re: port 4125 closed on my server ?"
- Reply: Jéjé: "Re: port 4125 closed on my server ?"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 5 Mar 2004 01:50:09 -0800
How are you verifying that the port is open? Did you do the verification
steps of seeing end to end communication through the ISA firewall?
-- Matthew Huynh This posting is provided "AS IS" with no warranties, and confers no rights. "Jéjé" <willgart@_A_hotAmail_A_.com> wrote in message news:uEzTvFkAEHA.3256@TK2MSFTNGP09.phx.gbl... > oohh... > ok... > > When I do this, then I see a listening socket at port 4125 > > internally there is no problem (or by VPN) > but through ISA I can't be connected (but the port is open) > > Does my server publishing rule based on port 4125 is enough? > > "MattHuynh" <matthuynh@attbi.com> a écrit dans le message de > news:%23KHHxNiAEHA.1796@TK2MSFTNGP12.phx.gbl... > > Can you check whether the TS Proxy will start a listening socket on port > > 4125? > > > > On the server just logon to the RWW and connect to a server or machine. > > From the command line type: > > netstat -aon | find "4125" > > Does a listening socket get generated? > > > > > > "Jéjé" <willgart@_A_hotAmail_A_.com> wrote in message > > news:%23xpjVIZAEHA.2316@TK2MSFTNGP10.phx.gbl... > > > thanks... > > > > > > all works fine, I can communicate without problem through the firewall. > > > > > > any other idea? > > > > > > "Matthew Huynh (MSFT)" <mhuynh@online.microsoft.com> a écrit dans le > > message > > > de news:%23eBVLBZAEHA.1700@TK2MSFTNGP12.phx.gbl... > > > > The TS Proxy (which listens on 4125) doesn't start a listening socket > > > until > > > > it is told to do so by the user that is requesting to connect to a > > server > > > or > > > > client in the list. > > > > > > > > I assume you have your web publishing rule setup correctly since you > are > > > > able to access the RWW. > > > > > > > > Try these steps to verify that your ISA server if forwarding > correctly: > > > > > > > > Go to http://isatools.org and download winsocktool.msi > > > > Install it on the SBS server > > > > Launch the winsocktool > > > > Configure the tool for: > > > > Mode: Server > > > > Protocol: TCP > > > > Local address: 0.0.0.0 > > > > Local port: 4125 > > > > Click Listen > > > > On your external client open a command prompt > > > > type telnet <external ip> 4125 > > > > Verify that the telnet session connected by typing some thing. You > > should > > > > see it on the winsocktool console. > > > > > > > > This will tell us if your router is not forwarding the traffic > > correctly. > > > > > > > > > > > > -- > > > > Matthew Huynh > > > > > > > > This posting is provided "AS IS" with no warranties, and confers no > > > rights. > > > > > > > > > > > > "Jéjé" <willgart@_A_hotAmail_A_.com> wrote in message > > > > news:%23yUMw2XAEHA.2808@TK2MSFTNGP10.phx.gbl... > > > > > hi, > > > > > > > > > > my remote desktop doesn't work from the internet, but works fine in > > the > > > > > local network. > > > > > > > > > > its like if my ISA server has the port 4125 closed, but this port is > > > open > > > > > and a server publishing rule redirect it to my SBS server (because > my > > > ISA > > > > > Server is another server) > > > > > > > > > > From the ISA logs, I can see that a user try to be connected trhough > > the > > > > web > > > > > page (a request to the port 4125 is granted) > > > > > but on my SBS server there is no listener for the port 4125!!! > > > > > > > > > > a telnet command to the port 4125 say there is no listener > > > > > and netstat -ao says the same thing. > > > > > > > > > > So, what is the problem? > > > > > there is a missing program? > > > > > > > > > > thanks. > > > > > > > > > > Jerome. > > > > > > > > > > > > > > > > > > > > --- > > > > > Outgoing mail is certified Virus Free. > > > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > > > Version: 6.0.600 / Virus Database: 381 - Release Date: 2004-02-28 > > > > > > > > > > > > > > > > > > > > > > > > > > > --- > > > Outgoing mail is certified Virus Free. > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > Version: 6.0.600 / Virus Database: 381 - Release Date: 2004-02-28 > > > > > > > > > > > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.600 / Virus Database: 381 - Release Date: 2004-02-28 > >
- Next message: Oliver R: "Lost Drive M:"
- Previous message: Trevor Daniel: "Exchange Not Workng after install"
- In reply to: Jéjé: "Re: port 4125 closed on my server ?"
- Next in thread: Jéjé: "Re: port 4125 closed on my server ?"
- Reply: Jéjé: "Re: port 4125 closed on my server ?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|