Charlie Tame said:
Jim Byrd said:
Charlie Tame said:Then maybe the problem is just one of speed Jim?
I only got one of the names back on that webpage but I don't use it very
often and don't really know how the page "Usually" performs. I guess this
could be delays outside of Ray's control but it seems to me someone who
regularly deals with DNS servers might be more helpful at this stage.
Charlie
Jim Byrd said:Ray and Charlie - FWIW, I just ran DNSTester 1.0 on that IP for 6 domains
using 10 threads. All domains and threads failed on the same Socket Read
Timeout error. Here's the last domain tested and the summary:
2408: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
3040: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
3028: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
708: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
764: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
988: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
1768: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
2784: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
2828: done - 191355ms. - 0 successes, 6 failures.
2408: done - 191365ms. - 0 successes, 6 failures.
3040: done - 191365ms. - 0 successes, 6 failures.
3028: done - 191365ms. - 0 successes, 6 failures.
708: done - 191375ms. - 0 successes, 6 failures.
764: done - 191416ms. - 0 successes, 6 failures.
988: done - 191365ms. - 0 successes, 6 failures.
1768: done - 191385ms. - 0 successes, 6 failures.
3208: done - 191375ms. - 0 successes, 6 failures.
2784: done - 190333ms. - 0 successes, 6 failures.
*** Finished ***
Total Attempts = 60
Total Time = 1912.699 seconds
Total OK = 0
Total NG = 60
Average Response Time = 31.8783166666667 seconds
Response time is poor
Success % = 0
Failed
Note: Results are from a small sampling (60) and should not be considered
accurate. Try setting a higher thread count or using a file with more
domains entries.
--
Regards, Jim Byrd, MS-MVP
My Blog, Defending Your Machine, here:
http://defendingyourmachine.blogspot.com/
http://www.webmaster-toolkit.com/[email protected]Charlie Tame said:I think I misunderstood your question first time around and there is a group
for windows.server.dns which might be more knowledgable about setting up the
server side of things. It's not a "Guess" by the server, I was suggesting a
human guess for a likely name from the user end of things. Your server
should get a DNS resolution for the domain and then from the domain servers
it should get the relevant details for mail. Perhaps this is something to do
with incorrect MX records if it's not working.
Here is what I got from whois at twinic.net
Domain Name: action.com.tw
Record expires on 2006-05-31 (YYYY-MM-DD)
Record created on 1997-05-01 (YYYY-MM-DD)
Domain servers in listed order:
isacn01.action.com.tw 203.75.63.13
mailacn01.action.com.tw 203.75.63.14
I really don't have any experience with setting up DNS servers but going by
that website it seems that isacn01 is coming back as the mail server address
and if it's not then I imagine there could be problems.
Charlie
Charlie,
Many thanks for your additional information.
Does the DNS server guess in this way? If so, it tells why our email
server cannot deliver some emails that do not meet such guess.
For example, we have to send an email to (e-mail address removed) and our email
server cannot deliver due to unresolved ip. Its email server address is
mailacn01.action.com.tw. I am unsure where fails to interpret
(e-mail address removed) to mailacn01.action.com.tw URL address and ip address.
It might be either their chain of machine issue or our chain of machine
issue. How can I identify the source of the issue?
Thanks
Ray
Easiest way is guess and simply type it in then do a "DNS" on it...
Most will be mail.domain.xxx or smtp.domain.xxx etc... if it comes back
with numbers there's a good chance you hit it.
To get info from OE highlight the message (right click) and select
properties then details... then message source if you want a better view.
If you have the preview pane open just highlight the message in the
list
hold down control key and press F3. That will give you fairly reliable
info on the domain of the computer that sent it.
I find the downloadable version easy to use by the way and it runs fine
on everything I've used so far inc W2003.
Charlie,
Thanks for your additional information. Could you please advise how can
I obtain the mail server name or ip from the domain name of a email
address in SamSpade.
Ray
For what it's worth a number of people seem to have had DNS problems
recently and some DNS systems have come under attack so I would not
be
too hasty about ripping your system apart without waiting a day or
two
If you translate some to numeric addresses using samspade and they work
alright it's almost certainly a DNS problem but beware that not all
numerics go to the site you expect because there is a secondary
method
of site location.
Charlie
Charlie,
Thanks for your useful source.
Ray
Ray,
http://www.samspade.org/ has a useful website and a downloadable
utility that can help with DNS and email stuff, you may find that
useful in future so I suggest taking a look.
It doesn't matter which DNS server you use. In theory your ISP is the
closest (less hops to find it etc) but you can even run your own if
problems persist. I can't go into detail but I know the owner of this
site is genuine and his software has been rigorously tested so you
might find it interesting to read http://www.ntcanuck.com/
Charlie
We are using the DNS server in our ISP and found from time to time
cannot resolve ips from URL addresses. Can someone advise how can I
verify if the DNS server in our ISP is operating correctly or the
servers located else where.
Thanks,
Ray
IfJim Byrd said:Agree, Charlie, although I would suspect non-response rather than just
delays for delays of that length.
--
Regards, Jim Byrd, MS-MVP
My Blog, Defending Your Machine, here:
http://defendingyourmachine.blogspot.com/
Charlie Tame said:Then maybe the problem is just one of speed Jim?
I only got one of the names back on that webpage but I don't use it very
often and don't really know how the page "Usually" performs. I guess this
could be delays outside of Ray's control but it seems to me someone who
regularly deals with DNS servers might be more helpful at this stage.
Charlie
Jim Byrd said:Ray and Charlie - FWIW, I just ran DNSTester 1.0 on that IP for 6
domains
using 10 threads. All domains and threads failed on the same Socket
Read
Timeout error. Here's the last domain tested and the summary:
2408: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
3040: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
3028: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
708: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
764: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
988: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
1768: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
2784: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
2828: done - 191355ms. - 0 successes, 6 failures.
2408: done - 191365ms. - 0 successes, 6 failures.
3040: done - 191365ms. - 0 successes, 6 failures.
3028: done - 191365ms. - 0 successes, 6 failures.
708: done - 191375ms. - 0 successes, 6 failures.
764: done - 191416ms. - 0 successes, 6 failures.
988: done - 191365ms. - 0 successes, 6 failures.
1768: done - 191385ms. - 0 successes, 6 failures.
3208: done - 191375ms. - 0 successes, 6 failures.
2784: done - 190333ms. - 0 successes, 6 failures.
*** Finished ***
Total Attempts = 60
Total Time = 1912.699 seconds
Total OK = 0
Total NG = 60
Average Response Time = 31.8783166666667 seconds
Response time is poor
Success % = 0
Failed
Note: Results are from a small sampling (60) and should not be
considered
accurate. Try setting a higher thread count or using a file with more
domains entries.
--
Regards, Jim Byrd, MS-MVP
My Blog, Defending Your Machine, here:
http://defendingyourmachine.blogspot.com/
Well I just checked on the mail server name you mentioned
(mailacn01.action.com.tw) and it resolves fine here to IP address
203.75.63.14
However looking up (e-mail address removed) on this website shows the
other
server listed in the whois below... so the info is there ..
http://www.webmaster-toolkit.com/[email protected]
I think I misunderstood your question first time around and there is a group
for windows.server.dns which might be more knowledgable about setting
up the
server side of things. It's not a "Guess" by the server, I was suggesting a
human guess for a likely name from the user end of things. Your server
should get a DNS resolution for the domain and then from the domain servers
it should get the relevant details for mail. Perhaps this is something to do
with incorrect MX records if it's not working.
Here is what I got from whois at twinic.net
Domain Name: action.com.tw
Record expires on 2006-05-31 (YYYY-MM-DD)
Record created on 1997-05-01 (YYYY-MM-DD)
Domain servers in listed order:
isacn01.action.com.tw 203.75.63.13
mailacn01.action.com.tw 203.75.63.14
I really don't have any experience with setting up DNS servers but
going by
that website it seems that isacn01 is coming back as the mail server address
and if it's not then I imagine there could be problems.
Charlie
Charlie,
Many thanks for your additional information.
Does the DNS server guess in this way? If so, it tells why our email
server cannot deliver some emails that do not meet such guess.
For example, we have to send an email to (e-mail address removed) and our email
server cannot deliver due to unresolved ip. Its email server address is
mailacn01.action.com.tw. I am unsure where fails to interpret
(e-mail address removed) to mailacn01.action.com.tw URL address and ip address.
It might be either their chain of machine issue or our chain of
machine
issue. How can I identify the source of the issue?
Thanks
Ray
Easiest way is guess and simply type it in then do a "DNS" on it...
Most will be mail.domain.xxx or smtp.domain.xxx etc... if it comes back
with numbers there's a good chance you hit it.
To get info from OE highlight the message (right click) and select
properties then details... then message source if you want a better view.
If you have the preview pane open just highlight the message in the
list
hold down control key and press F3. That will give you fairly
reliable
info on the domain of the computer that sent it.
I find the downloadable version easy to use by the way and it runs fine
on everything I've used so far inc W2003.
Charlie,
Thanks for your additional information. Could you please advise how can
I obtain the mail server name or ip from the domain name of a email
address in SamSpade.
Ray
For what it's worth a number of people seem to have had DNS
problems
recently and some DNS systems have come under attack so I would not
be
too hasty about ripping your system apart without waiting a day or
two
If you translate some to numeric addresses using samspade and they work
alright it's almost certainly a DNS problem but beware that not all
numerics go to the site you expect because there is a secondary
method
of site location.
Charlie
Charlie,
Thanks for your useful source.
Ray
Ray,
http://www.samspade.org/ has a useful website and a downloadable
utility that can help with DNS and email stuff, you may find that
useful in future so I suggest taking a look.
It doesn't matter which DNS server you use. In theory your ISP is the
closest (less hops to find it etc) but you can even run your own if
problems persist. I can't go into detail but I know the owner of this
site is genuine and his software has been rigorously tested so
you
might find it interesting to read http://www.ntcanuck.com/
Charlie
We are using the DNS server in our ISP and found from time to time
cannot resolve ips from URL addresses. Can someone advise how can I
verify if the DNS server in our ISP is operating correctly or
the
servers located else where.
Thanks,
Ray
Charlie Tame said:Well I think I misunderstood the question first time around, thinking it was
a question from the user end of things.
I must admit that with some of the server stuff (SMTP, POP, NNTP, FTP and
DNS) setups suffer from MS "Assumption language" - the setup data starts off
okay but degenerates to a series of 3 letter abbreviations you don't
necessarily have a complete knowledge of but the author assumes you do
the "abc" need to be integrated with the "def" you should set "ghi" to "jkl"
Course this leads to hours of searching to find references to the 3 letter
abbreviation so you can find out how to do what you want to do, but then
when you find the reference you are back into more of the same. Example -
one thing I have always found hard to follow is the "Permissions" scheme so
I want an FTP server the public can use but I want some private and secure
folders. Can you find a clear explanation of how to do this? I swear that is
one reason people go out and buy competitor's products and also make
security mistakes.
Charlie
Jim Byrd said:Agree, Charlie, although I would suspect non-response rather than just
delays for delays of that length.
--
Regards, Jim Byrd, MS-MVP
My Blog, Defending Your Machine, here:
http://defendingyourmachine.blogspot.com/
http://www.webmaster-toolkit.com/[email protected]Charlie Tame said:I think I misunderstood your question first time around and there is a group
for windows.server.dns which might be more knowledgable about setting
up the
server side of things. It's not a "Guess" by the server, I was suggesting a
human guess for a likely name from the user end of things. Your server
should get a DNS resolution for the domain and then from the domain servers
it should get the relevant details for mail. Perhaps this is something to do
with incorrect MX records if it's not working.
Here is what I got from whois at twinic.net
Domain Name: action.com.tw
Record expires on 2006-05-31 (YYYY-MM-DD)
Record created on 1997-05-01 (YYYY-MM-DD)
Domain servers in listed order:
isacn01.action.com.tw 203.75.63.13
mailacn01.action.com.tw 203.75.63.14
I really don't have any experience with setting up DNS servers but
going by
that website it seems that isacn01 is coming back as the mail server address
and if it's not then I imagine there could be problems.
Charlie
Charlie,
Many thanks for your additional information.
Does the DNS server guess in this way? If so, it tells why our email
server cannot deliver some emails that do not meet such guess.
For example, we have to send an email to (e-mail address removed) and our email
server cannot deliver due to unresolved ip. Its email server address is
mailacn01.action.com.tw. I am unsure where fails to interpret
(e-mail address removed) to mailacn01.action.com.tw URL address and ip address.
It might be either their chain of machine issue or our chain of
machine
issue. How can I identify the source of the issue?
Thanks
Ray
Easiest way is guess and simply type it in then do a "DNS" on it...
Most will be mail.domain.xxx or smtp.domain.xxx etc... if it comes back
with numbers there's a good chance you hit it.
To get info from OE highlight the message (right click) and select
properties then details... then message source if you want a better view.
If you have the preview pane open just highlight the message in the
list
hold down control key and press F3. That will give you fairly
reliable
info on the domain of the computer that sent it.
I find the downloadable version easy to use by the way and it runs fine
on everything I've used so far inc W2003.
Charlie,
Thanks for your additional information. Could you please advise how can
I obtain the mail server name or ip from the domain name of a email
address in SamSpade.
Ray
For what it's worth a number of people seem to have had DNS
problems
recently and some DNS systems have come under attack so I would not
be
too hasty about ripping your system apart without waiting a day or
two
If you translate some to numeric addresses using samspade and they work
alright it's almost certainly a DNS problem but beware that not all
numerics go to the site you expect because there is a secondary
method
of site location.
Charlie
Charlie,
Thanks for your useful source.
Ray
Ray,
http://www.samspade.org/ has a useful website and a downloadable
utility that can help with DNS and email stuff, you may find that
useful in future so I suggest taking a look.
It doesn't matter which DNS server you use. In theory your ISP is the
closest (less hops to find it etc) but you can even run your own if
problems persist. I can't go into detail but I know the owner of this
site is genuine and his software has been rigorously tested so
you
might find it interesting to read http://www.ntcanuck.com/
Charlie
We are using the DNS server in our ISP and found from time to time
cannot resolve ips from URL addresses. Can someone advise how can I
verify if the DNS server in our ISP is operating correctly or
the
servers located else where.
Thanks,
Ray
Jim Byrd said:Hi Charlie - You might want to take a look at MVP Mark Salloway's series
on
IIS here: http://www.mvps.org/marksxp/WindowsXP/IIS/iishome.php All four
parts are pertinent to various aspects of securing an FTP, while parts 2
and
3 directly address your question.
--
Regards, Jim Byrd, MS-MVP
My Blog, Defending Your Machine, here:
http://defendingyourmachine.blogspot.com/
Charlie Tame said:Well I think I misunderstood the question first time around, thinking it was
a question from the user end of things.
I must admit that with some of the server stuff (SMTP, POP, NNTP, FTP and
DNS) setups suffer from MS "Assumption language" - the setup data starts off
okay but degenerates to a series of 3 letter abbreviations you don't
necessarily have a complete knowledge of but the author assumes you do
the "abc" need to be integrated with the "def" you should set "ghi" to "jkl"
Course this leads to hours of searching to find references to the 3
letter
abbreviation so you can find out how to do what you want to do, but then
when you find the reference you are back into more of the same. Example -
one thing I have always found hard to follow is the "Permissions" scheme so
I want an FTP server the public can use but I want some private and
secure
folders. Can you find a clear explanation of how to do this? I swear that is
one reason people go out and buy competitor's products and also make
security mistakes.
Charlie
Jim Byrd said:Agree, Charlie, although I would suspect non-response rather than just
delays for delays of that length.
--
Regards, Jim Byrd, MS-MVP
My Blog, Defending Your Machine, here:
http://defendingyourmachine.blogspot.com/
Then maybe the problem is just one of speed Jim?
I only got one of the names back on that webpage but I don't use it
very
often and don't really know how the page "Usually" performs. I guess this
could be delays outside of Ray's control but it seems to me someone who
regularly deals with DNS servers might be more helpful at this stage.
Charlie
Ray and Charlie - FWIW, I just ran DNSTester 1.0 on that IP for 6
domains
using 10 threads. All domains and threads failed on the same Socket
Read
Timeout error. Here's the last domain tested and the summary:
2408: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
3040: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
3028: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
708: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
764: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
988: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
1768: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
2784: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
2828: done - 191355ms. - 0 successes, 6 failures.
2408: done - 191365ms. - 0 successes, 6 failures.
3040: done - 191365ms. - 0 successes, 6 failures.
3028: done - 191365ms. - 0 successes, 6 failures.
708: done - 191375ms. - 0 successes, 6 failures.
764: done - 191416ms. - 0 successes, 6 failures.
988: done - 191365ms. - 0 successes, 6 failures.
1768: done - 191385ms. - 0 successes, 6 failures.
3208: done - 191375ms. - 0 successes, 6 failures.
2784: done - 190333ms. - 0 successes, 6 failures.
*** Finished ***
Total Attempts = 60
Total Time = 1912.699 seconds
Total OK = 0
Total NG = 60
Average Response Time = 31.8783166666667 seconds
Response time is poor
Success % = 0
Failed
Note: Results are from a small sampling (60) and should not be
considered
accurate. Try setting a higher thread count or using a file with more
domains entries.
--
Regards, Jim Byrd, MS-MVP
My Blog, Defending Your Machine, here:
http://defendingyourmachine.blogspot.com/
Well I just checked on the mail server name you mentioned
(mailacn01.action.com.tw) and it resolves fine here to IP address
203.75.63.14
However looking up (e-mail address removed) on this website shows the
other
server listed in the whois below... so the info is there ..
http://www.webmaster-toolkit.com/[email protected]
I think I misunderstood your question first time around and there is
a group
for windows.server.dns which might be more knowledgable about setting
up
the
server side of things. It's not a "Guess" by the server, I was suggesting a
human guess for a likely name from the user end of things. Your
server
should get a DNS resolution for the domain and then from the domain servers
it should get the relevant details for mail. Perhaps this is
something to do
with incorrect MX records if it's not working.
Here is what I got from whois at twinic.net
Domain Name: action.com.tw
Record expires on 2006-05-31 (YYYY-MM-DD)
Record created on 1997-05-01 (YYYY-MM-DD)
Domain servers in listed order:
isacn01.action.com.tw 203.75.63.13
mailacn01.action.com.tw 203.75.63.14
I really don't have any experience with setting up DNS servers but
going
by
that website it seems that isacn01 is coming back as the mail server address
and if it's not then I imagine there could be problems.
Charlie
Charlie,
Many thanks for your additional information.
Does the DNS server guess in this way? If so, it tells why our
server cannot deliver some emails that do not meet such guess.
For example, we have to send an email to (e-mail address removed) and our email
server cannot deliver due to unresolved ip. Its email server
address is
mailacn01.action.com.tw. I am unsure where fails to interpret
(e-mail address removed) to mailacn01.action.com.tw URL address and ip address.
It might be either their chain of machine issue or our chain of
machine
issue. How can I identify the source of the issue?
Thanks
Ray
Easiest way is guess and simply type it in then do a "DNS" on it...
Most will be mail.domain.xxx or smtp.domain.xxx etc... if it comes back
with numbers there's a good chance you hit it.
To get info from OE highlight the message (right click) and select
properties then details... then message source if you want a better view.
If you have the preview pane open just highlight the message in the
list
hold down control key and press F3. That will give you fairly
reliable
info on the domain of the computer that sent it.
I find the downloadable version easy to use by the way and it runs fine
on everything I've used so far inc W2003.
Charlie,
Thanks for your additional information. Could you please advise how can
I obtain the mail server name or ip from the domain name of a
address in SamSpade.
Ray
For what it's worth a number of people seem to have had DNS
problems
recently and some DNS systems have come under attack so I would not
be
too hasty about ripping your system apart without waiting a day
or
two
If you translate some to numeric addresses using samspade and
they work
alright it's almost certainly a DNS problem but beware that not all
numerics go to the site you expect because there is a secondary
method
of site location.
Charlie
Charlie,
Thanks for your useful source.
Ray
Ray,
http://www.samspade.org/ has a useful website and a
downloadable
utility that can help with DNS and email stuff, you may find that
useful in future so I suggest taking a look.
It doesn't matter which DNS server you use. In theory your ISP is the
closest (less hops to find it etc) but you can even run your
own if
problems persist. I can't go into detail but I know the owner
of this
site is genuine and his software has been rigorously tested so
you
might find it interesting to read http://www.ntcanuck.com/
Charlie
We are using the DNS server in our ISP and found from time to time
cannot resolve ips from URL addresses. Can someone advise how can I
verify if the DNS server in our ISP is operating correctly or
the
servers located else where.
Thanks,
Ray
Charlie Tame said:Well thanks Jim I hadn't seen that one and it's probably just what I need to
check through. It is unfortunate that such useful sites are not immediately
obvious when searching. I suppose MS don't have the staff to do it but you'd
think a "Do this to get that" based on common configurations might be in
order. I suppose then they'd never sell the training courses.
Charlie
Jim Byrd said:Hi Charlie - You might want to take a look at MVP Mark Salloway's series
on
IIS here: http://www.mvps.org/marksxp/WindowsXP/IIS/iishome.php All four
parts are pertinent to various aspects of securing an FTP, while parts 2
and
3 directly address your question.
--
Regards, Jim Byrd, MS-MVP
My Blog, Defending Your Machine, here:
http://defendingyourmachine.blogspot.com/
http://www.webmaster-toolkit.com/[email protected]Charlie Tame said:Well I think I misunderstood the question first time around, thinking it was
a question from the user end of things.
I must admit that with some of the server stuff (SMTP, POP, NNTP, FTP and
DNS) setups suffer from MS "Assumption language" - the setup data starts off
okay but degenerates to a series of 3 letter abbreviations you don't
necessarily have a complete knowledge of but the author assumes you do
the "abc" need to be integrated with the "def" you should set "ghi" to "jkl"
Course this leads to hours of searching to find references to the 3
letter
abbreviation so you can find out how to do what you want to do, but then
when you find the reference you are back into more of the same. Example -
one thing I have always found hard to follow is the "Permissions" scheme so
I want an FTP server the public can use but I want some private and
secure
folders. Can you find a clear explanation of how to do this? I swear that is
one reason people go out and buy competitor's products and also make
security mistakes.
Charlie
Agree, Charlie, although I would suspect non-response rather than just
delays for delays of that length.
--
Regards, Jim Byrd, MS-MVP
My Blog, Defending Your Machine, here:
http://defendingyourmachine.blogspot.com/
Then maybe the problem is just one of speed Jim?
I only got one of the names back on that webpage but I don't use it
very
often and don't really know how the page "Usually" performs. I guess this
could be delays outside of Ray's control but it seems to me someone who
regularly deals with DNS servers might be more helpful at this stage.
Charlie
Ray and Charlie - FWIW, I just ran DNSTester 1.0 on that IP for 6
domains
using 10 threads. All domains and threads failed on the same Socket
Read
Timeout error. Here's the last domain tested and the summary:
2408: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
3040: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
3028: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
708: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
764: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
988: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
1768: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
2784: [google.com] : [LOC:1 / Sock receive] Socket Read Timeout
2828: done - 191355ms. - 0 successes, 6 failures.
2408: done - 191365ms. - 0 successes, 6 failures.
3040: done - 191365ms. - 0 successes, 6 failures.
3028: done - 191365ms. - 0 successes, 6 failures.
708: done - 191375ms. - 0 successes, 6 failures.
764: done - 191416ms. - 0 successes, 6 failures.
988: done - 191365ms. - 0 successes, 6 failures.
1768: done - 191385ms. - 0 successes, 6 failures.
3208: done - 191375ms. - 0 successes, 6 failures.
2784: done - 190333ms. - 0 successes, 6 failures.
*** Finished ***
Total Attempts = 60
Total Time = 1912.699 seconds
Total OK = 0
Total NG = 60
Average Response Time = 31.8783166666667 seconds
Response time is poor
Success % = 0
Failed
Note: Results are from a small sampling (60) and should not be
considered
accurate. Try setting a higher thread count or using a file with more
domains entries.
--
Regards, Jim Byrd, MS-MVP
My Blog, Defending Your Machine, here:
http://defendingyourmachine.blogspot.com/
Well I just checked on the mail server name you mentioned
(mailacn01.action.com.tw) and it resolves fine here to IP address
203.75.63.14
However looking up (e-mail address removed) on this website shows the
other
server listed in the whois below... so the info is there ..I think I misunderstood your question first time around and there is
a group
for windows.server.dns which might be more knowledgable about setting
up
the
server side of things. It's not a "Guess" by the server, I was suggesting a
human guess for a likely name from the user end of things. Your
server
should get a DNS resolution for the domain and then from the domain servers
it should get the relevant details for mail. Perhaps this is
something to do
with incorrect MX records if it's not working.
Here is what I got from whois at twinic.net
Domain Name: action.com.tw
Record expires on 2006-05-31 (YYYY-MM-DD)
Record created on 1997-05-01 (YYYY-MM-DD)
Domain servers in listed order:
isacn01.action.com.tw 203.75.63.13
mailacn01.action.com.tw 203.75.63.14
I really don't have any experience with setting up DNS servers but
going
by
that website it seems that isacn01 is coming back as the mail server address
and if it's not then I imagine there could be problems.
Charlie
Charlie,
Many thanks for your additional information.
Does the DNS server guess in this way? If so, it tells why our
server cannot deliver some emails that do not meet such guess.
For example, we have to send an email to (e-mail address removed) and our email
server cannot deliver due to unresolved ip. Its email server
address is
mailacn01.action.com.tw. I am unsure where fails to interpret
(e-mail address removed) to mailacn01.action.com.tw URL address and ip address.
It might be either their chain of machine issue or our chain of
machine
issue. How can I identify the source of the issue?
Thanks
Ray
Easiest way is guess and simply type it in then do a "DNS" on it...
Most will be mail.domain.xxx or smtp.domain.xxx etc... if it comes back
with numbers there's a good chance you hit it.
To get info from OE highlight the message (right click) and select
properties then details... then message source if you want a better view.
If you have the preview pane open just highlight the message in the
list
hold down control key and press F3. That will give you fairly
reliable
info on the domain of the computer that sent it.
I find the downloadable version easy to use by the way and it runs fine
on everything I've used so far inc W2003.
Charlie,
Thanks for your additional information. Could you please advise how can
I obtain the mail server name or ip from the domain name of a
address in SamSpade.
Ray
For what it's worth a number of people seem to have had DNS
problems
recently and some DNS systems have come under attack so I would not
be
too hasty about ripping your system apart without waiting a day
or
two
If you translate some to numeric addresses using samspade and
they work
alright it's almost certainly a DNS problem but beware that not all
numerics go to the site you expect because there is a secondary
method
of site location.
Charlie
Charlie,
Thanks for your useful source.
Ray
Ray,
http://www.samspade.org/ has a useful website and a
downloadable
utility that can help with DNS and email stuff, you may find that
useful in future so I suggest taking a look.
It doesn't matter which DNS server you use. In theory your ISP is the
closest (less hops to find it etc) but you can even run your
own if
problems persist. I can't go into detail but I know the owner
of this
site is genuine and his software has been rigorously tested so
you
might find it interesting to read http://www.ntcanuck.com/
Charlie
We are using the DNS server in our ISP and found from time to time
cannot resolve ips from URL addresses. Can someone advise how can I
verify if the DNS server in our ISP is operating correctly or
the
servers located else where.
Thanks,
Ray