O2 network dropping out

Is anyone else having problems with the o2 network dropping off regularly from their i-phone? I have spoken to o2 and they say i have to send the phone back to apple!
Someone has just told me that you can download a repair??? Does anyone know anything about it? Help I'm due to leave the country next week and dont have time to send my phone away and get it back before I leave.

tb64,
You can try updating to iPhone firmware 1.1.4 to see if it helps resolve your issue if you haven't already.
Connect your iPhone to your computer, open iTunes and click "Check for Update".
Hope this helps,
Nathan C.

Similar Messages

HT204406 When I activate iTunes Match it goes through the process of analysing my library, then it matches a few songs but always then stops stating that the network dropped out - any ideas?

When I activate iTunes Match it goes through the process of analysing my library, then it matches a few songs but always then stops stating that the network dropped out - any ideas?

Bstarling wrote:
I am unable to write down because the log is moving too quickly.
Well, you don't have to write down anything. Just click on the message and copy it. Then paste it here, or in a text editor (eg, TextEdit). And you can enter a string like "Audio CD" (w/o the quote marks) in the filter and see only messages containing it.
mds[71]: (Error) Server: Failed to register path "/Volumes/Audio CD"
That's the metadata server, used by Spotlight. AFAIK, Spotlight does not index audio CDs, so what is this about? I don't know. Maybe it's the cause of what you observe; or maybe it's another symptom. Thinking again of the network issue… have you maybe installed some third-party software related to both Spotlight and the network (Searchlight perhaps)?

S20 Lan Network drops out after Windows 10 upgrade

Upgrade went ok and everything seems to work ok, but the network drops out after some downloads. Adapter gets disabled and cannot be enabled unless i perform a reboot. The network adapter is a Broadcom NetXtreme Gigabit Ethernet. Installed the latest Lenovo System Update but that did not find any new drivers.

The network speed went down from approx 50 Mbps to 1.8 Mbps after the upgrade! So it is surely a network driver problem.

After Effects CS4 and NFS Network Drop-Outs

Hi all,
We're experiencing a high number of NFS drop-outs ever since we've upgraded our department to AE CS4. I'm not saying CS4 is the culprit, I'm just saying this is when we started noticing the issue.
13 Apple MacPro 8-core systems. 12 Leopard, 1 Snow Leopard.
Projects are located on an Apple XServe 2.26 Quad-Core Xeon with 12GB RAM running 10.5.8 Server
Projects are shared up via NFS protocol via gigabit network.
Basically throughout the day, a random number of peole will lose connection to the NFS share, to which it returns on its own in a few moments. Though it's not everyone each time, all users encounter the issue at least once-a-day, usually more. (We have to different servers with NFS shares, one does not drop, the other does) The server that drops the share is the newer XServe Leopard and is the primary server where all the footage and projects are located. The 2nd server is just secondary library media and stock footage...
Essentially, I'm curious if anyone else is having NFS issues since the update to CS4. I'm just trying to weed out all elements. It's hard to say if it's the server itself, as the logs only note a drop once-in-a-while... We also use Rush Rendering for our Maya renders, which we have just upgraded to the latest version and we get drops even when no one is using Rush or Maya...
Very strange but extremely frustrating issue. It's not fun when someone is working on a project and loses it because the share drops out.
Any input greatly appreciated. Let me know if you need more info.
Thanks!

Session timeouts.... I really do think it's the server. AE doesn't care for specific network stuff, it's all just volumes/ drives to the program. To avoid these issues, you would have to shorten the refresh cycles on your server availability broadcasts or the "keep alive" cycles on the connection/ session settings themselves. I'd know how to do it on Win Server, but I have no clue with regards to XServe configuration. Still, certainly some simple console commands and a restart of the server software should be able to take care of the matter.
Mylenium

Network drops out on wrt54GL

Im trying to attach a addonics NAS adaptor to my wrt54gl. Point is, it drops off the network after a few minutes, requiring a power reset to get it to work again. My old desktop and new laptop seem to work ffine on wireless (both), but the wired addonics box doesnt.
Anything known? Firnmware on the wrt is 4.30.7, which is within 0.00.02 of being up to date...
Id welcome any suggestions..

Seems to vary, unfortunately. The ping below illustrates the issue. The power was cycled in the middle. The default ping interval appears to be only about a second.
C:\Users\us>ping -t backup
Pinging backup [192.168.1.101] with 32 bytes of data:
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=627ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=2ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.100: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.1.100: Destination host unreachable.
Request timed out.
Reply from 192.168.1.100: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.101: bytes=32 time=2ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=772ms TTL=32
Reply from 192.168.1.101: bytes=32 time=15ms TTL=32
Reply from 192.168.1.101: bytes=32 time=4ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=2ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=7ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=4ms TTL=32
Reply from 192.168.1.101: bytes=32 time=18ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=2ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=2ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Reply from 192.168.1.101: bytes=32 time=1ms TTL=32
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.100: Destination host unreachable.
Ping statistics for 192.168.1.101:
Packets: Sent = 119, Received = 99, Lost = 20 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 772ms, Average = 24ms

Wireless network drops out on one MBP, not the other

I have two Macbook Pros as part of a wireless network (Extreme/Express 802.11g). Lately the older of the MBPs (2.16 Core Duo) keeps losing the connection and won't recognize the network. If I restart the Airport Extreme and my modem and the MBP it will sometimes come back. Meanwhile my brand new MBP never loses the connection.
Anybody have any suggestions on where I can start looking or what I can start adjusting to eliminate this problem? Please don't hesitate to let me know if there's other info I can provide to help solve this.
Thanks in advance.

If you place the two MBPs side by side for a few hours, does the older device still lose the wireless signal while newer one remains connected?
If yes, then you may have a wireless card that is starting to act up or the internal antenna connector may be making intermittent contact. A repair shop will need to check things out.
If no, then you're likely picking up some form of wireless interference in the area where the older MBP is normally located. The usual culprits are a cordless phone (sometimes at the neighbors) and nearby wireless networks. Post back for a few suggestions on this.

DONT update to OSX Mavericks. Network drop out since update....

Hey Guys,
Ever since i updated to OSX Mavericks i have been having problems with my network.
Before the update i could stream directly from my USB HDD thats connected to my airport extreme with absolutly no problems at all..
Since the update it has turned to sh**.. sometimes i can connect to the apple tv and sometimes i cant. If i can connect to the apple TV or even my Pioneer Receiver which has airplay built in, when streaming is doenst keep up. it will work for 5 secs then stops. if i walk more then 7metres away with either my Mac or iphone it completely cuts out.. then it wont connect.. streaming from the USB (that connect to the Airport extreme) doesnt work anymore. it just keeps trying to load but doesnt do anything..
this has only started to happen since the mavericks update a few months and im over this problem......
please help..
cheers

To help determine the possible causes of this behaviour read the following.
EtreCheck will not fix anything, but it will provide additional information required to advance troubleshooting:
Apple Support Communities contributor etresoft wrote a very useful app to quickly gather certain system information that may help point to a cause of this problem. Go to his website, download and run EtreCheck:
http://www.etresoft.com/etrecheck
Etrecheck will be in your Downloads folder. Open it from there. You may see the following dialog box:
Click Open - etresoft contributes to this forum frequently and can be considered a trustworthy developer.
It will take a moment to run as it collects its data.
Copy and paste its output in a reply.
Do not be concerned about anything that says "Problem" or "failed".
EtreCheck was designed to remove any personal information (such as your computer's name and serial numbers) but if you see anything that looks like an email address or any other personal information that should not be divulged to others, please delete or obscure that information when you post the reply.
When you are finished with EtreCheck, quit the program. It occupies very little space, and you can keep it or drag it to the Trash as you wish.

Network drop out with Apple TV2

OK, so let me describe the situation and symptoms that I am currently experiencing....
Recently I just purchased a MacBook PRO and so with that wanted all the accessories etc. etc. Just a couple of days ago purchased an ATV2. It sets up on the network fine, can see my computer and library all fine. I can stream from YouTube on the ATV2 and also watch trailers etc. However, when I goto my library and select something like a song or a movie, it loads... brings up the next screen, which is like the now playing screen, then goes back to the main menu page detailing that the ATV2 is not connected to any network... happens every time, I have not been able to listen to or watch one single thing. Really got me stumped.... would love some suggestions....
MacBook PRO - 2.3 GHz Intel Core i5 - 4GB RAM, 1333 MHz DDR3 (MAC OS X - 10.6.7)
Apple TV V.2 - OS 4.0
Router is a D-Link - DI-524 - Air Plus G - 802.11G - 2.4GHz Wireless Router

I'm going to update the ATV 2's OS from 4.0 and go from there..... after reading a few different threads in the support forum, it seems not to be a router or network issue.... would still love to know and here any insight from people that have experienced this problem and what they did to get through... thanks

Windows 2008 R2, Network drops even after rebuild, Please help to diagnose

Hi there,
I've had an issue for a while now and I have been working through it and I'm getting lost and starting to go around in circles.
I have just rebuild up a Server 2008 R2 x64
Configuration is
Server: HP Prolient ML330 G6 Quad core xeon 24GB ram (between 2-3 Years Old)
HDD: Raid1 500GB
ip: 192.168.1.253
su: 255,255,255.0
gw: 192.168.1.1
dns 1: 192.168.1.253 (Was 127.0.0.1) please read on!!!
dns 2: empty
Roles and SW: AD DC, DNS, DHCP and Exchange Server (in 1 box)
My original issue was network dropping out every few weeks, progressively got worse to being daily. Restarts would fix it, tho would disconnect after hours or a day or 2.
Issues would be that during a network outage, I cannot connect workstations to domain, no network shares. Internet was dead, and a heap of Event ID errors
Server rebuild went well, It's a 2008 R2 setup and it runs basically everything in 1 server 2008 R2.. I know its not ideal but it's what they had setup previously.
So After rebuild I was using it for hours and hours and configuring, adding, cleaning, updating. All was good.
I was restoring of some emails and system was loaded medium to high for a while.
I went home thinking all was good and might connect via VPN and do some work and monitor it all, The vpn disconnected after a few minutes.
I called their office and asked is all normal?
They said network shares and emails have stopped. I confirmed this as the network would do the same thing it was doing before the rebuild.
So I restarted the server and Internet/Network drops within minutes of being restarted. tried many things to solve this..
hours later I installed known hotfixes, updated drivers, and tried so many other things to try and solve this...
I had heaps of Event ID errors before the rebuild, and trying to ping anyone was resulting in General Errors, and cannot ping basically
After the rebuild it has same sorts of event id errors. I had same general errors when trying to ping.
In the end at 2am 2 weeks ago, I finally got it running smoother..
I did 2 things which have made the network last longer then few minutes...
1. Disabled the Network Port 1 and Enabled the 2nd Port. (Both On board FYI)
2. Changed DNS in the TCPIPv4 from 127.0.0.1 to (192.168.1.253 (Servers IP))
Since this change, I no longer get event ID errors.
When network stops working the network icon stays normal.
And network is lasting days rather then hours.
Things I've spoken to others about,
- 127.0.0.1 and changing to 192.168.1.253 these 2 are basically the same both being loopback to server. They both point to itself..
- The fact the problems reappeared after a rebuild points towards hardware
- I think the summer heat might have cooked the NIC :p as same day the server crapped itself my clients home wifi setup also died. The range extender died! weird coincidence
- So I am seriously thinking it cannot be the DNS IP Configuration setting, I know that running all roles on a single server is hard for a server. But I find it hard to believe it was the DNS which caused this error
I have continued to work on this issue through the weeks.,
The following information is newest
28th March,
After 2 days of sweet operation.. IE Just after the switch to 2nd port.
The server's network went down..,
I can ping only 127.0.0.1 or 192.168.1.253 ok
but ping gateway or workstations times out.
Netstat shows heaps of ipv6 and very few ipv4 addresses
I restarted the server, applying computer settings sat there for a while..
dunno if it was coincidence or not but unplugging the Gateway and replugging it made the CTRL-ALT-DEL come up right away.
after boot everything has been ok for 14 hours now...
Now the Network Ports (2 of them are on the server, most likely sharing controller)
Please take a look at my ping/netstat and please make any comments.
----- Ping.txt -----
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Administrator>ping 192.168.1.253
Pinging 192.168.1.253 with 32 bytes of data:
Reply from 192.168.1.253: bytes=32 time<1ms TTL=128
Reply from 192.168.1.253: bytes=32 time<1ms TTL=128
Reply from 192.168.1.253: bytes=32 time<1ms TTL=128
Reply from 192.168.1.253: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.253:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\Administrator>ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\Administrator>ping google.com
Ping request could not find host google.com. Please check the name and try again
C:\Users\Administrator>netstat
Active Connections
Proto Local Address Foreign Address State
TCP 192.168.1.125:6008 192.168.1.118:49683 ESTABLISHED
TCP 192.168.1.253:6008 192.168.1.120:55103 ESTABLISHED
TCP 192.168.1.253:6008 192.168.1.121:49703 ESTABLISHED
TCP 192.168.1.253:6674 WORK-SERVER:19928 TIME_WAIT
TCP 192.168.1.253:19928 WORK-SERVER:6674 TIME_WAIT
TCP [::1]:389 WORK-SERVER:6012 ESTABLISHED
TCP [::1]:389 WORK-SERVER:6013 ESTABLISHED
TCP [::1]:389 WORK-SERVER:36939 ESTABLISHED
TCP [::1]:6012 WORK-SERVER:ldap ESTABLISHED
TCP [::1]:6013 WORK-SERVER:ldap ESTABLISHED
TCP [::1]:36939 WORK-SERVER:ldap ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:135 WORK-SERVER:19932 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:135 WORK-SERVER:32574 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:135 WORK-SERVER:35314 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:135 WORK-SERVER:35353 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:135 WORK-SERVER:56321 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:135 WORK-SERVER:64583 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:6684 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:6685 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:6686 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:6687 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:6689 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:6692 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:6694 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:6712 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:6765 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:17256 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:17327 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:19074 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:19075 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:19077 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:19896 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:19902 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:24754 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:36936 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:36944 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:36946 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:41165 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:56317 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:56319 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:59239 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:59243 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:59244 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:59245 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:59258 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:59262 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:59263 ESTABLISHED
TCP [fe80::9142:b19d:a6d0:d31d%14]:389 WORK-SERVER:59327
A HEAP MORE IPv6 but msg too long
I have noticed currently using the Cisco Gigabit switch the network will last 24-48 hours.
3th April
I have tested a 10/100 16port netgear and the network lasted for 5+ Days.
8th April
I noticed network and sharing centre icon has no exclaimation mark looked normal.. so on server I tried to open google website.
Nothing....
I pinged loopback. was ok
Ping the modem and not ok.
So I restarted the adsl modem. Within a minute server resumed internet..
I am unsure if the router caused this dropout. And my thinking spans now using a maximum speed of 100mbps it has taken 5 days to drop. WHY is this?
Either the modem is causing this. Or its the server nic running at only 100mbps
Does it make any sence?
Can a nic on server cause a drop only to restart the gateway to make it startup again.
From my post do you think the port on the gateway is flaky? As you said maybe too much for it to handle.
The modem has 4 lan ports.
Would it make sence to connect more than 1 lan cable from switch to modem?
Thankyou
Cheers

Make sure you have the latest ROM bios and proliant support pack.
http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdHome/?sp4ts.oid=3948599&spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3DswEnvOID%253D4064%257CswLang%253D%257Caction%253DlistDriver&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken
Install the rom bios, then easiest to boot the HP smartstart to prepare for operating system deployment, then install the complete PSP next.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

SCCM remote control keeps dropping out when another network adaptor loses connection

Hey guys,
Hopefully someone will be able to help me out
at work, we are running SCCM 2012, and I use SCCM 2012 config manager to manage the clients etc
We have a particularly annoying issue with SCCM remote control; it constantly drops out when a network connection on the client machine disconnects or changes state, even if its not interface I'm remote controlling through
Here's an example for you:
a laptop with a wired, and wireless connection:
I remote control the machine through the wired network address (lets say 192.168.0.1), but if the wireless connection drops out (someone turns it off or it breaks) the remote control client will kick me off, lock the screen, and I have to wait 20-30 seconds
before it will accept my connection again
This happens with any network adaptor that's installed on the client
Here is a copy of the logs re-creating this issue: https://www.dropbox.com/s/nu4w28d44xky3rg/CmRcService.log
(I've edited it to take out usernames and IP addresses as they are publicly accessible)
So my question, does any one know how to fix this issue? I see it uses WMI, is there anyway to get WMI to ignore an interface?
Thanks heaps,
Harry

This is going to be done by design for security reasons. If the network connect for whatever reason is down the pc will automatically be locked.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

While using the computer the wi fi dropped out and it can longer find any networks. I have played around with the air port etc , still have no networks and can't connect to internet. Please help

Hi I am having Wi fi connectivity issues , while using my computer the wi fi dropped out , I can no longer connect and no networks come up. I have tried looking into the air port, trying manually to connect to the desired network with no success , it says the Wi fi is turned on. I am at a loss to why it will no longer connect, please if you have any suggestions,as I tried to ring apple support but my warranty has expired this is my first major issue since I purchased it in 2009.
Thanks

My 4s i-phone which is 2 years old cannot find any wi-fi networks not even my home network... I had the same problem two months ago but i turned off the i-phone for 8 hours and then it was okay... Now it happened again.... I tried to restart the modem but whilst my laptop is connected regularly, my phone still cannot find any wi-fi networks... I restart the i-phone, i reset it, i chose reset network settings, reset all settings, i turned it off for a whole day in case it was overloaded, i turned on the airplane mode and turned it off again, i put it into the freezer for 10 minutes within a zipped bag but 3 days now and i still cannot be connected to my home wifi... I went to the technician today and he told me that it means that wi-fi is broken and that i need to change it with a charge of 70 euro but i have to give my phone for 10 working days so as to be fixed... I am so frustrated and i don't know if i want to give 70 euro for wifi since i don't know if it would make the same problems again...

TS1424 When I ave network coverage, my wi if drops out. I am only able to access my music on my phone when I have no network signal, otherwise all songs are greyed out

I can only access my wi if, when I have no network signal. As soon as I move to a better signal area, my wi Di connection drops out.
I have music on my phone, but again, I cannot access this in the gym, when I have a network signal.
I also cannot access some of my apps, as they are greyed out. Please advise

Grey text when you look at the content and a lock symbol at the bottom of the screen just indicates that the iPod is set to sync automatically with iTunes. If you want to connect an iPod to multiple computers, play the iPod songs through iTunes, delete songs from the iPod, drag songs from iTunes, add playlists to the iPod etc. you need to change the update setting to "manually manage songs and videos". The text will change from grey to black and everything will be directly accessible through iTunes:
Managing content manually on iPod
Using iPod with Multiple computers
Syncing Music to iPod
Something to remember about using an iPod in manual mode is that the "Do Not Disconnect" message will remain on the display until you physically eject the device: Safely Disconnect IPod

"NETWORK CHANGE DETECTED" - Broadband dropping out

About 4 to 5 weeks ago I started finding my broadband connection would just 'drop out'.
I'd lose it. No email or internet browsing, nothing.
It might come back on it's own, it might not.
Generally I'd run diagnoistic's, and some time sit would come back immediately, some times I'd have to run it a few times
Sometimes I'd give up and walk away.
Often I get the message "NETWORK CHANGE DETECTED", and the connection would re-establish itself.
It may run for minutes, and I'd be back at square one, or it could run OK for days.
All extremely frustrating.
I've read past posts and see that this problem has come up before, but I cannot find a "do this to fix it" resposnse.
Seeing that it's happened to others, I'm hoping it's something Apple can advise on.
Does anyone know why this happens and how to fix it. I'm really at my wits end.
I've been in contact with my internet provider who give me the usual answers.
Mac-Mini (2.4Ghz Intel Core 2 Duo) running OS 10.6.7
8Gb Ram
Netcomm Modem NB6PLus4W
Broadband ran fine from Late December 2010 until mid may 2011. No idea whats cause this issue.
Thanks all.
Robert

This is interesting I just put up my first question to the community also with these things in common
I am in Australia
with TPG on ADSL2+
I have a netcomm NB14WN wireless router
mac version 10.6.7 then updated to 10.6.8 - hasnt made any difference.
since I joined with TPG I have also had at first very slow and unreliable speeds (worse than dial up) and several nights a week it would repeatedly disconnect and the network change detected.
So since numerous discussions with tpg and several 'rebooting' everything they had a level 2 engineeer check and update the servers and now with the ethernet cable it is stable and fast ( same bandwidth and speed test every time). What I still have at this stage is an unreliable wireless connection and we have checked for interference in the house etc and now they have finally sent me a replacement modem to see if that makes a difference (should pick it up tomorrow). The problem is that some days the wireless is fine and somedays it isn't. It played up again two hours ago - put on the ethernet cable and it was fine, took the cable off a couple of hours ago and the wireless is fine at present whilst I am typing this......So will let you know how the other wireless router goes - apparently they check this one before they send it out but this one is from Netcomm also - I wonder if it is that - my dad and I looked it up on the net and it only sells for $100AUS which is pretty cheap - when I touch it underneath it is also very hot.

Airport network music play drops out/in on Yosemite

I've been playing music throughout my house using 2 Airport Express on the same Airport network for years. Occasionally music would drop out but would recover by itself, and since it didn't occur very often, it was okay. However after upgrading to Yosemite and then upgrading to the latest version, music now drops out 1-3 per min on the same network with the same Airport Express devices - So frequently that it was virtually unlistenable. I was not expecting services to get worse with the OS upgrade. Is there a fix or workaround for this, or do I need to wait until the next "upgrade"? Thanks.

I'm having a similar problem.
Since my upgrade to Yosemite connecting to Airplay audio is much harder, have to try up to four times on occasion (error message: cannot connect to Airplay). It also disconnects in between songs on Itunes and in between videos on Youtube or different files elsewhere. Strangely when I get it working, it does not often drop out in the middle of a file.
I know I have quite some interference at my place of other routers (I bought the AP for this reasons), but I did not have this problem at all with Mavericks. As my WiFi in general also seems less stable, I definitely think this is related to the dreaded Yosemite WiFi issue. Glad to hear any suggestions, otherwise I hope 10.10.2 will fix this.
Gear:
Macbook Pro Mid 2012 // i7 2.9ghz // 8GB

Adding AE to network via Ethernet...trying to fix airtunes drop outs....

I have a older Time Capsule (not simultaneous dual band) in my home office, and two older AE's (not N) that I use to wirelessly extend my network. Overall it works OK, though maybe not as speedy as it could be.
Lately, my airtunes streaming has been a bit erratic. Sometimes it works fine, other times it has a lot of drop outs. I use airtunes on both my AE's. On my "living room" AE, I use a digital connection to a high end DAC/preamp. On my "garage" AE I use an analog connection to a boombox. Both these setups experience intermittent dropouts.
I could use ethernet to connect my living room AE to my LAN, since I have a wired connection at that location. I can not do that on my garage AE.
First question is would a wired connection be more stable for airtunes? Since this problem may be associated with the Snow Leopard upgrade....I wonder if I'm wasting my time on the specifics of the network.
Second question: when I tried to set up the AE for a wired connection, It doesn't give me the "extend the network via ethernet" option in Airport utility. It only gives me the "extend network wirelessly" option. I moved the AE to the office and connected it directly to the time capsule (to make sure the wired network wasn't the issue) and I still am not given the option to do that.
Thoughts?
Thanks
Fabian

Inkjet....
Thanks for that tidbit. I'll try to remove my wireless AE from the loop and see if the wired AE works any better.
I'm getting the feeling though that this is an iTunes/OS issue, not a network issue. Reading the other threads on this topic seem all involve the upgrade to SL and/or iTunes 9.
As an aside, since my original post on this, I've replaced both the older AE's with the new n versions. I still use the older TC.
Also, I've used AirRadar to examine the "interference" issue. It shows very low levels of interference (though I'm not sure what is acceptable). No other local networks show up which are on the channel I'm using. Again, I just don't think its the network.
Finally, I don't think I'll go to the powerline transmission route. If wired were the answer, I'll find a way to get ethernet to the second AE. However, it needs to be the answer before going through the exercise.
Fabian

O2 network dropping out

Similar Messages

Maybe you are looking for