Problems with DNS - http

Good afternoon in my timezone.
I am developing a web appp in J2EE.
This web app is called and access inside a sharepoint portal.
When i enter through the sharepoint portal i can access my application, using chrome developes tools i can see all the HTTP traffic, and i see that the browsers sends a request to the following server that is where my app is running serverprd.enterprisename.com.
But when i use the command line in my windows 7 , to ping the machine(server) , for example :
ping serverprd.enterprisename.com it returns me the following message:
"Ping request could not find host serverprd.enterprisename.com"
I am using a proxy.
Can anyone tells me why this happening ? Why through the browser i can access the server and the ping command does not find me the server ?
With the best regards.
Thanks in advance.

Your proxy server id the one who have an access to outside world. All http requests are sent to proxy server and proxy server does DNS lookup. In case of pin, your host have to do DNS lookup and this operation obviously now allowed ( firewall or so).

Related

IIS ASP.NET application responds to IP but not to domain name

I've got a problem with IIS. I got a ASP.NET application there running and I am able to connect to it from local network (http://192.168.100.121:12002/) and from outer network too (185.91.165.134:12002 , connecting via phone, because router doesn't support this feature).
The thing is when I try to connect via a domain name queue.laststep.eu, it says error: timed out.
I've asked my friend to tracert this domain name and it finished at the router the server is connected to, so I suppose DNS is configured properly.
Does anyone got an idea what may be blocking inbound traffic? (Firewall is off, ports on our primary router are forwarded...)
I am attaching a screenshot of the site bindings(got to put it on 3rd party server due to low reputation... https://imgur.com/a/hTvqivY)
Thank you for help!

'Invalid hostname' response from http.sys

We have web service running hosted on an OwinHttpListener (http.sys behind the scenes). Whenever we send requests to the app on the IP address, it responds with 'Invalid hostname'.
After much trawling of stack overflow and google, im not really any closer to a solution. The requests are getting through to http.sys, as i can see them in the HTTP error log. I can log onto the server in question and access the service locally (using localhost or 127.0.0.1) and i can use the server name to successfully get through, the only failure condition is using the servers IP address.
Ive tried the following:
Ensure the app is listening on all interfaces (http://+:8080)
Ensure IIS is not trying to use the port (it isnt)
Ensure windows firewall is configured to allow traffic on that port (it is)

Can't access IIS website from local IP

I have a .Net service hosted on IIS. The service was accessible from IP:Port/Service.asmx, until recently when I couldn't access it from IP or System name again but only from Localhost:port/Service.asmx. I have pinged the server and it is replying. I have also confirmed that the local ip is listening on port 80. Really I don't know what is wrong, I have been on this for so long.
That's a hard one. Things I'd try:
Rebooting system.
Set a breakpoint at the earliest part of the request pipeline to verify whether the request is making it into your .Net code
Make a browser request via IP for a static file like an image. Is that served? That lets you see if the server will respond for a request that likely isn't going through Asp.Net.

Published asp.net website not accessible in other system in same network

I have developed a asp.net website and published in a server.Whereas everything works perfectly in that server if i give browser from that IIS manager, and in server ( published system ) everything works perfect.But i need to access the same published application also in the other systems also ( which are connected in same network ). How is it possible..??
NOTE:
1. Used IIS 7.
When tried to connect from another system from same networ getting error as follows
The socket connection to 172.31.7.243 failed.
ErrorCode: 10060.A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 172.31.7.243:90
If Your are accessing Your application on Hosted Server like this then just replace
localhost with ipaddress of hosted server to access it over the network
[localhost]/MyProjectName
then like this:
[IPaddress_of_HostedServer]/MyProjectName
It is possible that the HTTP traffic on port 80 incoming from the local network is blocked.
You should check if ISA server is installed on your server and if so if HTTP traffic on port 80 is allowed or not. If it's blocked try to allow it for the local network ip range.
Edit: Or port 90 as your error code states, but why are you working on port 90?

About http post from desktop application

My q is whats can stop http post from desktop applications ?
e.g
i have a desktop application before it start it's ask users form some information
like a username ad Email ,,, and then take this information and post it on php webpage and php insert it into MySql Server any way the problem now is lets say like
6 of 16 download(s) are registered and the others not so whats can make http post not run correctly ?
Note :
Software tested on every windows os and runs ok
Software run with all anti viruses programs ok
Software add port throw windows firewall ok
So whats can make http post not run correctly ?
Regards
There are many things that could stop communication between your application, and your database.
If the client has a firewall that requires authorisation for outbound requests.
If the client has to connect via a proxy server, and you application is not proxy aware
If your website fails to process your request (perhaps, if the MySql server is too busy to allow connections, etc.)
So, consider an end user behind a WebSense proxy that additionally allows administrators to filter out unwanted traffic. If your application is not proxy server aware, it will fail to connect; If your application is proxy aware, and whatever WebSense category you fall into is filtered for that client, it will also fail to connect.

Resources