I am trying to install and configure TFS Server on Windows 2012 AWS EC2 instance. I will like to configure an RDS SQL Server as backend but I am facing some issues with the connection so I am testing the ports and the connection using this command:
Test-NetConnection -Port 1433 -ComputerName tfsserver.sqlserver.region.rds.amazonaws.com -InformationLevel Detailed
And the command result is:
ComputerName : tfsserver.sqlserver.region.rds.amazonaws.com
RemoteAddress : sql_server_address
RemotePort : 1433
AllNameResolutionResults : sql_server_address
MatchingIPsecRules :
NetworkIsolationContext : Internet
InterfaceAlias : Ethernet
SourceAddress : tfs_server_address
NetRoute (NextHop) : gateway_hop_address
PingSucceeded : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded : False
Note: I changed originals IP address and RDS endpoint name
My issue here is:
The ping command is not allowed in my security group so how do I know if the connection is open because:
TcpTestSucceeded : False
Is that result related with the ping command or is the 1433 port closed? I will like to know if the connection is open.
That is a result of the tcp port not being accessible. Either as it's not open, its not allowed somewhere along the path (local firewall, route or RDS security group)
If you specify the -Port parameter then it's a TCP test not an ICMP echo (ping) https://technet.microsoft.com/en-us/library/dn372891.aspx
Related
I am trying to connect to open up port 89 on my Windows machine so others can access it, but I'm having trouble doing so. I added a rule to Firewall to allow access to port 89, but it still seems like it's not working. Any advice on how to resolve or even how to debug?
PS D:\> Test-NetConnection devbox -p 89
WARNING: TCP connect to (fe80::188d:3b90:868b:c3f6%5 : 89) failed WARNING: TCP connect to (2001:4898:3:25:7975:d61e:f88e:bfe2 : 89) failed WARNING: TCP connect to (2001:4898:3:25:188d:3b90:868b:c3f6 : 89) failed WARNING: TCP connect to (fe80::4c9e:1380:c530:b43a%42 : 89) failed WARNING: TCP connect to (fe80::6d77:dd66:a5b1:902c%26 : 89) failed WARNING: TCP connect to (fe80::69d3:4282:2917:485d%18 : 89) failed WARNING: TCP connect to (fe80::c9a:5dbc:5823:fdd9%13 : 89) failed WARNING: TCP connect to (10.123.77.38 : 89) failed WARNING: TCP connect to (172.24.96.1 : 89) failed WARNING: TCP connect to (172.24.48.1 : 89) failed WARNING: TCP connect to (172.21.128.1 : 89) failed WARNING: TCP connect to (2001:0:d5b:9458:c9a:5dbc:5823:fdd9 : 89) failed ComputerName : devbox RemoteAddress : fe80::188d:3b90:868b:c3f6%5 RemotePort : 89
InterfaceAlias : vEthernet (New Virtual Switch)
SourceAddress : 2001:4898:3:25:188d:3b90:868b:c3f6
PingSucceeded : True
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded : False
Be sure that you or your friend exactly do this:
Navigate to Control Panel, System and Security and Windows Firewall.
Select Advanced settings and highlight Inbound Rules in the left pane.
Right click Inbound Rules and select New Rule.
Add the port you need to open and click Next.
Add the protocol (TCP or UDP) and the port number into the next window and click Next.
Select Allow the connection in the next window and hit Next.
Select the network type as you see fit and click Next.
Name the rule something meaningful and click Finish.
That's all you have to do to open a firewall port in Windows 10
Many devices have open ports to send error reports to a server. But
the things is those devices are their to send and then recieve
acknowledgement to the sent packet. So what you need is a device to
recieve and then send to. To overcome this problem, you need to become
that server which the device request/send to and recieve the service
from it. You can send a .bat file to a friend/ victim laptop which cab
change its dns and gateway address to your server which you will be
running ,hence Becoming the middle man.(just an example)
Client tries to connect to IPv6 address: TCP connect to (fe80::188d:3b90:868b:c3f6%5 : 89) failed.
Maybe your server is listening only IPv4.
Also the problem may come from trying to connect to an IPv6 address instead of the IPv4 address that you are listening to. Instead, you can try entering the IPv4 address, 10.3.10.200, as the "ComputerName" to restrict the test to IPv4.
Notify me if this works for you.
So i am trying to run Selenium tests written in Java through Eclipse on my guest machine.
My host machine is Windows 7 and I am running Windows 7 guest machine. I have set 2 network adapter NAT and Host only. I am farily new to the whole Selenium testing so I am still exploring all the stuff.
I already run hub and node on my guest with next commands:
java -jar selenium-2.39/selenium-server-standalone-2.39.0.jar -role hub -port 4444 -host 192.168.56.1
and node with:
java -jar selenium-2.39/selenium-server-standalone-2.39.0.jar -role node -port 5555 -hub http://10.0.2.15:4444/grid/register -browser "browserName=internet explorer,version=11,platform=WINDOWS" -host 192.168.56.1
from Eclipse i am trying to access hub on http://192.168.56.1:5555/wd/hub and http://192.168.56.1:4444/wd/hub but in both cases i get an error:
org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.45.0', revision: '32a636c', time: '2015-03-05 22:01:35'
System info: host: 'xxxxx', ip: '192.168.xxx.xxx', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_31'
...
I do not know if I am using the correct IP addresses in both cases, if i go into my browser on guest machine i can access the console from hub
Thank you in advance.
OK.
So after long playing with the setting I finaly made this working. First thing is I disabled the Host-Only networking and left only NAT and I've set up a port 4444 forwarding from my host (127.0.0.1) to guest (10.0.2.15).
I've run hub with
java -jar selenium-2.39/selenium-server-standalone-2.39.0.jar -role hub
And node with
java -jar selenium-2.39/selenium-server-standalone-2.39.0.jar -role node -port 5555 -hub http://localhost:4444/grid/register -browser "browserName=iexplorer,version=11,platform=WINDOWS" -Dwebdriver.ie.driver=selenium-2.39/IEDriverServer.exe
Later on in Eclipse under Debug Configurations under Environment tab i set new property (notice: it is custom property in this case)
xx.xxxxxxxxxxxxxxx.selenium.properties.remoteUrl with value http://localhost:4444/wd/hub
After running tests I could reach my remote hub.
When I run the following command, I can get successfull result.
root#ubuntu:/home/can# radtest user password 127.0.0.1 1812 testing123
Sending Access-Request of id 78 to 127.0.0.1 port 1812
User-Name = "user"
User-Password = "password"
NAS-IP-Address = 127.0.1.1
NAS-Port = 1812
Message-Authenticator = 0x00000000000000000000000000000000
rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=78, length=20
However When I run the "freeradius -X" , I get error message as following :
.....
Failed binding to authentication address * port 1812: Address already in use
/etc/freeradius/radiusd.conf[250]: Error binding to port for 0.0.0.0 port 1812
Please Help Me
Thank you for your efforts.
Can
radiusd is already running. sudo service freeradius stop will stop it, and allow freeradius -X to bind to the address/port that was previously used by the RADIUS daemon.
Run 'service freeradius restart' and 'service freeradius stop' commands
Then run the command,'freeradius -X'
you will not face binding issue anymore.
Even having finished the service, there were pending zombie process.
Searching for a zumbi process I´ve found one:
[root#localhost sites-enabled]# ps aux | grep radi
radiusd 25042 0.0 0.7 186360 14980 ? Ssl Fev17 0:00 /usr/sbin/radiusd -d /etc/raddb
[root#localhost sites-enabled]# kill -9 25042
Service was start sucessfully after this.
Basically the port freeradius is looking to use is already in use by another background running instance of freeradius. Ending the first instance of freeradius will allow you to use that same port for the newly run instance.
I am attempting to set up a new quality of service for VoIP on windows 8.1. As I do not have Pro the "gpedit.msc" is unavailable so I am utilizing Windows Power Shell to create a Quality of Service Policy with the New-NetQosPolicy parameter. Unfortunately the traffic is still populating as the default O through WireShark. I have tried disabling the entire firewall and simply allowing the softphone through all 3 levels of the firewall to no avail. My policies are below, while they are both successfully set they are not working.
NOTE: This is a physical machine, not virtual.
New-NetQosPolicy -Name "Line of Business VOICE" -AppPathNameMatchCondition "%ProgramFiles(x86)%\VoIPphone.exe" -DSCPAction 46 -IPProtocolMatchCondition UDP -IPSrcPortEndMatchCondition 20000 -IPSrcPortStartMatchCondition 10000 -PolicyStore "MY-PC" -UserMatchCondition "Me"
New-NetQosPolicy -Name "Line of Business SIP" -AppPathNameMatchCondition "%ProgramFiles(x86)%\VoIPphone.exe" -DSCPAction 24 -IPProtocolMatchCondition UDP -IPSrcPortMatchCondition 5060 -PolicyStore "MY-PC" -UserMatchCondition "Me"
Maybe change out the %ProgramFiles(x86)% for ${env:ProgramFiles(x86)}?
I'm Using Sphinx 2.0.5-release On both Server .
Both Server have same indexers.I have Searchd running on both server . But I would like
to fetch Data of Server 1 from Server 2.
I used this particular code :
$cl = new SphinxClient;
$cl->SetServer(remote_sphinx_server,9312); (remote_sphinx_server : IP address of 2nd
Server)
$cl->SetMatchMode(SPH_MATCH_EXTENDED);
$result = $cl->Query("","$indexer");
But I Don't get any response .
Im getting error : connection to "Server 2 IP:9312" failed (errno=113, msg=No route to
host)
If i Use below code :
$cl = new SphinxClient;
$cl->SetMatchMode(SPH_MATCH_EXTENDED);
$result = $cl->Query("","$indexer");
I get proper response. As the data is coming from local Sphinx .
What can be the problem fetching data from remote Server ? Any Help is very much
appreciated .
Thank you
you may have multiple network interfaces on server 2 and you are using one the IPs that is not reachable by server 1
check if firewall allows communication on port 9312
check if searchd does run on server 2. Also, by default, searchd opens the port on all available interfaces, unless specified. Check searchd.log if reports any error about opening the port(s).