Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hey all, I've installed a couple of Linux servers here at my work. They're basically just file repositories at this time but hey, they run Linux and they're problem free. Until now. We were almost out of IP addresses so I moved us from one big subnet to three subnets: 1.xxx, 2.xxx and 3.xxx. All of my workstations are in the 1.xxx or the 3.xxx subnets, all of my servers are in the 2.xxx subnet and we're all separated by a Fortigate router. If I set my workstation address to 2.xxx I can get into everything, but if I set my workstation address to 1.xxx I can get into everything except my Debian 6 server. I can ping the server, I can run NMAP on it and see all of the ports but I can't ssh into it or access it from a web browser. If I change back to a 2.xxx address I can do all of these things. Does my Debian server have some kind of ACL list running on it? I didn't set up anything like that that I know of but I'm still kind of new to Linux.
Hi chrism01, here's the output of your iptables code:
root@BigDeb:/home/jobee# iptables -nvL
Chain INPUT (policy ACCEPT 276 packets, 42817 bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 117 packets, 28661 bytes)
pkts bytes target prot opt in out source destination
root@BigDeb:/home/jobee#
I don't have any idea what any of this means but I'm guessing that since nothing is listed under what I believe to be column headings my problem isn't being caused by iptables. Do you see anything here?
So there aren't any Access Control Lists that could be automatically configured for current subnet access? I can't find anything that's blocking access. It's for sure not a routing issue because I can access a CentOS server that's plugged into the same switch. Any one have any guesses for something to look into???
Chrism01, I added the following line to hosts.allow (it was blank, and it WAS under /etc) but it didn't help:
ALL : 192.168.1.0/255.255.255.0 \
I checked the hosts.deny file and it was blank. I uncommented the ListenAddress 0.0.0.0 line but that didn't help either. Any other ideas? Anyone else?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.