Senderbase DNS failing?
As of 02/19/2014our Cisco ironport started getting failures on senderbase lookups:
i.e. SG UNKNOWNLIST match sbrs[none] SBRS unable to retrieve
.... because DNS queries like 49.33.146.216.sb-adfe2ko9.senderbase.org are returning NXDOMAIN
This has happened in the past when Senderbase has had issues but I'm not finding any info on this.
Anyone else having this problem right now?
-Bryan Hance
As with the IPAS and AV updates - it is possible you may have had an issue with a previous update completing, and then staled out the rules --- in which, using the 'force' will prompt the appliance to reachout and grab ALL rules, and reimplement the update in complete... correcting the issue. If you 'grep' the "updater_logs" - do you see any issues with the updater service... anything outside of the norm?
Hope this helps!
-Robert
(*If you have received the answer to your original question, and found this helpful/correct - please mark the question as answered, and be sure to leave a rating to reflect!)
Similar Messages
-
Help
WiFi only works close to router, DNS fail, Signal Bars present but Safari says no Internet, I've deleted and re-added through to reset and full reset, I had no problem with 4.3.2 only 4.3.3 both my iPhone4 and my iPad2. I am now beside router - no problem, but go 20 metres and WiFi becomes unstable. Only way to get either to work is disable WiFi either as a Hot Spot or turn it off and use the 3G connection. This worked with 4.3 & 4.3.2 what has gone wrong? I raised it at the Apple Store in Belfast as a problem but was told that there was no problem with Apple but I must have a faulty router - yeah - that's a lot of faulty routers, my home, my office, my holiday home, Starbucks, my friends house, my son's house. I've tried all the 'fixes'. I think it is a plan to force us to buy Apple RoutersTwo ways out, I added two more Belkin Access Points in my house in Spain so that I'm not more than 10Mtrs away, (Reinforced Concrete & solar glass 2010)
I bought 3 Apple Airports, 1 x Extreme and 2 x Express (1 as a hard wired AP, 1 as an extender) for my other house (Brick construction 1930's)
Everthing now works perfectly, as I said 'an apple plot', so either blast them with signal or visit your nearest apple store.
Early beta iOS5 (iPad) is also much inproved in Beta 3, I have not had any problem with 'Lion'
Happy hunting!
john -
Background
all Server 2012 VMs...1 domain controller, multiple member servers. I have only one member server that is having DNS issues. The problem was first discovered while trying to gpupdate /force, which failed stating there's a lack of network connectivity
with the domain controller, event ID 1129. I looked in the event logs further and there were event ID 8020 "the system failed to register host (A AAA) resource records for network adapter with settings....", there were also events where the
time service could not sync with the DC.
From there I dropped the server from the domain, and then rejoined it without issue. It still was having the same errors. I looked in the DNS Manager on the DC, and the record with that IP address had the wrong host name. I deleted it,
and attempted to have the server register the record. I followed ipconfig /flushdns, and ipconfig /registerdns. Still having the same issues.
It is part of the domain, trust relationships seem fine. Any thoughts? I can't find anything anywhere on that event ID.Seems like too few info to decide what is your problem. My very first guess is that there is error in VM settings. Make sure that VMs has disabled time synchronization with host. Secon problem may stem from possible port blocking (try without fw) and third
problem in VM may be caused by wrongly setting IP DNS in NIC parameters.
Also start with dcdiag to find the health of AD. Do not remember to delete DNS cache whenever you do any chnages is DNS settings.
Here are references that may help:
https://technet.microsoft.com/en-us/library/cc727335(v=ws.10).aspx
If you use DHCP from network router (which is wrong configuration):
https://support.microsoft.com/en-us/kb/2459530
HTH
Milos -
Secondary DNS failing to redirect clients when Primary DNS goes down
I have a single domain with two Windows 2008 servers, DC1 (physical) and DC2 (virtual). Both servers run DNS and are GC servers, and the entire domain is on the same subnet (192.168.0.x).
All clients on the network are configured to use DC1 as primary DNS, DC2 as secondary DNS.
DHCP is enabled only on DC1. (This might be part of the issue, not sure).
The problem is that when DC1 goes down for a reboot or repair, we lose access to the internet from our clients. Trying to pull up any website results in a "Page cannot be displayed" error. DC2 is available during this time and can be
pinged from any client but does not resolve DNS requests, even if I specify it as the primary DNS server on one of my workstations. However I can log on to DC2 locally and browse the web.
Here are the results of a DCdiag /dnsall from DC2 (I bolded areas of concern):
Directory Server Diagnosis
Performing initial setup:
* Connecting to directory service on server DC2.
* Identified AD Forest.
Collecting AD specific global data
* Collecting site info.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=mydomain,DC=com,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
The previous call succeeded
Iterating through the sites
Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mydomain,DC=com
Getting ISTG and options for the site
* Identifying all servers.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=mydomain,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
The previous call succeeded....
The previous call succeeded
Iterating through the list of servers
Getting information for the server CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mydomain,DC=com
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
Getting information for the server CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mydomain,DC=com
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC2
Starting test: Connectivity
* Active Directory LDAP Services Check
Determining IP4 connectivity
Determining IP6 connectivity
* Active Directory RPC Services Check
......................... DC2 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC2
Test omitted by user request: Advertising
Test omitted by user request: CheckSecurityError
Test omitted by user request: CutoffServers
Test omitted by user request: FrsEvent
Test omitted by user request: DFSREvent
Test omitted by user request: SysVolCheck
Test omitted by user request: KccEvent
Test omitted by user request: KnowsOfRoleHolders
Test omitted by user request: MachineAccount
Test omitted by user request: NCSecDesc
Test omitted by user request: NetLogons
Test omitted by user request: ObjectsReplicated
Test omitted by user request: OutboundSecureChannels
Test omitted by user request: Replications
Test omitted by user request: RidManager
Test omitted by user request: Services
Test omitted by user request: SystemLog
Test omitted by user request: Topology
Test omitted by user request: VerifyEnterpriseReferences
Test omitted by user request: VerifyReferences
Test omitted by user request: VerifyReplicas
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
See DNS test in enterprise tests section for results
......................... DC2 passed test DNS
Running partition tests on : ForestDnsZones
Test omitted by user request: CheckSDRefDom
Test omitted by user request: CrossRefValidation
Running partition tests on : DomainDnsZones
Test omitted by user request: CheckSDRefDom
Test omitted by user request: CrossRefValidation
Running partition tests on : Schema
Test omitted by user request: CheckSDRefDom
Test omitted by user request: CrossRefValidation
Running partition tests on : Configuration
Test omitted by user request: CheckSDRefDom
Test omitted by user request: CrossRefValidation
Running partition tests on : mydomain
Test omitted by user request: CheckSDRefDom
Test omitted by user request: CrossRefValidation
Running enterprise tests on : mydomain.com
Starting test: DNS
Test results for domain controllers:
DC: DC2.mydomain.com
Domain: mydomain.com
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
Microsoftr Windows Serverr 2008 Standard
(Service Pack level: 2.0)
is supported
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000006] Intel(R) PRO/1000 MT Network Connection:
MAC address is 00:0C:29:91:59:68
IP Address is static
IP address: 192.168.0.249
DNS servers:
192.168.0.105 (DC1.mydomain.com.) [Valid]
127.0.0.1 (DC2) [Valid]
The A host record(s) for this DC was found
Warning: The AAAA record for this DC was not found
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.) - mydomain.com]
The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found primary
Root zone on this DC/DNS server was not found
TEST: Forwarders/Root hints (Forw)
Recursion is enabled
Forwarders Information:
192.168.0.105 (DC1.mydomain.com.) [Valid]
192.168.0.7 (<name unavailable>) [Invalid (unreachable)]
Error: Forwarders list has invalid forwarder: 192.168.0.7 (<name unavailable>)
TEST: Delegations (Del)
Delegation information for the zone: mydomain.com.
Delegated domain name: _msdcs.mydomain.com.
DNS server: DC1.mydomain.com. IP:192.168.0.105 [Valid]
TEST: Dynamic update (Dyn)
Test record _dcdiag_test_record added successfully in zone mydomain.com
Test record _dcdiag_test_record deleted successfully in zone mydomain.com
TEST: Records registration (RReg)
Network Adapter
[00000006] Intel(R) PRO/1000 MT Network Connection:
Matching CNAME record found at DNS server 192.168.0.105:
a32fcfbd-16bb-4697-a23d-20fc3b8c274c._msdcs.mydomain.com
Matching A record found at DNS server 192.168.0.105:
DC2.mydomain.com
Warning:
Missing AAAA record at DNS server 192.168.0.105:
DC2.mydomain.com
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
Matching SRV record found at DNS server 192.168.0.105:
_ldap._tcp.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_ldap._tcp.ac09921d-4553-475e-b25c-059742ac0552.domains._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_kerberos._tcp.dc._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_ldap._tcp.dc._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_kerberos._tcp.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_kerberos._udp.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_kpasswd._tcp.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_ldap._tcp.Default-First-Site-Name._sites.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_kerberos._tcp.Default-First-Site-Name._sites.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_ldap._tcp.gc._msdcs.mydomain.com
Matching A record found at DNS server 192.168.0.105:
gc._msdcs.mydomain.com
Warning:
Missing AAAA record at DNS server 192.168.0.105:
gc._msdcs.mydomain.com
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
Matching SRV record found at DNS server 192.168.0.105:
_gc._tcp.Default-First-Site-Name._sites.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.mydomain.com
Matching CNAME record found at DNS server 192.168.0.249:
a32fcfbd-16bb-4697-a23d-20fc3b8c274c._msdcs.mydomain.com
Matching A record found at DNS server 192.168.0.249:
DC2.mydomain.com
Warning:
Missing AAAA record at DNS server 192.168.0.249:
DC2.mydomain.com
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
Matching SRV record found at DNS server 192.168.0.249:
_ldap._tcp.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_ldap._tcp.ac09921d-4553-475e-b25c-059742ac0552.domains._msdcs.mydomain.com
Matching
SRV record found at DNS server 192.168.0.249:
_kerberos._tcp.dc._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_ldap._tcp.dc._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_kerberos._tcp.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_kerberos._udp.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_kpasswd._tcp.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_ldap._tcp.Default-First-Site-Name._sites.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.mydomain.com
Matching
SRV record found at DNS server 192.168.0.249:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_kerberos._tcp.Default-First-Site-Name._sites.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_ldap._tcp.gc._msdcs.mydomain.com
Matching A record found at DNS server 192.168.0.249:
gc._msdcs.mydomain.com
Warning:
Missing AAAA record at DNS server 192.168.0.249:
gc._msdcs.mydomain.com
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
Matching SRV record found at DNS server 192.168.0.249:
_gc._tcp.Default-First-Site-Name._sites.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.mydomain.com
Warning: Record Registrations not found in some network adapters
TEST: External name resolution (Ext)
Internet name www.microsoft.com was resolved successfully
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 192.168.0.7 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.168.0.7
[Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 192.168.0.105 (DC1.mydomain.com.)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
DNS delegation for the domain _msdcs.mydomain.com. is operational on IP 192.168.0.105
DNS server: 192.168.0.249 (DC2)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
Domain: mydomain.com
DC2
PASS WARN FAIL PASS PASS WARN PASS
......................... mydomain.com failed test DNS
Test omitted by user request: LocatorCheck
Test omitted by user request: IntersiteLooks like it may be trying to forward to a machine that's down (DC1 and another 192.168.0.7) and root hints aren't available.
Check out this article:
http://technet.microsoft.com/en-us/library/ff807391(v=ws.10).aspx
See if you can enable DNS access through the firewall to the Internet if it's not already available. Try to match whatever forwarder settings are on DC1, or remove them entirely and let the server resolve DNS from Internet root servers. Alternativly,
you could change your forwarder to a public DNS server you have access to, your ISP should supply this or you could test with something common like 4.2.2.2.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications -
DNS fails to resolve w/ 10.6.8
I have a home network consisting of 2 iMacs and 1 Macbook Pro, all running on 5 GHz N-band through an Asus RT-N56U dual-band router. The Macbook Pro and one of the iMacs are fine, however starting several months ago the third iMac began having a problem where it fails to resolve domain names, as many as 3 times a day. All 3 computers have identical network preferences, each with their own static LAN IP.
I looked through the Console logs for the problem iMac and found the same entries repeating, which appear to show mdnsResponder crashing:
mDNSResponder[18]
SendResponses: No active interface 0000000000000006 to send: 0000000000000000 08 41 _afpovertcp._tcp.local. PTR User's\032Computer._afpovertcp._tcp.local.
mDNSResponder[18]
SendResponses: No active interface 0000000000000006 to send: 0000000000000000 08 34 _rfb._tcp.local. PTR User's\032Computer._rfb._tcp.local.
mDNSResponder[18]
ERROR: handle_resolve_request bad interfaceIndex 6
com.apple.usbmuxd[37]
_BrowseReplyReceivedCallback (thread 0x7fff70463cc0): Error doing DNSServiceResolve(): -65540
mDNSResponder[18]
SendResponses: No active interface 0000000000000006 to send: 0000000000000000 04 15 User's\032Computer._device-info._tcp.local. TXT model=iMac10,1
/System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[102]
BonjourBrowser::DNSServiceQueryRecord returned -65540
mDNSResponder[18]
ERROR: handle_resolve_request bad interfaceIndex 6
com.apple.usbmuxd[37]
_BrowseReplyReceivedCallback (thread 0x7fff70463cc0): Error doing DNSServiceResolve(): -65540
mDNSResponder[18]
SendResponses: No active interface 0000000000000006 to send: 0000000000000000 04 15 User's\032Computer._device-info._tcp.local. TXT model=iMac10,1
mDNSResponder[18]
SendResponses: No active interface 0000000000000006 to send: 0000000000000000 08 34 _rfb._tcp.local. PTR User's\032Computer._rfb._tcp.local.
mDNSResponder[18]
PenaltyTimeForServer: PenaltyTime negative -154358, (server penaltyTime -58278099, timenow -58123741) resetting the penalty
mDNSResponder[18]
ERROR: handle_resolve_request bad interfaceIndex 6
com.apple.usbmuxd[37]
_BrowseReplyReceivedCallback (thread 0x7fff70463cc0): Error doing DNSServiceResolve(): -65540
mDNSResponder[18]
ERROR: handle_resolve_request bad interfaceIndex 6
com.apple.usbmuxd[37]
_BrowseReplyReceivedCallback (thread 0x7fff70463cc0): Error doing DNSServiceResolve(): -65540
mDNSResponder[18]
mDNSResponder mDNSResponder-258.21 (May 26 2011 14:40:13) stopping
mDNSResponder[18]
mDNSResponder mDNSResponder-258.21 (May 26 2011 14:40:13) starting
I did some Googling on the issue and came up with results similar to my problem, dating back as far as OS X 10.6.5, perhaps even earlier. Several people suggested killing/restarting mdnsResponder as a temporary fix using the following:
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
This appeared initially to be successful, however it turns out the fix is just that – temporary. DNS still breaks every day, leaving my iMac able to send and receive email, but unable to browse the Internet.Hi,
Regarding search domains - those are not directly responsible for your internet conectivity.
You can read what they are here:
http://support.apple.com/kb/HT4845
regarding the mdnsResponder
You can try dragging this file to the desktop & rebooting.
Machintosh HD/System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
This should clear the issue.
Please let me know how it goes. -
DNS Fails for NFS Server Shares
When I boot, I get a message that DNS has failed for the NFS server mounts, and the shares do not mount. The message says, "mount.nfs: DNS resolution failed for server: name or service unknown." I have to mount the shares myself. Then when rebooting, I get the same error saying it can't unmount the shares.
this is /etc/resolv.conf:
$ cat /etc/resolv.conf
# Generated by dhcpcd from eth0
# /etc/resolv.conf.head can replace this line
nameserver 208.67.222.222
nameserver 208.67.220.220
# /etc/resolv.conf.tail can replace this line
this is /etc/conf.d/nfs:
# Number of servers to be started up by default
NFSD_OPTS=8
# Options to pass to rpc.mountd
# e.g. MOUNTDOPTS="-p 32767"
MOUNTD_OPTS="--no-nfs-version 1 --no-nfs-version 2"
# Options to pass to rpc.statd
# N.B. statd normally runs on both client and server, and run-time
# options should be specified accordingly. Specifically, the Arch
# NFS init scripts require the --no-notify flag on the server,
# but not on the client e.g.
# STATD_OPTS="--no-notify -p 32765 -o 32766" -> server
# STATD_OPTS="-p 32765 -o 32766" -> client
STATD_OPTS=""
# Options to pass to sm-notify
# e.g. SMNOTIFY_OPTS="-p 32764"
SMNOTIFY_OPTS=""
Do I need to add some option to rpc.statd, or is there some other misconfiguration there? AFAIK it is the default. What else should I look at to fix this? I can ping the server by name, and log in with ssh by name, just fine. It's only the nfs that is failing with DNS.airman99 wrote:
Yahoo! Good news, I've finally solved the problem on my laptop. The message I was receiving turned out merely to be a network timing issue.
The error I was receiving was exactly correct and informative. When /etc/rc.d/netfs ran and executed a 'mount -a -t nfs...' the network was indeed NOT reachable. I am running networkmanager, and apparently during bootup, networkmanager gets loaded, but there is a delay between when networkmanager is loaded and when the network is available. In other words, networkmanager allows the boot process to continue before the network is available.
My daemons are loaded in this order (rc.conf):
DAEMONS=(syslog-ng hal dhcdbd networkmanager crond cups ntpdate ntpd portmap nfslock netfs)
Consequently, if I add a delay to /etc/rc.d/netfs to allow time for the network to come up, then when the NFS shares are mounted, the network is up. In my case I had to add a 3 second delay.
sleep 3
I'm sure this isn't the best way to solve the problem, by editing the system file /etc/rc.d/netfs, because the next upgrade where changes occur to netfs, my fix will get overwritten. But I'll keep it until I figure out the "right" fix.
The real solution is to not load networkmanager in the background, but to force startup to wait for the networok to be up before continuing.
there is the _netdev option you can use in fstab, but that doesn't always work:
http://linux.die.net/man/8/mount
_netdev
The filesystem resides on a device that requires network access (used to prevent the system from attempting to mount these filesystems until the network has been enabled on the system).
Alternatively, you could just add a cronjob to do a mount -a with a sleep 20 in there or something. You might have to play with the sleep value a little to make sure it's long enough -
I have an RV320 I am testing in order to determine if it's suitable for use in the company I work for. We have several remote offices, and will be using IPSEC tunnels, VPN for IT troubleshooting and other features.
Dynamic DNS is returning
"Authorization failed(username or password)." error, although I think it's properly configured and works on
error, although I think it's properly configured and works on other firewall/router units. I have reentered the user, password and domain several times, each time it returns the same error.
Can anyone provide insight into the problem?
I also notice the options do not seem to include any way to use a Custom DNS, that is instead of xxx.dyndns.org it would be myhost.TLD. We have a bunch of xxx.dyndns.org, but do have a few myhost.tld. I hope this is something that could be fixed.
Thanks,
JeffHi Jeff,
I think that the issue is that the PW is too long. I recall a case a while back where a customer had a passord over 20 characters and he had to shorten it. My recollection is not great, but I think that 18 was the limit. A feature request was made to lengthen the password field but no change was made due to hardware or maybe OS limitation. I think that the router was the RV042, which has similar code to the RV320. Sorry I can't be more specific. I would try changing the password at least temporarily to see if it works.
If you would like to make a feature request, please call support and open a case.
www.cisco.com/go/sbsc
- Marty -
Hi,
I was doing tests on my 11g R2 RAC. I wanted to simulate if DNS was down, what will happen. And, I got the following.
ERROR:
ORA-12545: Connect failed because target host or object does not exist
Enter user-name:
Anyone encountered this or have some workarounds to share?
Thanks.Hi,
there is some more information needed, to answer your question:
=> From where did you try to connect (Server/Client)?
=> What did you use as connect string?
=> If you used a TNSNAMES.ORA entry, how did that look like?
=> If you tried connecting to a normal VIP Hostname, the workaround would be /etc/hosts. How does /etc/hosts look like?
=> How did you simulate the DNS server down?
BTW: If you DNS is down and you try to connect via. SCAN an error is expected, since the SCAN name cannot be resolved (without a DNS).
Sebastian -
DNS fails using router IP address as DNS server address with static IP
This is my first experience with a Linksys router so it might be normal behaviour but just wanted to check. With a WRT54G2 router I have a few PC's I want to use static IP. Up till now with other brand routers including Belkin and Dlink, I have been able to just put the router IP address in as the address of the DNS server when I use static IP. This seemed to work initially with the Linksys but now for some reason, if I don't code the IP addresses of the DNS server provided by my ISP, DNS lookup fails. If I use DHCP for the PC's there is no problem.
Is that normal behaviour or is there something wrong I am doing?
Thanks
LarryI decided to upgrade my Linksys 54G router to a "Ultra RangePlus Wireless-N Broadband Router (WRT160N)Version 1" . I have had problems with the wireless (as far as I know just wireless portion) connection dropping. I have done some searching I was able to find some settings to try, and it did work better, but not for too long. I have this router within arm reach away, so it's not a distance issue. I have tried many things for about the last 6months or so.
As a last resort, and I do mean last resort and against my better judgement I purchased " Dual-Band Wireless-N Notebook Adapter (WPC600N) Version 1". I was hoping it was a compatibility issue, but there was no difference.
I have heard of trying older firmware, but I can't find any.
I have been a Linksys fan for quite sometime, but as of recently I am thinking of reconsidering if I can't get this resolved with out spending any more money. -
Local DNS server (corporate intranet) does not like Firfofox requests.
Intranet sites end up with:
Host Not Found
DNS error (the host name of the page you are looking for does not exist) or Server did not accept the connection.
Please check that the host name has been spelled correctly.
All external sites resolve correctly.
All internal sites can be pinged & reached with IE.
Problem stared after 3.6.7 update; 3.6.6 was ok. No changes made to corporate network.
What changed in 3.6.7 that affected DNS / authentication with local DNS?
== This happened ==
Every time Firefox opened
== 3.6.7 update; 3.6.6 was ok. No changes made to corporate network.You are not alone with issues related to the e1000e (but all they concluded was that reloading the module makes it work again):
https://bbs.archlinux.org/viewtopic.php?id=145564
It seems like this is more your issue:
http://permalink.gmane.org/gmane.linux. … devel/8932
But if none of those boot flags work for you, then there's not much you can do, and you'll have to write a script to reload the module each time after initial boot finishes I guess until the module gets fixed.
Also, power management of the PCIe interface causes the e1000e to shut off after a while as well (lots of people on CentOS noticing this):
http://serverfault.com/questions/226319 … ie-aspm-do
So you can use that boot parameter to stop that from happening, if that becomes an issue for you as well. -
This is the message I get when attempting to start:
The DNS server could not listen on Transmission Control Protocol (TCP) socket for address 0.0.0.0. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for use.
Restart the DNS server or reboot the computer.
and then:
The DNS server could not open socket for address 0.0.0.0.
Verify that this is a valid IP address for the server computer. If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces. Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error. In that case remove the DNS\Parmeters\ ListenAddress value in the services section of the registry and restart.)
If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.
I can't get to the properties of the DNS server to even see what address it's trying to bind to. Everything worked fine before a group of updates were installed. The machine is a SBS and has NAT to deal with the outside interface.
I have checked the DNS and there is no key for listenaddress in the DNS service. Also, in services, it says DNS is started, but I can't get into it. The DNS service MMC just has a red X through it.
Any ideas would be appreciated.Hello,
According to the description, the issue seems to be related to SBS 2003. As we mainly focus on the general question about Windows Server system, for better and quick answer to the question, it is recommend you initial a new thread in the SBS newsgroup to get further support.
For your convenience, I have list the link to the corresponding community as followed.
Discussions in microsoft.public.windows.server.sbs
http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.server.sbs
Hope the issue can be resolved soon.
This posting is provided "AS IS" with no warranties, and confers no rights. -
we have recently installed a RV042 V1.3 in our office and have been having a very frustrating time with internet access. It appears to be a DNS issue and is certainly the RV042 with the issue. When I connect directly or through our old Linsys 54G the problem goes away.
There are many sites that simply return not found error. This is intermittent sometimes a site is ok, other times not.
When I ping a site (for example right now I can not get to google.com) it returns with error. However a nslookup returns the IP no problem. Then half an hour later google will be ok and another address will have an issue. Grabbing the IP from nslookup and using it instead of the domain name results in fast and reliable internet access.
I noticed that this issue does not seem to be serious on our windows pcs. Actually, the way I am writing this note is from windows within my mac. Windows seems snappy and the mac browser crawls or simply 404s.
I have updated the firmware. Removed everything down to bare-bones (Only using WAN1) to try an isolate the issue...tried static DNS servers... but no luck.
I have done a lot of searching online and have come across others with the same issue however no solution.
I consider myself quite competent with this type of thing and am coming here after a lot of research and trying various things. I feel that I have tried everything and am about to get rid of the router - this is my last resort.
Any ideas?Hi mpyhala,
This problem also occurs in the previous firmware.
What type of internet connection do you have? = Cable Modem(WAN1) / ADSL(WAN2)
What is the MTU set at on the router WAN port? = 1500
What version of Mac OS is having the issues? = 10.6
Does the RV042 have the latest available firmware now? (v1.3.13.02) = 1.3.13.02-tm (Jan 28 2011 18:39:04)
thank you for attention
What type of internet connection do you have?
What is the MTU set at on the router WAN port?
What version of Mac OS is having the issues?
Does the RV042 have the latest available firmware now? (v1.3.13.02)
I will look into this some more and see if I can find a definite answer for you. -
Situation:
On our wifi iPhone/iPod Touch devices correctly receive DHCP information.
Access to the outside world works well with addresses resolving correctly.
However these devices cannot browse to internal names - only the underlying ip address.
Why?
Additional Info:
The DNS servers provided by DHCP are both internal.
Windows PC's using identical DHCP settings (served from the same server) resolve internal and external addresses successfully.
Changing the DNS servers to an external source is not an option as we want to use the Apple devices to access internal content.this sounds pretty much like my problem at http://discussions.apple.com/thread.jspa?threadID=2534692&tstart=0. Is it possible your internal DNS zone is called <something>.local?
-
This is a bit confusing, I have two main ways I access the wifi in the house, my iphone and an xp laptop.
Recently the laptop is giving the symptoms of the hub not connecting to the adsl, i give the hub a reboot and off we go again.
It is really disappointing to have reboot the router but the really wierd thing is my iphone happily uses the connection even when the laptop thinks it's broken!
(and before you ask, it is connected to the hub and it's 3g connection is off as I am on pay as you go)
has anyone come accross this, its not accptable to have to regularly reboot it.Hi back_ache,
I don't really think this would be a DNS issue. If your iPhone holds the connection but your laptop doesn't, the common denominator here would appear to be the laptop being at fault. What error messages do you get on the laptop when the connection drops/stops working? If it's something to do with limited/no connectivity, have you tried setting up a static IP on your laptop to see if it holds the connection? Let us know anyway - we might be able to help you sort this out
Dean
BTCare Community Mod
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’. -
Windows 7 Pro DNS issue with static IP
0
down vote
favorite
I have been unable to solve a DNS problem I am having as follows:
I have a Windows 7 Professional (64 bit) computer running VirtualBox with a couple of Windows XP guests (not sure if this bit is relevant). After heavy file copying/transfer on both of the Windows XP machines, both the guest machines AND the host loose anything
DNS related, so I cannot call anything by name, but by direct IP works fine. The only resolution is to reboot the (host) machine and it will then work OK for a while until it happens again. The only trigger to make it seem to happen quicker is to re-initiate
the heavy file transfer and this then causes the DNS resolution to stop working again.
The machine has a fixed IP address, so it isn't related to DHCP.
I've tried the machine connected wired and wireless, no difference.
The IP settings are manual and I have tried giving it the DNS settings of the router (normal settings) and I have also tried giving it Google's DNS servers (8.8.8.8 & 8.8.4.4). No difference.
It seems to happen (sooner) during heavy traffic.
Other Windows 7 machines in the network work fine (though they are Home version, not Pro).
ONLY DNS fails, direct IP works OK.
Reboot seems only solution at the moment.
I am now lost as to what to try to resolve this issue, I do not really want to reload Windows 7 as it is a relatively new install... I have read about issues with wired connections on my router (BT Home Hub 2.0) so tried a wireless connection, still the
same.
Here is my ipconfig /all (it shows the BT Home Hub router DNS settings, but it also failed with Google's 8.8.8.8 and 8.8.4.4 entered here and also with the routers 192.168.1.254 (default).
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\G>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : e1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 30-85-A9-AD-07-81
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::59f:484a:827f:42ba%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.87(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 238060969
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-2B-4D-30-85-A9-AD-07-81
DNS Servers . . . . . . . . . . . : 217.32.171.21
213.120.234.30
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-00-28-56
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8d2d:7418:381b:8dc0%15(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 336068647
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-2B-4D-30-85-A9-AD-07-81
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{486D4DCC-9CB7-417E-A796-596E0E6B1D54}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{67455999-75A5-436E-9EAC-12B093363132}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Users\G>
Any ideas where to look, or what other info to provide for any assistance?
Many thanks in advance.Hi,
This has just happened again, here is the content of the netstat results as requested...
If I kill the VirtualBox virtual machines, it starts working again. It is as if there are no ports left, but I am not occupying that many? Surely Windows 7 can cope with this?
I feel I am missing something important, but cannot put my finger on it...
Further below, I have re-run the netstat command AFTER I have closed the VirtualBox machines and the system works OK.
netstat results DURING ISSUE:
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING 1444
[FileZilla Server.exe]
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING 1692
[MESMTPC.EXE]
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
Can not obtain ownership information
TCP 0.0.0.0:110 0.0.0.0:0 LISTENING 1660
[MEPOPS.EXE]
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 752
RpcSs
[svchost.exe]
TCP 0.0.0.0:143 0.0.0.0:0 LISTENING 1524
[MEIMAPS.exe]
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
Can not obtain ownership information
TCP 0.0.0.0:1221 0.0.0.0:0 LISTENING 4796
[VirtualBox.exe]
TCP 0.0.0.0:2199 0.0.0.0:0 LISTENING 4820
[VirtualBox.exe]
TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING 1756
[mysqld.exe]
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 1104
CryptSvc
[svchost.exe]
TCP 0.0.0.0:6901 0.0.0.0:0 LISTENING 4636
[WinVNC.exe]
TCP 0.0.0.0:6901 0.0.0.0:0 LISTENING 4636
[WinVNC.exe]
TCP 0.0.0.0:8300 0.0.0.0:0 LISTENING 3464
[sc_serv.exe]
TCP 0.0.0.0:8301 0.0.0.0:0 LISTENING 3464
[sc_serv.exe]
TCP 0.0.0.0:8360 0.0.0.0:0 LISTENING 3080
[sc_serv.exe]
TCP 0.0.0.0:8361 0.0.0.0:0 LISTENING 3080
[sc_serv.exe]
TCP 0.0.0.0:9022 0.0.0.0:0 LISTENING 4804
[VirtualBox.exe]
TCP 0.0.0.0:9023 0.0.0.0:0 LISTENING 4804
[VirtualBox.exe]
TCP 0.0.0.0:9080 0.0.0.0:0 LISTENING 4804
[VirtualBox.exe]
TCP 0.0.0.0:10001 0.0.0.0:0 LISTENING 4828
[VirtualBox.exe]
TCP 0.0.0.0:10002 0.0.0.0:0 LISTENING 4828
[VirtualBox.exe]
TCP 0.0.0.0:10003 0.0.0.0:0 LISTENING 4828
[VirtualBox.exe]
TCP 0.0.0.0:10011 0.0.0.0:0 LISTENING 4780
[VirtualBox.exe]
TCP 0.0.0.0:10012 0.0.0.0:0 LISTENING 4780
[VirtualBox.exe]
TCP 0.0.0.0:10013 0.0.0.0:0 LISTENING 4780
[VirtualBox.exe]
TCP 0.0.0.0:25566 0.0.0.0:0 LISTENING 3648
[TerrariaServer.exe]
TCP 0.0.0.0:30001 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30002 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30003 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30004 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30005 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30006 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30007 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30020 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30021 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30039 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30080 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30081 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30082 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30083 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30084 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30085 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30086 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30087 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30088 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30089 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30090 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30091 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30092 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30093 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30094 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30095 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30096 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30097 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30098 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30099 0.0.0.0:0 LISTENING 4788
[VirtualBox.exe]
TCP 0.0.0.0:30101 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30102 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30103 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30104 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30105 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30106 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30107 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30108 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30109 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30110 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30111 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30112 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30113 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30114 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30115 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30116 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30117 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30118 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30119 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30120 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30121 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30139 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30180 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30181 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30182 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30183 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30184 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30185 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30186 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30187 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30188 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30189 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30190 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30191 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30192 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30193 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30194 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30195 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30196 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30197 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30198 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30199 0.0.0.0:0 LISTENING 4812
[VirtualBox.exe]
TCP 0.0.0.0:30201 0.0.0.0:0 LISTENING 4796
[VirtualBox.exe]
TCP 0.0.0.0:30239 0.0.0.0:0 LISTENING 4796
[VirtualBox.exe]
TCP 0.0.0.0:33306 0.0.0.0:0 LISTENING 4796
[VirtualBox.exe]
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 440
[wininit.exe]
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 880
eventlog
[svchost.exe]
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING 1000
Schedule
[svchost.exe]
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING 508
[lsass.exe]
TCP 0.0.0.0:49157 0.0.0.0:0 LISTENING 500
[services.exe]
TCP 0.0.0.0:49158 0.0.0.0:0 LISTENING 3048
PolicyAgent
[svchost.exe]
TCP 127.0.0.1:8361 127.0.0.1:49364 ESTABLISHED 3080
[sc_serv.exe]
TCP 127.0.0.1:14147 0.0.0.0:0 LISTENING 1444
[FileZilla Server.exe]
TCP 127.0.0.1:14147 127.0.0.1:49162 ESTABLISHED 1444
[FileZilla Server.exe]
TCP 127.0.0.1:49162 127.0.0.1:14147 ESTABLISHED 3156
[FileZilla Server Interface.exe]
TCP 127.0.0.1:49212 127.0.0.1:49213 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49213 127.0.0.1:49212 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49214 127.0.0.1:49215 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49215 127.0.0.1:49214 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49216 127.0.0.1:49217 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49217 127.0.0.1:49216 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49218 127.0.0.1:49219 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49219 127.0.0.1:49218 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49220 127.0.0.1:49221 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49221 127.0.0.1:49220 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49222 127.0.0.1:49223 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49223 127.0.0.1:49222 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49224 127.0.0.1:49225 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49225 127.0.0.1:49224 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49226 127.0.0.1:49227 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49227 127.0.0.1:49226 ESTABLISHED 4288
[java.exe]
TCP 127.0.0.1:49364 127.0.0.1:8361 ESTABLISHED 3100
[Instore_Radioboss.exe]
TCP 192.168.1.87:139 0.0.0.0:0 LISTENING 4
Can not obtain ownership information
TCP 192.168.1.87:3389 217.156.134.12:22971 ESTABLISHED 1104
CryptSvc
[svchost.exe]
TCP 192.168.1.87:8360 81.148.248.221:1026 ESTABLISHED 3080
[sc_serv.exe]
TCP 192.168.1.87:25565 0.0.0.0:0 LISTENING 4288
[java.exe]
TCP 192.168.1.87:50644 37.139.0.151:8233 ESTABLISHED 4796
[VirtualBox.exe]
TCP 192.168.1.87:51019 81.27.96.46:21 TIME_WAIT 0
TCP 192.168.1.87:53126 192.168.1.86:445 ESTABLISHED 4
Can not obtain ownership information
TCP 192.168.1.87:60462 192.168.1.86:445 CLOSE_WAIT 4
Can not obtain ownership information
TCP 192.168.1.87:65029 37.139.0.151:8231 ESTABLISHED 4796
[VirtualBox.exe]
TCP 192.168.56.1:139 0.0.0.0:0 LISTENING 4
Can not obtain ownership information
TCP [::]:21 [::]:0 LISTENING
1444
[FileZilla Server.exe]
TCP [::]:25 [::]:0 LISTENING
1692
[MESMTPC.EXE]
TCP [::]:80 [::]:0 LISTENING
4
Can not obtain ownership information
TCP [::]:135 [::]:0 LISTENING
752
RpcSs
[svchost.exe]
TCP [::]:445 [::]:0 LISTENING
4
Can not obtain ownership information
TCP [::]:3306 [::]:0 LISTENING
1756
[mysqld.exe]
TCP [::]:3389 [::]:0 LISTENING
1104
CryptSvc
[svchost.exe]
TCP [::]:30239 [::]:0 LISTENING
4796
[VirtualBox.exe]
TCP [::]:49152 [::]:0 LISTENING
440
[wininit.exe]
TCP [::]:49153 [::]:0 LISTENING
880
eventlog
[svchost.exe]
TCP [::]:49154 [::]:0 LISTENING
1000
Schedule
[svchost.exe]
TCP [::]:49156 [::]:0 LISTENING
508
[lsass.exe]
TCP [::]:49157 [::]:0 LISTENING
500
[services.exe]
TCP [::]:49158 [::]:0 LISTENING
3048
PolicyAgent
[svchost.exe]
TCP [::1]:14147 [::]:0 LISTENING 1444
[FileZilla Server.exe]
UDP 0.0.0.0:123 *:*
964
W32Time
[svchost.exe]
UDP 0.0.0.0:500 *:*
1000
IKEEXT
[svchost.exe]
UDP 0.0.0.0:3702 *:*
964
EventSystem
[svchost.exe]
UDP 0.0.0.0:3702 *:*
964
EventSystem
[svchost.exe]
UDP 0.0.0.0:4500 *:*
1000
IKEEXT
[svchost.exe]
UDP 0.0.0.0:5355 *:*
1104
Dnscache
[svchost.exe]
UDP 0.0.0.0:53274 *:*
4780
[VirtualBox.exe]
UDP 0.0.0.0:53727 *:*
4788
[VirtualBox.exe]
UDP 0.0.0.0:54111 *:*
4828
[VirtualBox.exe]
UDP 0.0.0.0:54112 *:*
4828
[VirtualBox.exe]
UDP 0.0.0.0:54113 *:*
4780
[VirtualBox.exe]
UDP 0.0.0.0:55421 *:*
964
EventSystem
[svchost.exe]
UDP 0.0.0.0:58596 *:*
964
EventSystem
[svchost.exe]
UDP 0.0.0.0:59838 *:*
4812
[VirtualBox.exe]
UDP 0.0.0.0:62498 *:*
4796
[VirtualBox.exe]
UDP 127.0.0.1:1900 *:*
4172
SSDPSRV
[svchost.exe]
UDP 127.0.0.1:55045 *:*
4172
SSDPSRV
[svchost.exe]
UDP 192.168.1.87:137 *:*
4
Can not obtain ownership information
UDP 192.168.1.87:138 *:*
4
Can not obtain ownership information
UDP 192.168.1.87:1900 *:*
4172
SSDPSRV
[svchost.exe]
UDP 192.168.1.87:55043 *:*
4172
SSDPSRV
[svchost.exe]
UDP 192.168.56.1:137 *:*
4
Can not obtain ownership information
UDP 192.168.56.1:138 *:*
4
Can not obtain ownership information
UDP 192.168.56.1:1900 *:*
4172
SSDPSRV
[svchost.exe]
UDP 192.168.56.1:55044 *:*
4172
SSDPSRV
[svchost.exe]
UDP [::]:123 *:*
964
W32Time
[svchost.exe]
UDP [::]:500 *:*
1000
IKEEXT
[svchost.exe]
UDP [::]:3702 *:*
964
EventSystem
[svchost.exe]
UDP [::]:3702 *:*
964
EventSystem
[svchost.exe]
UDP [::]:4500 *:*
1000
IKEEXT
[svchost.exe]
UDP [::]:5355 *:*
1104
Dnscache
[svchost.exe]
UDP [::]:55422 *:*
964
EventSystem
[svchost.exe]
UDP [::]:58597 *:*
964
EventSystem
[svchost.exe]
UDP [::1]:1900 *:*
4172
SSDPSRV
[svchost.exe]
UDP [::1]:55042 *:*
4172
SSDPSRV
[svchost.exe]
UDP [fe80::59f:484a:827f:42ba%11]:1900 *:*
4172
SSDPSRV
[svchost.exe]
UDP [fe80::59f:484a:827f:42ba%11]:55040 *:*
4172
SSDPSRV
[svchost.exe]
UDP [fe80::11a6:2283:bc40:c0cb%16]:1900 *:*
4172
SSDPSRV
[svchost.exe]
UDP [fe80::11a6:2283:bc40:c0cb%16]:55041 *:*
4172
SSDPSRV
[svchost.exe]
Maybe you are looking for
-
Will nokia 301 work with the old PC suite?
Hi, I am planning to buy Nokia 301(Dual sim varient), i am more concerned about Nokia PC suite connectivity over blue tooth (PC suite -(v.7.1.180.94) and Not Nokia suite). Can you please tell will nokia 301 work with the old PC suite or not.? and btw
-
Any solution for H264 thumbNail problem
Hi All I am trying to display thumbnail using netStream and H264 video for one of my course. but it results Blank For more detail about the Issue (Locked by some one else) http://bugs.adobe.com/jira/browse/FP-132 Any help regarding this is highly app
-
When i add a cd to my library and then try to up load it in match my itunes shuts down
when i add a cd to my library and then try to up load it in match my itunes shuts down with a error message saying itunes has stop working and windows is shutting it down. HELP
-
Can't Synq iPhone 3GS Calendars after installing iOS6, any suggestions?
Can't Synq iPhone 3GS Calendars after installing iOS6, any suggestions? I'm all mac-based and followed the instructions for the upgrade to iOS6 software for iPhone but now my calendars won't synq. When I connect to iTunes and run the synq process, i
-
Getting contacts from iphone onto new macbook
I am having a problem getting all my contacts from my iphone to my new computer. I lost my last computer. I do have mobileme and have synced all my contacts from my phone to mobileme. In setting up my new computer, i went into system preferences to m