Is it possible to obtain the website's IP address that you are connecting to on a HTTPWebRequest session?
I'm looking to do this for an authentication check in a licensing class to prevent people from chainging their hosts.etc file and sending false replies to crack my software.
When retrieving URL via HttpWebRequest, can I see the IP address of the destination server?
Check out the thread about this might help you
Cheers
Truez
Above thread was correct, code used below:
For Each IP In Dns.GetHostEntry("website.com").AddressList
If IP.ToString() <> "websiteip" Then
MessageBox.Show("Not connecting to correct IP address")
Exit Sub
End If
Next
Related
When calling get broadcast object rest API, the RTMP Url in response shows private IP instead of public IP like below
"rtmpURL": "rtmp://172.58.0.1/LiveApp/test",
Is there anyway we can get public IP address?
Thank you for this question.
You can get the public IP by declaring globalIp
Please go to <AMS_DIR>/conf/red5.properties
i.e., /usr/local/antmedia/conf/red5.properties
Edit the properties file and Set useGlobalIp=true
save the settings
restart AMS with sudo service antmedia restart
Thank you
antmedia.io
I am serving my Rails 3 app on Heroku, my mail through Google, and the domain through Enom. This is for www.challengage.com
This works 95% of the time, however, once in a while, when someone tries to reply to an email I send them, it fails with the below error message because my email, josh#challengage.com, somehow got replaced with josh#herokuapp.challengage.com when they recieved it. I think it has something to do with Mail Delivery Subsystems, but I'm not sure. It also only seems to happen when emailing University professionals.
Error Message:
From: Mail Delivery Subsystem [mailto:MAILER-DAEMON#smtp2.syr.edu]
Sent: Monday, July 15, 2013 2:08 PM
To: David DiMaggio
Subject: Undeliverable: FW: Challengage - Work Team Simulation product for interviewing evaluations
Delivery has failed to these recipients or groups:
paul#challengage.herokuapp.com
The server has tried to deliver this message, without success, and has stopped trying. Please try sending this message again. If the problem continues, contact your helpdesk.
The following organization rejected your message: challengage.herokuapp.com.
Any ideas?
Thanks everyone.
This is almost certainly because you're using a CNAME for your email records.
Although most email servers will reflect the original domain when sending a message, others will replace it with the domain that's at the end of the CNAME.
This means that instead of sending to someone#challengage.com they send to someone#challengage.herokuapp.com instead.
The mail server sees the request to send to someone#challengage.herokuapp.com and decides that it doesn't look after challengage.herokuapp.com and so from it's perspective the message is rejected.
We used to see this issue with CloudMailin customers and started to recommend that they don't use CNAMES where email is involved and just make use of adding MX records direct to the Apex domain.
With Heroku this poses a problem though as you don't have a single IP that you can use to access their servers. We eventually ended up using Route 53 to host our domain, then adding an SSL endpoint (to get load balancer details) and then adding that load balancer to Route 53's Alias command so that it automatically always gave the correct results. Alternatively you can setup some sort of static IP based system on your apex domain to redirect.
I have a website running 2 WCF services. Working awesome until I needed to move them from the "Default Web Site" in IIS7 to a dedicated website with a new IP address. Now I get the error message:
"...could not be loaded because more than one endpoint configuration for that contract was found. Please indicate the preferred endpoint configuration section by name"
ALL I did was change:
net.tcp://localhost/...
TO:
net.tcp://10.1.2.204/...
I have changed every spot in my configs which once used localhost to specified IP address. The new website is setup exactly the same with the proper net.tcp bindings and it is bound to the single IP address of 10.1.2.204.
I cannot seem to figure out what is going on. I am looking at the svc trace logs and all I get is a bunch of the same.
My new website is called "core" whereas previously I was hosting on "Default Web Site". I added a new FQDN/public IP to route to this new site (backwards to the mentioned private IP address). Now my services are busted.
I know baseAddress is ignored when using IIS/WAS hosting, so I am not sure what else to check. I changed absolutely nothing else in the configs.
What else can I provide to help troubleshoot this?
--
I am also seeing this in the service trace viewer:
Activity Name Receive bytes on connection 'Listen at 'net.tcp://hole.myserver.com/...'.'.
...but the WCF services are actually hosted on that new "core" website which translates to my new private IP address. I have change FQDN names for the example. To make it clear:
I used to have 1 FQDN on this server using Default Web Site.
I now added a 2nd FQDN to this server, new website, second IP. It seems to me that the listening should be directed towards: net.tcp://core.myserver.com instead of net.tcp://hole.myserver.com. Let's pretend the server name is hole.myserver.com and my new website is core.myserver.com on the same server.
Hopefully this is not confusing and you can make sense of it.
I'm using the default net.tcp port of 808 and binding of 808:*
--
This is the first exception thrown that I can tell:
The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:00:10'.
--
None of these combos will activate the service and all produce the same exception:
net.tcp://localhost
net.tcp://localhost:808
net.tcp://10.1.2.204
net.tcp://10.1.2.204:808
even using a different port which I have done before without issue:
net.tcp://localhost:75
net.tcp://10.1.2.204:75
none of these work. :(
Thanks so much!
Its rights issue. Right click on your new website --> then Edit Permissions. On properties window click security tab and Edit button. Then Add IIS_IUSRS and give Read & Execute, List folder contents, Read permissions. Now iisreset and start to host and connect net tcp on new website.
When sending emails through our rails app they are going to spam in some email accounts(hotmail) and not coming at all in others.
We are using sendmail to send the emails. The sender email id is no-reply#xyz.com. What could be the possible reasons for this. Where do we check the logs for the sendmail(ubuntu).
Regards,
Pankaj
I think its with your SMTP mail server. if you can send the mail using like Gmail SMTP server you will overcome this prob !
check this list and see if your ip is in the list. Replace your 1.2.3.4 with your ip.
http://bgp.he.net/ip/1.2.3.4#_rbl
Check the full headers of the messages that are ending up in spam folders. The sendmail logs on your end won't tell you anything, unless the recipient's server is refusing your traffic at the SMTP level. Anti-spam software will often add header lines showing which tests failed -- maybe the IP address you're sending from is blacklisted or has a poor reputation; maybe there's something about the content that looks spammy.
One of our applications started erroring out and a result was that hundreds of error emails were being sent in matter of seconds. This got the email sender (seems to be just the from address, not the IP) banned. We use the IIS 6 SMTP server. This is the entry from the bad mail file:
Diagnostic-Code: smtp;553 sorry, your envelope sender is in my badmailfrom list (#5.7.1)
I would like to remove the email sender from the list, but I cannot find it. I search the web for the location, but I didn't turn up anything.
Any help on this would be appreciated.
Thanks,
Darren
The error although recorded on the server hosting IIS actually originated from our 3rd Party email host. The email address being used to send the email was actually blocked from the email host. Calling them and getting them to remove the email address from their block list resolved this issue.