|
|
|
Od: |
"Lewis G Rosenthal" <os2-wireless_users@2rosenthals.com> |
Glava Izvorno E-sporo?ilo |
Zadeva: |
Re: [OS2Wireless]Re: OT: DNS Lookup tracing (was: Re: [OS2Wireless]Re: Any idea why there are so many sessions to port53? -crossposted) |
Datum: |
Fri, 09 Feb 2007 20:21:10 -0500 |
Za: |
OS/2 Wireless Users Mailing List <os2-wireless_users@2rosenthals.com> |
|
---|
"Processing mail..." meaning...what?
What do NAT sessions have to do with DNS requests? The fact is that you are behind a NAT firewall. All that is being said is that your machine is traversing a NAT to get to a DNS box and make a request. For a mail server, this is a regular thing. the only way I avoid all the internet traffic is that my NetWare server is running DNS, forwarding, and caching. So, the first time Hawking2 (my OS/2 mail server) looks for an address (or a reverse DNS lookup), it sends that request to Galileo (NetWare). Galileo looks to see if he has cached the info, and if not, makes the request upstream to one of the root servers, caches a copy, and sends the data back to Hawking2. The next time, the response is faster, as Galileo doesn't need to go beyond his own cache. Hawking2, however, will once again make the request, as he is not running any kind of DNS cache locally.
Here's a snippet for Hawking2's DNS traffic (note the time of each request):
20:17:09.440 5 DNR-024259(mail.queensbotanical.org) A-request
20:17:09.440 4 DNR-024259(mail.queensbotanical.org) A-request -> udp:[192.168.100.1]:53
20:17:09.440 5 DNR-024259(mail.queensbotanical.org) got 294 bytes from [192.168.100.1]:53: 5E C3 81 80 00 01 00 02 00 05 00 05 04 6D 61 69 6C 0F 71 75 65 65 6E 73 62 6F 74 61 6E 69 63 61 6C 03 6F 72 67 00 00 01 00 01 C0 0C 00 05 00 01 00 00 17 85 00 1A 04 71 62 67 31 0F 71 75 65 65 6E 73 62 6F 74
20:17:09.440 5 DNR-024259(mail.queensbotanical.org) A:OK
20:17:09.440 4 DNR-024259(mail.queensbotanical.org) A[1]: qbg1.queensbotanical.org=[64.105.127.170]
20:17:11.010 5 DNR-024260(146.248.9.216.IN-ADDR.ARPA) PTR-request
20:17:11.020 4 DNR-024260(146.248.9.216.IN-ADDR.ARPA) PTR-request -> udp:[192.168.100.1]:53
20:17:11.410 5 DNR-024260(146.248.9.216.IN-ADDR.ARPA) got 86 bytes from [192.168.100.1]:53: 5E C4 81 80 00 01 00 01 00 00 00 00 03 31 34 36 03 32 34 38 01 39 03 32 31 36 07 69 6E 2D 61 64 64 72 04 61 72 70 61 00 00 0C 00 01 C0 0C 00 0C 00 01 00 00 02 58 00 1E 06 62 64 61 32 32 36 03 62 69 73 02 6E
20:17:11.410 5 DNR-024260(146.248.9.216.IN-ADDR.ARPA) PTR:OK
20:17:11.410 4 DNR-024260(146.248.9.216.IN-ADDR.ARPA) PTR[0]: 146.248.9.216.in-addr.arpa -> bda226.bis.na.blackberry.com
20:17:27.400 5 DNR-024261(incoming.verizon.net) A-request
20:17:27.400 4 DNR-024261(incoming.verizon.net) A-request -> udp:[192.168.100.1]:53
20:17:27.400 5 DNR-024261(incoming.verizon.net) got 501 bytes from [192.168.100.1]:53: 5E C5 81 80 00 01 00 01 00 0D 00 0D 08 69 6E 63 6F 6D 69 6E 67 07 76 65 72 69 7A 6F 6E 03 6E 65 74 00 00 01 00 01 C0 0C 00 01 00 01 00 00 72 75 00 04 CE 2E E8 0A 03 4E 45 54 00 00 02 00 01 00 00 DB 6C 00 14 01 4C
20:17:27.400 5 DNR-024261(incoming.verizon.net) A:OK
20:17:27.400 4 DNR-024261(incoming.verizon.net) A[0]: incoming.verizon.net=[206.46.232.10]
20:17:28.400 5 DNR-024262(incoming.verizon.net) A-request
20:17:28.400 4 DNR-024262(incoming.verizon.net) A-request -> udp:[192.168.100.1]:53
20:17:28.400 5 DNR-024262(incoming.verizon.net) got 501 bytes from [192.168.100.1]:53: 5E C6 81 80 00 01 00 01 00 0D 00 0D 08 69 6E 63 6F 6D 69 6E 67 07 76 65 72 69 7A 6F 6E 03 6E 65 74 00 00 01 00 01 C0 0C 00 01 00 01 00 00 72 74 00 04 CE 2E E8 0A 03 4E 45 54 00 00 02 00 01 00 00 DB 6B 00 14 01 4C
20:17:28.400 5 DNR-024262(incoming.verizon.net) A:OK
20:17:28.400 4 DNR-024262(incoming.verizon.net) A[0]: incoming.verizon.net=[206.46.232.10]
20:17:32.710 5 DNR-024263(135.249.9.216.IN-ADDR.ARPA) PTR-request
20:17:32.710 4 DNR-024263(135.249.9.216.IN-ADDR.ARPA) PTR-request -> udp:[192.168.100.1]:53
20:17:33.050 5 DNR-024263(135.249.9.216.IN-ADDR.ARPA) got 86 bytes from [192.168.100.1]:53: 5E C7 81 80 00 01 00 01 00 00 00 00 03 31 33 35 03 32 34 39 01 39 03 32 31 36 07 69 6E 2D 61 64 64 72 04 61 72 70 61 00 00 0C 00 01 C0 0C 00 0C 00 01 00 00 02 58 00 1E 06 62 64 61 31 33 35 03 62 69 73 02 6E
20:17:33.050 5 DNR-024263(135.249.9.216.IN-ADDR.ARPA) PTR:OK
20:17:33.050 4 DNR-024263(135.249.9.216.IN-ADDR.ARPA) PTR[0]: 135.249.9.216.in-addr.arpa -> bda135.bis.na.blackberry.com
20:17:33.500 5 DNR-024264(168.196.208.63.IN-ADDR.ARPA) PTR-request
20:17:33.500 4 DNR-024264(168.196.208.63.IN-ADDR.ARPA) PTR-request -> udp:[192.168.100.1]:53
20:17:33.500 5 DNR-024264(168.196.208.63.IN-ADDR.ARPA) got 497 bytes from [192.168.100.1]:53: 5E C8 81 80 00 01 00 01 00 0C 00 0D 03 31 36 38 03 31 39 36 03 32 30 38 02 36 33 07 49 4E 2D 41 44 44 52 04 41 52 50 41 00 00 0C 00 01 C0 0C 00 0C 00 01 00 00 75 2A 00 14 06 6D 78 6F 75 74 34 07 6D 61 69
20:17:33.500 5 DNR-024264(168.196.208.63.IN-ADDR.ARPA) PTR:OK
20:17:33.500 4 DNR-024264(168.196.208.63.IN-ADDR.ARPA) PTR[0]: 168.196.208.63.IN-ADDR.ARPA -> mxout4.mailhop.org
20:17:33.500 5 DNR-024265(168.196.208.63.xbl.spamhaus.org) A-request
20:17:33.500 4 DNR-024265(168.196.208.63.xbl.spamhaus.org) A-request -> udp:[192.168.100.1]:53
20:17:33.500 5 DNR-024265(168.196.208.63.xbl.spamhaus.org) got 129 bytes from [192.168.100.1]:53: 5E C9 85 83 00 01 00 00 00 01 00 00 03 31 36 38 03 31 39 36 03 32 30 38 02 36 33 03 78 62 6C 08 73 70 61 6D 68 61 75 73 03 6F 72 67 00 00 01 00 01 03 78 62 6C 08 73 70 61 6D 68 61 75 73 03 6F 72 67 00
20:17:33.500 4 DNR-024265(168.196.208.63.xbl.spamhaus.org) A:host name is unknown
20:17:33.500 5 DNR-024266(168.196.208.63.sbl.spamhaus.org) A-request
20:17:33.500 4 DNR-024266(168.196.208.63.sbl.spamhaus.org) A-request -> udp:[192.168.100.1]:53
20:17:33.500 5 DNR-024266(168.196.208.63.sbl.spamhaus.org) got 129 bytes from [192.168.100.1]:53: 5E CA 85 83 00 01 00 00 00 01 00 00 03 31 36 38 03 31 39 36 03 32 30 38 02 36 33 03 73 62 6C 08 73 70 61 6D 68 61 75 73 03 6F 72 67 00 00 01 00 01 03 73 62 6C 08 73 70 61 6D 68 61 75 73 03 6F 72 67 00
20:17:33.500 4 DNR-024266(168.196.208.63.sbl.spamhaus.org) A:host name is unknown
20:17:33.540 5 DNR-024267(mxout4.mailhop.org) A-request
20:17:33.540 4 DNR-024267(mxout4.mailhop.org) A-request -> udp:[192.168.100.1]:53
20:17:33.540 5 DNR-024267(mxout4.mailhop.org) got 372 bytes from [192.168.100.1]:53: 5E CB 81 80 00 01 00 01 00 06 00 08 06 6D 78 6F 75 74 34 07 6D 61 69 6C 68 6F 70 03 6F 72 67 00 00 01 00 01 C0 0C 00 01 00 01 00 00 6E 66 00 04 3F D0 C4 A8 03 4F 52 47 00 00 02 00 01 00 00 89 C4 00 13 04 54 4C 44
20:17:33.540 5 DNR-024267(mxout4.mailhop.org) A:OK
20:17:33.540 4 DNR-024267(mxout4.mailhop.org) A[0]: mxout4.mailhop.org=[63.208.196.168]
20:17:33.570 5 DNR-024268(mtu-net.ru) MX-request
20:17:33.570 4 DNR-024268(mtu-net.ru) MX-request -> udp:[192.168.100.1]:53
20:17:33.620 5 DNR-024268(mtu-net.ru) got 52 bytes from [192.168.100.1]:53: 5E CC 81 80 00 01 00 01 00 00 00 00 07 6D 74 75 2D 6E 65 74 02 72 75 00 00 0F 00 01 C0 0C 00 0F 00 01 00 00 00 82 00 0C 00 0A 03 6D 78 30 03 6D 74 75 C0 14
20:17:33.620 5 DNR-024268(mtu-net.ru) MX:OK
20:17:33.620 4 DNR-024268(mtu-net.ru) MX[0]: mtu-net.ru(pty 10) = mx0.mtu.ru
20:17:33.620 5 DNR-024269(mx0.mtu.ru) A-request
20:17:33.620 4 DNR-024269(mx0.mtu.ru) A-request -> udp:[192.168.100.1]:53
20:17:33.650 5 DNR-024269(mx0.mtu.ru) got 44 bytes from [192.168.100.1]:53: 5E CD 81 80 00 01 00 01 00 00 00 00 03 6D 78 30 03 6D 74 75 02 72 75 00 00 01 00 01 C0 0C 00 01 00 01 00 00 00 9B 00 04 C3 22 20 FE
20:17:33.650 5 DNR-024269(mx0.mtu.ru) A:OK
20:17:33.650 4 DNR-024269(mx0.mtu.ru) A[0]: mx0.mtu.ru=[195.34.32.254]
20:17:33.760 5 DNR-024270(127.219.168.68.IN-ADDR.ARPA) PTR-request
20:17:33.760 4 DNR-024270(127.219.168.68.IN-ADDR.ARPA) PTR-request -> udp:[192.168.100.1]:53
20:17:33.760 5 DNR-024270(127.219.168.68.IN-ADDR.ARPA) got 371 bytes from [192.168.100.1]:53: 5E CE 81 80 00 01 00 01 00 07 00 07 03 31 32 37 03 32 31 39 03 31 36 38 02 36 38 07 49 4E 2D 41 44 44 52 04 41 52 50 41 00 00 0C 00 01 C0 0C 00 0C 00 01 00 00 8B A5 00 24 0E 36 38 2D 31 36 38 2D 32 31 39
20:17:33.760 5 DNR-024270(127.219.168.68.IN-ADDR.ARPA) PTR:OK
20:17:33.760 4 DNR-024270(127.219.168.68.IN-ADDR.ARPA) PTR[0]: 127.219.168.68.IN-ADDR.ARPA -> 68-168-219-127.atlsfl.adelphia.net
20:17:34.430 5 DNR-024271(168.196.208.63.IN-ADDR.ARPA) PTR-request
20:17:34.430 4 DNR-024271(168.196.208.63.IN-ADDR.ARPA) PTR-request -> udp:[192.168.100.1]:53
20:17:34.430 5 DNR-024271(168.196.208.63.IN-ADDR.ARPA) got 497 bytes from [192.168.100.1]:53: 5E CF 81 80 00 01 00 01 00 0C 00 0D 03 31 36 38 03 31 39 36 03 32 30 38 02 36 33 07 49 4E 2D 41 44 44 52 04 41 52 50 41 00 00 0C 00 01 C0 0C 00 0C 00 01 00 00 75 29 00 14 06 6D 78 6F 75 74 34 07 6D 61 69
20:17:34.430 5 DNR-024271(168.196.208.63.IN-ADDR.ARPA) PTR:OK
20:17:34.430 4 DNR-024271(168.196.208.63.IN-ADDR.ARPA) PTR[0]: 168.196.208.63.IN-ADDR.ARPA -> mxout4.mailhop.org
20:17:34.430 5 DNR-024272(168.196.208.63.xbl.spamhaus.org) A-request
20:17:34.430 4 DNR-024272(168.196.208.63.xbl.spamhaus.org) A-request -> udp:[192.168.100.1]:53
20:17:34.430 5 DNR-024272(168.196.208.63.xbl.spamhaus.org) got 129 bytes from [192.168.100.1]:53: 5E D0 85 83 00 01 00 00 00 01 00 00 03 31 36 38 03 31 39 36 03 32 30 38 02 36 33 03 78 62 6C 08 73 70 61 6D 68 61 75 73 03 6F 72 67 00 00 01 00 01 03 78 62 6C 08 73 70 61 6D 68 61 75 73 03 6F 72 67 00
20:17:34.430 4 DNR-024272(168.196.208.63.xbl.spamhaus.org) A:host name is unknown
20:17:34.430 5 DNR-024273(168.196.208.63.sbl.spamhaus.org) A-request
20:17:34.430 4 DNR-024273(168.196.208.63.sbl.spamhaus.org) A-request -> udp:[192.168.100.1]:53
20:17:34.430 5 DNR-024273(168.196.208.63.sbl.spamhaus.org) got 129 bytes from [192.168.100.1]:53: 5E D1 85 83 00 01 00 00 00 01 00 00 03 31 36 38 03 31 39 36 03 32 30 38 02 36 33 03 73 62 6C 08 73 70 61 6D 68 61 75 73 03 6F 72 67 00 00 01 00 01 03 73 62 6C 08 73 70 61 6D 68 61 75 73 03 6F 72 67 00
20:17:34.430 4 DNR-024273(168.196.208.63.sbl.spamhaus.org) A:host name is unknown
20:17:34.510 5 DNR-024274(mxout4.mailhop.org) A-request
20:17:34.510 4 DNR-024274(mxout4.mailhop.org) A-request -> udp:[192.168.100.1]:53
20:17:34.510 5 DNR-024274(mxout4.mailhop.org) got 372 bytes from [192.168.100.1]:53: 5E D2 81 80 00 01 00 01 00 06 00 08 06 6D 78 6F 75 74 34 07 6D 61 69 6C 68 6F 70 03 6F 72 67 00 00 01 00 01 C0 0C 00 01 00 01 00 00 6E 65 00 04 3F D0 C4 A8 03 4F 52 47 00 00 02 00 01 00 00 89 C3 00 13 04 54 4C 44
20:17:34.510 5 DNR-024274(mxout4.mailhop.org) A:OK
20:17:34.510 4 DNR-024274(mxout4.mailhop.org) A[0]: mxout4.mailhop.org=[63.208.196.168]
20:17:34.550 5 DNR-024275(mtu-net.ru) MX-request
20:17:34.550 4 DNR-024275(mtu-net.ru) MX-request -> udp:[192.168.100.1]:53
20:17:34.550 5 DNR-024275(mtu-net.ru) got 505 bytes from [192.168.100.1]:53: 5E D3 81 80 00 01 00 01 00 0D 00 0F 07 6D 74 75 2D 6E 65 74 02 72 75 00 00 0F 00 01 C0 0C 00 0F 00 01 00 00 00 81 00 0E 00 0A 03 6D 78 30 03 6D 74 75 02 72 75 00 00 00 02 00 01 00 32 CD 0B 00 14 01 4D 0C 52 4F 4F 54 2D 53
20:17:34.550 5 DNR-024275(mtu-net.ru) MX:OK
20:17:34.550 4 DNR-024275(mtu-net.ru) MX[0]: mtu-net.ru(pty 10) = mx0.mtu.ru
20:17:34.550 4 DNR-024275(mtu-net.ru) suppl[0]: mx0.mtu.ru=[195.34.32.254]
The spamhaus.org lookups are (obviously) for DNSBL lookups (host name is unknown indicates that the host is *not* on a blocklist).
Anyway, this was a relatively quiet couple of minutes.
DNS is a busy service!
On 02/09/07 05:53 pm, Leon D. Zetekoff thus wrote :
* Lewis G Rosenthal wrote, On 2/9/2007 5:43 PM:
If you're browsing or checking or sending email, UDP 53 will be in constant use (unless you have such a huge hosts file that lookups are unnecessary). You really need to debug the DNS requests to determine what it's trying to find, and that should give you some clue as to what's asking.
Hi Lewis...but this is from my OS?2 machine which all it is doing is processing mail every five minutes. All those NAT sessions seem way too many for what should be going on....
Leon
IPTRACE won't give you enough detail. You'll need something which will list the UDP packets on port 53 and their contents in order to determine what is being requested.
On 02/09/07 12:34 pm, Leon D. Zetekoff thus wrote :
yes the 192...100 is the os2 box on my internal network. It is NATed by the router. Yes port 53 is DNS but OS2 for some reason is chatting away. Guess I'll get a task list and see what's in there. The 199.224 address is one of the DNS servers of my provider.
Thanks leon
* Sam Lewis wrote, On 2/9/2007 12:25 PM:
It's probably the port NAT is using to forward packets. Here is a link to an explanation of how NAT works. It may explain this better.
http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a0080094831.shtml#flash Sam
Leon D. Zetekoff wrote:
Sorry for the crosspost but trying to get an answer...thanks leon
====================
It seems my os/2 box likes to talk out to port 53. Check out this from
my router:
Page 40/40
Internal Prot. External NAT Time-out
192.168.0.100:54692 UDP 199.224.86.16:53 65159 153
192.168.0.100:54713 UDP 199.224.86.16:53 65191 159
192.168.0.100:54800 UDP 199.224.86.16:53 65215 195
192.168.0.100:54779 UDP 199.224.86.16:53 65239 186
192.168.0.100:54562 UDP 199.224.86.16:53 65261 103
192.168.0.100:54477 UDP 199.224.86.16:53 65263 63
192.168.0.100:54967 UDP 199.224.86.16:53 65271 266
192.168.0.100:54387 UDP 199.224.86.16:53 65299 39
192.168.0.100:54758 UDP 199.224.86.16:53 65331 177
192.168.0.100:54336 UDP 199.224.86.16:53 65335 14
192.168.0.102:1803 UDP 199.224.86.20:53 65357 214
192.168.0.100:54527 UDP 199.224.86.16:53 65361 86
192.168.0.100:54509 UDP 199.224.86.16:53 65405 80
192.168.0.100:54383 UDP 199.224.86.16:53 65409 39
192.168.0.100:54649 UDP 199.224.86.16:53 65423 141
192.168.0.100:55015 UDP 199.224.86.16:53 65431 274
192.168.0.100:54877 UDP 199.224.86.16:53 65433 229
192.168.0.100:54732 UDP 199.224.86.16:53 65437 167
192.168.0.100:54898 UDP 199.224.86.16:53 65453 239
192.168.0.100 is the os2 box any idea why it chatters so much?
Thanks leon
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This message is sent to you because you are subscribed to
the mailing list <os2-wireless_users@2rosenthals.com>.
To unsubscribe, E-mail to: <os2-wireless_users-off@2rosenthals.com>
To switch to the DIGEST mode, E-mail to <os2-wireless_users-digest@2rosenthals.com>
To switch to the INDEX mode, E-mail to <os2-wireless_users-index@2rosenthals.com>
Send administrative queries to <os2-wireless_users-request@2rosenthals.com>
To subscribe (new addresses), E-mail to: <os2-wireless_users-on@2rosenthals.com> and reply to the confirmation email.
This list is hosted by Rosenthal & Rosenthal
P.O. Box 281, Deer Park, NY 11729-0281. Non-
electronic communications related to content
contained in these messages should be directed
to the above address. (CAN-SPAM Act of 2003)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This message is sent to you because you are subscribed to
the mailing list <os2-wireless_users@2rosenthals.com>.
To unsubscribe, E-mail to: <os2-wireless_users-off@2rosenthals.com>
To switch to the DIGEST mode, E-mail to <os2-wireless_users-digest@2rosenthals.com>
To switch to the INDEX mode, E-mail to <os2-wireless_users-index@2rosenthals.com>
Send administrative queries to <os2-wireless_users-request@2rosenthals.com>
To subscribe (new addresses), E-mail to: <os2-wireless_users-on@2rosenthals.com> and reply to the confirmation email.
This list is hosted by Rosenthal & Rosenthal
P.O. Box 281, Deer Park, NY 11729-0281. Non-
electronic communications related to content
contained in these messages should be directed
to the above address. (CAN-SPAM Act of 2003)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This message is sent to you because you are subscribed to
the mailing list <os2-wireless_users@2rosenthals.com>.
To unsubscribe, E-mail to: <os2-wireless_users-off@2rosenthals.com>
To switch to the DIGEST mode, E-mail to <os2-wireless_users-digest@2rosenthals.com>
To switch to the INDEX mode, E-mail to <os2-wireless_users-index@2rosenthals.com>
Send administrative queries to <os2-wireless_users-request@2rosenthals.com>
To subscribe (new addresses), E-mail to: <os2-wireless_users-on@2rosenthals.com> and reply to the confirmation email.
This list is hosted by Rosenthal & Rosenthal
P.O. Box 281, Deer Park, NY 11729-0281. Non-
electronic communications related to content
contained in these messages should be directed
to the above address. (CAN-SPAM Act of 2003)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-- *Leon Zetekoff*
Proprietor
*Work:* 484-335-9920
*Mobile:* 610-223-8642
*Fax:* 484-335-9921
*Email:* wa4zlw@arrl.net <mailto:wa4zlw@arrl.net>
*http://www.linkedin.com/in/leonzetekoff*
*BackWoods Wireless*
<http://www.backwoodswireless.net> 505 B Main Street
<http://maps.google.com/maps?q=505+B+Main+Street%2CBlandon%2CPA+19510&hl=en> Blandon, PA 19510
"Bringing Broadband Technology to Rural Areas"
See who we know in common <http://www.linkedin.com/e/wwk/1265359/> Want a signature like this? <http://www.linkedin.com/e/sig/1265359/>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This message is sent to you because you are subscribed to
the mailing list <os2-wireless_users@2rosenthals.com>.
To unsubscribe, E-mail to: <os2-wireless_users-off@2rosenthals.com>
To switch to the DIGEST mode, E-mail to <os2-wireless_users-digest@2rosenthals.com>
To switch to the INDEX mode, E-mail to <os2-wireless_users-index@2rosenthals.com>
Send administrative queries to <os2-wireless_users-request@2rosenthals.com>
To subscribe (new addresses), E-mail to: <os2-wireless_users-on@2rosenthals.com> and reply to the confirmation email.
This list is hosted by Rosenthal & Rosenthal
P.O. Box 281, Deer Park, NY 11729-0281. Non-
electronic communications related to content
contained in these messages should be directed
to the above address. (CAN-SPAM Act of 2003)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
--
Lewis
------------------------------------------------------------
Lewis G Rosenthal, CNA, CLP, CLE
Rosenthal & Rosenthal, LLC
Accountants / Network Consultants
New York / Northern Virginia www.2rosenthals.com
eComStation Consultants www.ecomstation.com
Novell Users Int'l www.novell.com/openenterpriseserver
Need a managed Wi-Fi hotspot? www.hautspot.com
------------------------------------------------------------
|
|
|
|
|
|