cancel
Showing results for 
Search instead for 
Did you mean: 

How does Finger actually work??

beskar
Grafter
Posts: 159
Registered: 24-08-2007

How does Finger actually work??

I'm having problems with 'Finger Postmaster@Autotturn.plus.net' and I'm wondering if - for it to work - it needs to havesome sort of access to the originating machine (for authorisation?)

I'm hoping to be able to just use the SMTP choice in MyEmail to forward mail to my Exchange Server (212.159.xxx.13Cool rather than have to faff around with MX records at present.

On analog I was getting mail fine (set it to issue TURN, which worked) but not on ADSL - and 'finger postmaster@autoturn.plus.net' does not appear to work.

What happens with 'finger postmaster@autoturn.plus.net' : When I run this in a command window, I get the following response:

[autoturn.force9.net]
finger: connect:: Host is unreachable

Pinging autoturn.plus.net works fine, by the way. (Comes back with ip addr: 212.159.3.9)

So - my mail is queuing up and not coming to me.

I'm using a dual NIC combo, with the external nic having a public ip of
212.159.xxx.138, connected to a router (no NAT involved) and thence on to
ADSL.

Externally I can telnet 212.159.xxx.138 25 no probs, and get a response to
HELO by the way.
I can also ping .136 -.139 (of which .137, .138 re usable) fine.

Thanks
(Web browsing is fine too, by the way)

p.s. these entries in my server ISA (web proxy/firewall) logs, by the way: Port 79 (Finger)IS open, i.e has packet filter configured. 192.168.16.2 is the internal ip of the server (.138 is the external ip)

2002-05-23 01:28:14 212.159.xxx.138 212.159.3.9 Tcp 5182 79 BLOCKED
212.159.98.138
2002-05-23 01:28:21 212.159.xxx.138 212.159.3.9 Tcp 5182 79 BLOCKED
212.159.98.138
2002-05-23 01:28:48 192.168.16.2 255.255.255.255 Udp 68 67 BLOCKED
212.159.98.138
2002-05-23 01:28:48 192.168.16.2 255.255.255.255 Udp 67 68 BLOCKED
212.159.98.138
2002-05-23 01:28:56 192.168.16.2 255.255.255.255 Udp 68 67 BLOCKED
212.159.98.138
2002-05-23 01:28:56 192.168.16.2 255.255.255.255 Udp 67 68 BLOCKED
212.159.98.138
2002-05-23 01:29:03 192.168.16.2 255.255.255.255 Udp 68 67 BLOCKED
212.159.98.138
2002-05-23 01:29:03 192.168.16.2 255.255.255.255 Udp 67 68 BLOCKED
212.159.98.138
2002-05-23 01:29:11 192.168.16.2 255.255.255.255 Udp 68 67 BLOCKED
212.159.98.138
2002-05-23 01:29:11 192.168.16.2 255.255.255.255 Udp 67 68 BLOCKED
212.159.xxx.138

2 REPLIES
beskar
Grafter
Posts: 159
Registered: 24-08-2007

RE: How does Finger actually work??

(just an update to this problem to save someone else from shooting themselves...)

The Finger problem now sorted - apparently a packet filter needs to be configured for port 79 - in Msoft ISA at least, the instructions are:

Outbound, tcp/ip, local port any, remote port fixed 79.

This eliminates the 'host unreachable' business and allows SMTP mail to dequeue.

(thanks to SF in the SBS NG for this solution)

Also, there may have been an issue with my IP info at PlusNET - they've reconfigured some MX records, and we wait in hope for the 2am refresh!


beskar
Grafter
Posts: 159
Registered: 24-08-2007

RE: How does Finger actually work??

And another one...

- I also asked around about how to put a script into Win2k Server to automate the Finger biz on reboot. Haven't tried this yet, but James from the SBS NG suggested the following:
---------------------------------------------------

Write a .cmd file containing the commands you need to run and then use the
Task Scheduler (in the Control Panel) to schedule it to run "When my
computer starts". You may need to get hold of sleep.exe from the Resource
Kit (it's definitely in the Windows 2000 Pro and 2000 Server kits, not sure
about the SBS one). You can use that to add a delay before your finger
command dequeues the SMTP mail. Your script might look like this:

rem first, wait for 60 seconds for everything to start properly
sleep 60
rem dequeue the mail
finger @autoturn.plus.net

---------------------------------------

HTH