Forum Replies Created
-
Posts
-
The IGMP protocol is a prerequisite for routers to learn which directly connected hosts are interested in a particular multicast group. I doubt IGMP is in Zeroshell’s protocol suite.
In this day and age, rebooting fixes most problems. Anytime you call into a support center for troubleshooting a device 9/10 times they ask you to reboot the device first. When you build a multi-vendor network just as you have in your situation, they don’t always play nice together and rebooting them sometimes gets them to sync up and cooperate. I’m sure there is a specific technical reason why your setup wasn’t working temporarily.
I think there is a cleaner way to do it but this should make it work regardless.
Try Firewall/Input Chain/Add
SourceIP: (The IP of the box that will be connecting to the server (RDP client))
DestinationIP: IP of the server
Protocol Matching: TCP, destination port 3389
Push the “confirm” buttonNow add another firewall rule
Source IP: 0.0.0.0/0
Destination IP: IP of the server
Protocol Matching: TCP, destination port 3389
Change Action from ACCEPT to DROP
Push the “confirm” buttonMake sure you save the changes
Man learn how to search! 🙂
http://www.zeroshell.net/eng/forum/viewtopic.php?t=582
Or should be able to add other lines like:
nameserver 24.204.0.5
in the resolv.conf file.
even simpler reference:
http://www.cyberciti.biz/tips/linux-how-to-setup-as-dns-client.htmlWould try disabling any wireless security first. If you have everything on the same network then the DHCP broadcasts can reach every device.
The only difference between this setup working and not working is whether you are plugged in wireless or wired. I’ve seen where if you enter in the wrong WEP key a windows client will say “Limited or no connectivity” and give you a 169.x.x.x address.
