>Ping 127.0.0.1 is pinging yourself. 127.0.0.1 is a loopback address (as I said earlier) and all that does is send IP packets from the send of your network card to the receive of your network card. All it really does is test whether TCP/IP is installed correctly.

Ok. Clear here.

>If you try http://wsn_server, unless you have an entry in your local HOSTS file or your network is running WINS to resolve the PC name to an IP address, this probably won't work.

>From your server, go to a CMD prompt and type IPCONFIG. This will list your ethernet adapters with the associated IP address. Find the card connected to your network, and use it's IP address from your workstation PCs instead of the Windows name.

http://wsn_server/mywebapp (server name) or http://192.168.0.1/mywebapp (server IP address) returns the same error "Browser error, Browser sent a malformed request."

I can't figure it out why?

jb


>Ex.
>http://205.205.57.4
>
>>Joao,
>>
>>All in one answer to your posted messages:
>>
>>Ping 127.0.0.1 replies well whether in server or workstation.
>>
>>http://127.0.0.1 or http://localhost in workstation gets the info. of the workstation itself which returns error: "page can not be displayed" and displays "my computer" in the window bar status (it should be local intranet).
>>
>>http://wsn_server in workstation gives "browser error" but displays "local intranet" which is contrary to http://127.0.0.1 - "my computer".
>>
>>I already bypassed the proxy for local IP address.
>>
>>jb
>>
>>>Hi Jess
>>>
>>>How many networks cards have you in your server?
>>>
>>>One = no problem, more it could be a problem...
>>>
>>>João Batista