
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-20-2009 03:43 PM
Since the upgrade to 3.5 I have been seeing alot more of this error. When using the connection tester I can connect via the IP Address get OK for all test, but connecting via the NETBIOS Name or the FQDN does not work.
I thought that the Active Scan attempted to connect via all three methods, is that not correct.
Anyway was just wondering if there was something I could do to resolve this issue.
Thanks.
I thought that the Active Scan attempted to connect via all three methods, is that not correct.
Anyway was just wondering if there was something I could do to resolve this issue.
Thanks.
Labels:
- Labels:
-
Archive
1 REPLY 1

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-20-2009 04:11 PM
Active scanning connects to the FQDN.
Errors like this happen if you have wrong IP/dns entries. (dns names pointing to wrong IP addresses)
Errors like this happen if you have wrong IP/dns entries. (dns names pointing to wrong IP addresses)
