One other thing though I just thought of...
How do programs such as locustworld (software to turn PC hardware into a
mesh wifi access point) manage connections using MACs?
I know someone that used to run locustworld, and he could block PC's by MAC
easily which included all ports, UDP, TCP, NetB etc.
Any ideas?
Jamie
"Jamie Dale" <j.dale@turboz.net> wrote in message
news:44d0c14d@newsgroups.borland.com...
> G'day Remy
>
> Yeah your answers make sense - I wasn't sure if it would be possible or
> not but I thought I would ask just incase you had some miracle answers.
>
> I'll stick with the firewall and the TCP server for the time being. I can
> get MAC address's using the IP address of the networked computer. This is
> for a private network only (using wifi) so it should be safe from the web.
>
> Just wanted to restrict it a bit though. I'll simply set the server to
> disconnect if the MAC isn't whitelisted.
>
> Thanks
>
> Jamie
>
> "Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
> news:44cfc967$1@newsgroups.borland.com...
>>
>> "Jamie Dale" <j.dale@turboz.net> wrote in message
>> news:44cf960b@newsgroups.borland.com...
>>
>>> IS there a way that I can stop a computer connecting to
>>> another computer on a LAN?
>>
>> No.
>>
>>> I want one computer to be a file server (of sorts) but I only want 1
>>> or 2 other computers to be able to connect to it.
>>
>> Then you should isolate the file server onto a private network that only
>> those 2 other machines have physical access to.
>>
>>> These will be identified by their LAN MAC address's.
>>
>> You cannot retreive the MAC address of a client. You will have to
>> identify
>> them by their IP address instead.
>>
>>> I know that using TIdTCPServer I could simply disconnect, BUT that
>>> would still allow the remote computer ping and a possible hack etc.
>>
>> That is what firewalls are for.
>>
>>> I want to make the Server physically ignore/discard all network traffic
>>> OR disconnect any computer that does not have an authorised MAC.
>>
>> Then you should physically isolate it to begin with, and not try to
>> handle
>> everything in code.
>>
>>
>> Gambit
