Homebrew Question Why won't my FTPD work?

[laramie]

still gives the same error. also where did 192.168.68.0 come from? since my switch is 192.168.68.115

I think he's linking wifi subnets

 

[TheRealMrBuushy]

you could just login to your modem/router and check in advanced settings?

can't do that tonight. it's not my router so I don't have the log in to it. I can do it in the morning if there is no other solution

 

[laramie]

can't do that tonight. it's not my router so I don't have the log in to it. I can do it in the morning if there is no other solution

well logging in was just to bypass the port scan tool.. You could just use nmap either online or running it. (online requires external IP)

 

[TheRealMrBuushy]

well logging in was just to bypass the port scan tool.. You could just use nmap either online or running it. (online requires external IP)

so do I just download it and run it?

 

[lwiz]

still gives the same error. also where did 192.168.68.0 come from? since my switch is 192.168.68.115

Kinda thought so, but too tired to get thinking about the route dilemma more properly. The 192.168.68.0 came from the Switch's IP your Switch is in subnet 192.168.68.0/24 (the 24 meaning that only last number/octet is meaningful for single machine, rest is subnet part)

Then your PC is in subnet 192.168.0.0/24. What would be ideal is:
a) Get them both on same subnet using same connection type
b) Change router settings to use only one subnet for connected devices (the WiFi and wired are both provided by the same router?)
c) Change routing setting so that the 192.168.68.0 subnet will be visible from 192.168.0.0 subnet

As the c) didn't work directly there would be need of examining network topology more closely with arp, traceroute and such tools, which might give information not best shared on public forum, so it's either a) or b) I'm afraid.

 

[laramie]

so do I just download it and run it?

yeah just run nmap IPADDRESS

 

[AlexMCS]

You have to troubleshoot the connection.
Portqry is very simple to use and does not need to be installed, unlike nmap.

 

[TheRealMrBuushy]

Kinda thought so, but too tired to get thinking about the route dilemma more properly. The 192.168.68.0 came from the Switch's IP your Switch is in subnet 192.168.68.0/24 (the 24 meaning that only last number/octet is meaningful for single machine, rest is subnet part)

Then your PC is in subnet 192.168.0.0/24. What would be ideal is:
a) Get them both on same subnet using same connection type
b) Change router settings to use only one subnet for connected devices (the WiFi and wired are both provided by the same router?)
c) Change routing setting so that the 192.168.68.0 subnet will be visible from 192.168.0.0 subnet

As the c) didn't work directly there would be need of examining network topology more closely with arp, traceroute and such tools, which might give information not best shared on public forum, so it's either a) or b) I'm afraid.

1) I have to applaud you because for someone who is tired, you have literally just said the biggest brain shit and I don't even understand a single part of it. 2) the Wifi and Wired connection are both connected to the same router, so would option B be the best? also, my PC internal IP is 192.168.0.34 incase I missed something

--------------------- MERGED ---------------------------

You have to troubleshoot the connection.
Portqry is very simple to use and does not need to be installed, unlike nmap.

well i currently have portqry opened. I don't know what to put for "destination ip" and what to choose/put for "query type"

 

[lwiz]

1) I have to applaud you because for someone who is tired, you have literally just said the biggest brain shit and I don't even understand a single part of it. 2) the Wifi and Wired connection are both connected to the same router, so would option B be the best? also, my PC internal IP is 192.168.0.34 incase I missed something

b) would be the best hoping the router has the option for using same subnet for wifi and wired

 

[AlexMCS]

Here, I'll try explaining it with pics:
Running FTPd 3.1.0 installed from the hbstore, just like you did.
My current private IP network is on the 10.100.0.0/16 range (meaning all IPs start with 10.100).

My switch got the IP 10.100.0.130, as it shows on the FTPd screen.

First test, ICMP Echo (ping). See if you can reach the switch at all:

With this, I know I can reach the switch.
Now I'll try to see if I can reach the FTPd port, using portqry:

Now you can see that the switch is accepting incoming connections on the FTPd port.

 

[TheRealMrBuushy]

yeah just run nmap IPADDRESS

what should i put for the "IPADDRESS" when i put "nmap" in CMD?

 

[AlexMCS]

Finally connecting using Winscp.
Here's the config I use:

Here's the result:

 

[laramie]

what should i put for the "IPADDRESS" when i put "nmap" in CMD?

switch IP

 

[TheRealMrBuushy]

Here, I'll try explaining it with pics:
Running FTPd 3.1.0 installed from the hbstore, just like you did.
My current private IP network is on the 10.100.0.0/16 range (meaning all IPs start with 10.100).

My switch got the IP 10.100.0.130, as it shows on the FTPd screen.

First test, ICMP Echo (ping). See if you can reach the switch at all:

View attachment 268324

With this, I know I can reach the switch.
Now I'll try to see if I can reach the FTPd port, using portqry:

View attachment 268325

Now you can see that the switch is accepting incoming connections on the FTPd port.

pinging my switch internal IP (192.168.68.115) just gives "Request timed out."

 

[TheRealMrBuushy]

what should i put for the "IPADDRESS" when i put "nmap" in CMD?

gave this:

C:\WINDOWS\system32>nmap 192.168.68.115
Starting Nmap 7.91 ( https://nmap.org ) at 2021-06-28 02:43 GMT Summer Time
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.20 seconds

 

[AlexMCS]

Then you have a firewall or other routing issue to solve first.

First, I think you should double check whether that's you actual switch's private IP, because rarely does one change the default private IP range from 192.168.0.0/24 to 192.168.68.0/24.

Does any other device, like a smartphone, connected to that same WiFi gets an IP starting with 192.168.68?
If it does, can you ping the switch from the phone (use Termux, cancel with CTRL+C)?

 

[laramie]

pinging my switch internal IP (192.168.68.115) just gives "Request timed out."

switch is having problems with network through some kind of redirection. It is either forwarded wrong or dns maybe vpn or some other means of hopping through servers/backtraces. Yeah switch is def blocking something
If you can make your switch a static IP not dynamic through router tomorrow.

 

[TheRealMrBuushy]

switch is having problems with network through some kind of redirection. It is either forwarded wrong or dns maybe vpn or some other means of hopping through servers/backtraces. Yeah switch is def blocking something
If you can make your switch a static IP not dynamic through router tomorrow.

will try and reply to you as soon as its done or tried. also with the nmap thing, i did the -pn thing it asked and got this:

Nmap scan report for 192.168.68.115
Host is up.
All 1000 scanned ports on 192.168.68.115 are filtered

Nmap done: 1 IP address (1 host up) scanned in 201.56 seconds

I don't know what it means though

 

[laramie]

will try and reply to you as soon as its done or tried. also with the nmap thing, i did the -pn thing it asked and got this:

Nmap scan report for 192.168.68.115
Host is up.
All 1000 scanned ports on 192.168.68.115 are filtered

Nmap done: 1 IP address (1 host up) scanned in 201.56 seconds

I don't know what it means though

it means some or all ports are being actively blocked like through a firewall which could be through pc or router

 

[AlexMCS]

will try and reply to you as soon as its done or tried. also with the nmap thing, i did the -pn thing it asked and got this:

Nmap scan report for 192.168.68.115
Host is up.
All 1000 scanned ports on 192.168.68.115 are filtered

Nmap done: 1 IP address (1 host up) scanned in 201.56 seconds

I don't know what it means though

Like I said, nmap is overkill for this.
It could also mean that the IP can't be reached at all, as ping timing out implies.
Just check the IP of other wireless devices on the same WiFi network and see if they are in the same range.

 

[TheRealMrBuushy]

Then you have a firewall or other routing issue to solve first.

First, I think you should double check whether that's you actual switch's private IP, because rarely does one change the default private IP range from 192.168.0.0/24 to 192.168.68.0/24.

Does any other device, like a smartphone, connected to that same WiFi gets an IP starting with 192.168.68?
If it does, can you ping the switch from the phone (use Termux, cancel with CTRL+C)?

my mobile phone ip address is 192.168.68.102. i installed termux and it seems to be pinging it if:
64 bytes from 192.168.68.115: (other stuff)
is pinging it

Edit: I canceled it and it said that all packets were transmitted and recieved