I have ejabberd installed on my windows 7 machine .I created users using the web admin and clients are connecting fine.(I am using psi). I want for the users on other machines to be able to connect and even users with android clients.
I have modified the hosts file in
C:\Windows\System32\drivers\etc\hosts
like this:
127.0.0.1 domain.tz
192.168.0.161 domain.tz
192.168.0.161 is the ip address of the machine the server is installed on.I can ping it from other machines but when i try to connect a user with let say usr: user1#domain.tz pwd: passwrd it says the server can't be reached. What do I need to do to let clients connect successfuly to my ejabberd server?I apologize if this is basic but this is my first trial on xmpp server administration.
It was a problem with my own understanding with DNS .The domain name you set up when you set up your xmpp server should be an already existing ACCESSIBLE address on the network. I found the name of my pc simply by running the famous
ipconfig/all
on windows and used the host name value as my domain while setting up ejabberd.It usually even finds it by default.
NOTE: To reconfigure ejabberd ,I uninstalled it and deleted everything in the
C:\Users\myUserName\AppData\Roaming\ejabberd.
If i didn't do so ,the last settings of the server are not deleted and you can't create your new admin account.These are my findings on ejabberd so far and I hope it helps somebody some day.
Related
Environment (User):
Windows 10 laptop
AzureAD joined
User in the office
Side note: Majority of our users are domain joined, this user travels alot, so we set him up as AzureAD to see how it would work.
Environment (Network)
Firewall controls DHCP, routing, etc.
DNS is running on DC (windows server 2016); DNS = 192.168.1.10
DC is hosted in Azure (connected to on-prem via VPN to firewall)
Problem:
This user cant ping host (A) records on the DNS server. The user can ping the FQDN though. e.g. can not ping servername, can ping servername.internal.company.com
This is breaking a service this user needs to run.
All the machines settings for DNS are correctly set (getting pulled through from the firewall). It just seems like the azuread joined device is not able to authenticate to the DC/DNS to retrieve details about a host name, but I find it really weird it can get responses back when using the FQDN of the server?
Can anyone please suggest why this user is getting blocked? I am thinking that becasue this is an AzureAD user their is an authentication issue, any help on the matter is greatly appreciated.Thanks!
recently I have faced the same problem with azure windows VM I have tried all the best possible afford to resolve the issue, but not success finally I have to change the VM IP with azure login panel after restart internet is working.
I have the following setup in my DEV environment which is running on Windows 10 (which should be irrelevant).
Homestead with Virtual box to develop my Laravel applications
on my local OS I have a IBM Domino server running as dev1.mydomain.local
I'm trying to access the REST API on the Domino server from my Laravel installations. At the moment I'm getting 404 errors when trying because the domino server is not available from within the VirtualBox of Homestead.
Here is the network configuration of the homestead virtual box
Both webservers Domino and nginx on the virtual box are running on standard ports
Here is the ifconfig output of the virtual box
How can I make that possible?
UPDATE:
It just came to me that I am able to access the Domino server with LDAP, so perhaps changing the http and https port of the Domino server is already the answer...
I will test that and then get back here...
Changing the Port of the Domino server to 8080 enable me to access the server's REST API
dev1.mydomain.local:8080/api/data/
The connection to the local machine seems to be enable through the VirtualBox's second network adapter and the my call to the REST API got confused with the 2 web servers listening to the same port on localhost(127.0.0.1)
Update
although I was kind of able to connect to the server using the address above, still left me with the problem that authentication wasn't possible. In order to do so (and I have not the slightest idea why), I had to change to the local IP address of my PC to access the REST services
http://192.168.0.155:8080/api/data
If someone could explain that I would be happy :-)
I have a WI-FI & LAN network at office. I have all my files on my desktop computer (192.168.1.2) and want to access local host over there from another computer (192.168.1.8).
My xampp version is v3.2.2 and windows 7 64 bit.
On my desktop I can access localhost through the normal http://localhost. Apache is running on port 80 as usual.
Exactly what do I have to do to achieve this? There is documentation on the net but they either don't work me or are too old and confusing to understand.
Any ideas as to what changes to make it possible? Please give me step by step instructions.
User should have access of your localhost, you can check this by sharing the folder and check on other machine that folder is accessible or not, If it is accessible then that user easily can access your local host by using the http:/IPAddress, If not contact to IT department they will help to achieve this by removing some restriction on network.
I am able to access the link http://localhost/men/tops-men/jackets-men.html successfully from my VM (configured using X2Go client).
IP Address of the VM: 10.146.106.204
I am also able to ping the VM successfully from my host machine (Windows).
The page that I am trying to access is a php page deployed on Apache Web Server.
However I am not able to do so from my Windows host machine.
I tried http://10.146.106.204/men/tops-men/jackets-men.html from my Windows machine but it did not work.
Do I have to configure something on my host machine or on my VM ?
Not sure what I am missing.
On VM check you can view http://10.146.106.204/men/tops-men/jackets-men.html
If not you need to configure the web server to listen on that IP (if you're running IIS this is under "bindings" in the right-hand side panel of IIS Manager).
On Host open a cmd window and check you can ping 10.146.106.204
If not check your firewall settings on the VM.
If neither of these 2 things help then you need to add more information about your setup to the question. Those are 2 very simple things you can do to diagnose 2 basic problems you might be having.
I was finally able to solve the problem based on this SO link: Unable to access magento site from anywhere but localhost
Updated the DB table core_config_data and updated the data by replacing http://localhost with http://ip-of-vm and then restarted the apache web server.
So I have this issue. The issue is I am unable to connect to my red5 server from a remote client. I also have not found any tutorials on how to install red5 so that remote clients can connect to it. However, here is what I have done...
Inside My MXML Flex File I try to connect to the computers IP that the server is running on(My Server is running from within Eclipse). The line for connecting looks like this netConnection.connect(rtmp://192.168.2.12/myApp, true);
All that happens is after a lot of minutes go by, I just get NetConnection.Connect.Failed and there is no log being output by Eclipse. Almost like it never even registers the connection that the remote client is trying to make.
The other interesting thing is that I am ABLE to connect to my Red5 Server using a different computer within my local home network just fine. But only when it is remote I am unable to connect.
I have changed my Red5-web.properties file and added this...
webapp.contextPath=/myApp
webapp.virtualHosts=*, 127.0.0.1, localhost, 192.168.2.14, 174.122.104.3
The 174 one is my website where the Flex Swf Resides on.
I think maybe somehow my computer is not setup or configured to allow these remote connections and is rejecting them or something, I'm not quite sure why a remote client can't connect. Does anyone have any idas?
Your help is greatly appreciated.
You may uninstall the red5 and reinstall it.
When it ask you the server ip address type your server's LAN adress (192.168.2.* or 10.0.0.* whatever). This solved my problem.
In my opinion, if you have at least one domain name that you own, the best way for you to go is to set up an Apache Http Server to your server machine, and create subdomains for both red5, rtmp and rtmpt. Make the Apache handle your incoming requests, and decide their correct routing there.
In case you don't own a domain, or the previous way is too time-taking to set up and get it work, you should just make sure that the ip address you're trying to connect to is not an internal IP.
In your example above you are trying to connect from the client to a 192.168... address. If you try to connect to it from within your LAN, it works, since that ip there is registered to your machine.
But when you take your notebook to your neighbor, and using his internet connection to access your site and connect to red5, the client (flex application) will also try to connect to that 192.168..., and your neighbor's router has no idea about your LAN, probably it doesn't have such an internal IP address either, but SURELY cannot connect to your server.
So instead of using 192.168... in your connection string, you should try using your external IP address (the 174... one):
netConnection.connect("rtmp://174.122.104.3/myApp", true);
This will work always, as far as you have a static IP address.
Also make sure, that your red5 server is accessible over the 80 port, or if it's not, specify the correct port number there.
For that you can do following thing...
These steps I took and it's solved my problem...
1.During the installation, you must have given ip 127.0.0.1 (localhost) and port :5080
2.firstly open the port (5080 and 1935) on firewall.
Visit http://windows.microsoft.com/en-in/windows/open-port-windows-firewall#1TC=windows-7
3.Now to go red5->conf->red5.properties and open this file in notepad++. (or any other editor)
4.repalce http.host and rtmp.host ip with your ip address (ipv4)
5.start the red5 service.
6.Now check http://yourip:5080
It will start working, and you can access it from other system also (in the same network Obviously )