TorB,

So it's still somewhat inconclusive if we'er connecting to EWB or something else is intercepting this.

If you're up for more experimentation then this is what i would try next :

1. If you leave the TCPView program running and sorted by "Local Port" column it will actually show the new telnet session as you execute telnet connection. It would highlighted by green for a seconds. Basically see if you see 2 lines for webbuilder after you've run the telnet but before you type anything else.

2. Did you try doing the telnet with 127.0.0.1 address (instead of localhost) so type telnet 127.0.0.1 80 and then proceed as before.

Raul

<<Hi Raul.
But when I run the command GET / HTTP/1.1 and hit ENTER twice the
telnet program exits and I am back on the command prompt again. :-/
>>

Hi Raul.
I have done as you adviced
I have tried both the name 'localhost' and the localhost ip address
127.0.0.1, same problem.
In TCPView I see another process starting when running the command
TELNET LOCALHOST 80.
This is a process on http port with state ESTABLISHED which should be normal.
--
I then execute the GET / HTTP/1.1 command, which by the way is not
echoed on the screen, I only see the cursor moving when typing the
command. After hitting ENTER twice, the process goes yellow for a short
time and then changes to a system process with state TIME_Wait. In the
command window I can see that the GET command exits and I am then back
on the command prompt again.
--
My Windows is a Parallells Desktop 7 virtual Windows on a MacBookPro. I
have also checked the options in Parallells to see if there is
something there which is blocking the connection. Nothing obvious.
I have also checked the network connection center in Win 7. Negative.
--
I have started to believe that there may be some components in Windows
itself that are not installed.
Any good advice is appreciated

Kind regards
TorB.

-----


On 2012-01-20 04:06:57 +0000, Raul said:

> TorB,
>
> So it's still somewhat inconclusive if we'er connecting to EWB or
> something else is intercepting this.
>
> If you're up for more experimentation then this is what i would try next :
>
> 1. If you leave the TCPView program running and sorted by "Local Port"
> column it will actually show the new telnet session as you execute
> telnet connection. It would highlighted by green for a seconds.
> Basically see if you see 2 lines for webbuilder after you've run the
> telnet but before you type anything else.
>
> 2. Did you try doing the telnet with 127.0.0.1 address (instead of
> localhost) so type telnet 127.0.0.1 80 and then proceed as before.
>
> Raul
>
> <<Hi Raul.
> But when I run the command GET / HTTP/1.1 and hit ENTER twice the
> telnet program exits and I am back on the command prompt again. :-/

Hi Tor

Try using Fiddler - it's a standard (free) http diagnostic tool
http://www.fiddler2.com/

This article discusses its use with localhost

http://www.codinghorror.com/blog/2006/05/localhost-http-debugging-with-fiddler.html

Cheers, Bob

Tor J M Breines wrote:

Hi Raul.
I have done as you adviced
I have tried both the name 'localhost' and the localhost ip address
127.0.0.1, same problem.
In TCPView I see another process starting when running the command
TELNET LOCALHOST 80.
This is a process on http port with state ESTABLISHED which should be normal.
--
I then execute the GET / HTTP/1.1 command, which by the way is not
echoed on the screen, I only see the cursor moving when typing the
command. After hitting ENTER twice, the process goes yellow for a short
time and then changes to a system process with state TIME_Wait. In the
command window I can see that the GET command exits and I am then back
on the command prompt again.
--
My Windows is a Parallells Desktop 7 virtual Windows on a MacBookPro. I
have also checked the options in Parallells to see if there is
something there which is blocking the connection. Nothing obvious.
I have also checked the network connection center in Win 7. Negative.
--
I have started to believe that there may be some components in Windows
itself that are not installed.
Any good advice is appreciated

Kind regards
TorB.

-----


On 2012-01-20 04:06:57 +0000, Raul said:

> TorB,
>
> So it's still somewhat inconclusive if we'er connecting to EWB or
> something else is intercepting this.
>
> If you're up for more experimentation then this is what i would try next :
>
> 1. If you leave the TCPView program running and sorted by "Local Port"
> column it will actually show the new telnet session as you execute
> telnet connection. It would highlighted by green for a seconds.
> Basically see if you see 2 lines for webbuilder after you've run the
> telnet but before you type anything else.
>
> 2. Did you try doing the telnet with 127.0.0.1 address (instead of
> localhost) so type telnet 127.0.0.1 80 and then proceed as before.
>
> Raul
>
> <<Hi Raul.
> But when I run the command GET / HTTP/1.1 and hit ENTER twice the
> telnet program exits and I am back on the command prompt again. :-/




Hola, perdona que escriba en español, a mi me pasa exactamente lo mismo, lo que he hecho ha sido instalar el IIS de windows 7 y entro en EWB con el servidor inactivo, me funciona ahora perfectamente, me ejecuta mediante el servidor de windows y tengo desactivado el de EWB. Saludos

Hi fdez.
I see the same effect here. I have not installed IIS, but if I stop the
EWB web server, the appliation runs.
Kind regards
TorB.

On 2012-01-20 17:46:50 +0000, fdez said:

Hi Bob.
I must admit that some times I feel like an idiot.
I had run out of good ideas and decided to install the dotNET package
3.5.1 in adition to the dotNET v. 4 package that was already installed.
And now I can not start the EWB web server at all.
I now get this message: The web server can not be started (Socket
error: ….. (100013) on API 'bind' ).
But with the web server stopped I can now run the application. I now
see the complete file path in the title line of the browser.
This is like it was in the first version og EWB.
Still looking for a solution
Kind regards
TorB.

----

On 2012-01-20 09:37:39 +0000, Bob Devine said:

> Hi Tor
>
> Try using Fiddler - it's a standard (free) http diagnostic tool
> http://www.fiddler2.com/
>
> This article discusses its use with localhost
>
> http://www.codinghorror.com/blog/2006/05/localhost-http-debugging-with-fiddler.html
>
>
> Cheers, Bob

Hi Tor

Close EWB, open a command window and type the following at the prompt:

netstat -an |find /i "listening"

You'll get a list of open ports and this will tell you if you've already
got a process listening on port 80.

Cheers, Bob

Hi Bob.
Thanks for helping.
Here is the first lines of the netstat status.
I do not understand this, but it seems to be another process using port 80.
Kind regards
TorB.
"
C:\Windows\system32>netstat -an |find /i "listening"
 TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
 TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
 TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
 TCP    0.0.0.0:554            0.0.0.0:0              LISTENING
 TCP    0.0.0.0:2508           0.0.0.0:0              LISTENING
"
-----

On 2012-01-20 19:47:45 +0000, Bob Devine said:

> Hi Tor
>
> Close EWB, open a command window and type the following at the prompt:
>
> netstat -an |find /i "listening"
>
> You'll get a list of open ports and this will tell you if you've
> already got a process listening on port 80.
>
> Cheers, Bob

Yes there's something there - obvious possibilities are IIS or Skype.
Instead of '-an' use '-ao' in the netstat query:

netstat -ao |find /i "listening"

In the list you'll see the PID. Open task manager, go to View and select
PID as one of the visible columns. Look in the list of processes for the
PID seen in netstat and that'll be your culprit.

Cheers, Bob


On 20/01/2012 19:58, Tor J M Breines wrote:
> Hi Bob.
> Thanks for helping.
> Here is the first lines of the netstat status.
> I do not understand this, but it seems to be another process using port 80.
> Kind regards
> TorB.
> "
> C:\Windows\system32>netstat -an |find /i "listening"
> TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
> TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
> TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
> TCP 0.0.0.0:554 0.0.0.0:0 LISTENING
> TCP 0.0.0.0:2508 0.0.0.0:0 LISTENING
> "
> -----
>
> On 2012-01-20 19:47:45 +0000, Bob Devine said:
>
>> Hi Tor
>>
>> Close EWB, open a command window and type the following at the prompt:
>>
>> netstat -an |find /i "listening"
>>
>> You'll get a list of open ports and this will tell you if you've
>> already got a process listening on port 80.
>>
>> Cheers, Bob
>
>

Or just use the TCPView utility referenced earlier in the thread that you you already have - it'll show you the executable involved etc.

Raul

<<
Instead of '-an' use '-ao' in the netstat query:

netstat -ao |find /i "listening"

In the list you'll see the PID. Open task manager, go to View and select
PID as one of the visible columns. Look in the list of processes for the
PID seen in netstat and that'll be your culprit.
>>