Mysterious Network Outage

New iMac about two weeks ago although I don't think it's part of the problem. My home Airport wifi network has been in place for almost five years with no problems. Two Airport Expresses - one main and one "slave" connected to my stereo to play iTunes music.
About the time the iMac went in (replacing early iMac G5 without camera), the network started to act up. It would just stop working for no apparent reason, two or three times a day. If I launched Airport Admin Utility to try to troubleshoot, most of the time it could not detect either of the Airports when it scanned the network. (This was true if I ran Airport Admin Utility on the iMac or on my MacBook.) Sometimes if I turned off the Airport card on the iMac and turned it back on again it would fix things, but usually not. Most of the time, if the network was detected when I did that, it would ask for the network password, and then wouldn't accept the correct password when I'd enter it.
If I clicked the "show password" box on the login dialog, what I saw was puzzling: if the correct WEP password was "ABC" the password that showed was "3A3B3C." The password is the correct length - this is just an example. Don't know where the 3s are coming from, but it's always 3s and that always seems to be the cause of my not being able to get back up and running.
The fix, ultimately, is to unplug the main Airport Express, wait a second, and plug it back in and wait for it to restart and reconfigure. Once that's done, the other one comes back online and everything is fine until it all happens again.
I have completely reconfigured both Airport Expresses from their factory settings a couple of times. Everything works fine for a while and then it doesn't - all for no reason that I can point to. The guys at the Apple Store say that there shouldn't be any issue with the older Airport Expresses and the newer iMac/Mac OS, although I have noticed that when the network is out the iMac is "usually" asleep - but this isn't always true either.
Has anyone had any similar experiences? I'm not a network expert but I think I know enough to keep my little network running well enough to do what I need it to do, and this is thoroughly frustrating, especially not being able to "reboot" the routers with the Apple utility that's meant for just that purpose. If it can't see the devices, what's the problem?

Leopard in my opinion plays much nicer with WPA/WPA2 networks. WEP is insecure and you should upgrade your network security anyway. Try configuring your base stations with WPA/WPA2 passwords.

Similar Messages

Network speed affected by large file copy operations. Also, why intermittent network outages?

Hi
I have a couple of issues on our company network.
The first is thate a single large file copy imapcts the entire network and dramatically reduces network speed and the second is that there are periodic outages where file open/close/save operations may appear to hang, and also where programs that rely on
network connectivity e.g. email, appear to hang. It is as though the PC loses it's connection to the network, but the status of the network icon does not change. For the second issue if we wait the program will respond but the wait period can be up to 1min.
The downside of this is that this affects Access databases on our server so that when an 'outage' occurs the Access client cannot recover and hangs permamnently.
We have a Windows Active Directory domain that comprises Windows 2003 R2 (soon to be decommissioned), Windows Server 2008 Standard and Windows Server 2012 R2 Standard domain controllers. There are two member servers: A file server running Windows 2008 Storage
Server and a remote access server (which also runs WSUS) running Windows Server 2012 Standard. The clients comprise about 35 Win7 PC's and 1 Vista PC.
When I copy or move a large file from the 2008 Storage Server to my Win7 client other staff experience massive slowdowns when accessing the network. Recently I was moving several files from the Storage Server to my local drive. The files comprised pairs
(e.g. folo76t5.pmm and folo76t5.pmi), one of which is less than 1MB and the other varies between 1.5 - 1.9GB. I was moving two files at a time so the total file size for each operation was just under 2GB.
While the file move operation was taking place a colleague was trying to open a 36k Excel file. After waiting 3mins he asked me for help. I did some tests and noticed that when I was not copying large files he could open the Excel file immediately. When
I started copying more data from the Storage Server to my local drive it took several minutes before his PC could open the Excel file.
I also noticed on my Win7 client that our email client (Pegasus Mail), which was the only application I had open at the time would hang when the move operation was started and it would take at least a minute for it to start responding.
Ordinarlily we work with many files
Anyone have any suggestions, please? This is something that is affecting all clients. I can't carry out file maintenance on large files during normal work hours if network speed is going to be so badly impacted.
I'm still working on the intermittent network outages (the second issue), but if anyone has any suggestions about what may be causing this I would be grateful if you could share them.
Thanks

What have you checked for resource usage during one of these copies of a large file?
At a minimum I would check Task Manager>Resource Monitor. In particular check the disk and network usage. Also, look at RAM and CPU while the copy is taking place.
What RAID level is there on the file server?
There are many possible areas that could be causing your problem(s). And it could be more than one thing. Start by checking these things. And go from there.
Hi, JohnB352
Thanks for the suggestions. I have monitored the server and can see that the memory is nearly maxed out with a lot of hard faults (varies between several hundred to several thousand), recorded during normal usage. The Disk and CPU seem normal.
I'm going to replace the RAM and double it up to 12GB.
Thanks! This may help with some other issues we are having. I'll post back after it has been done.
[Edit]
Forgot to mention: there are 6 drives in the server. 2 for the OS (Mirrored RAID 1) and 4 for the data (Striped RAID 5).

Database Replication never fall back over MAPI Network in case of dedicate network outage

Hi All,
Exchange 2010 SP3 RU4 and every time I have an outage on dedicated network the replication stop working and all Database looses sync (content Index) and I have to manually resync all as suggested on
http://exchangeserverpro.com/cannot-activate-database-copy-content-index-catalog-files-in-failed-state/
Should be MAPI network used to replicate and sync (even if replication disabled) in case of dedicate network outage ?
I'm reading everywhere "Yes, Database copy will revert on MAPI network in case of dedicated network's outge, even if Replication is disabled on MAPI network" but it's not my case.
Everything else up and running fine but I'd like to avoid to resync manually hundreds of DB.
Any suggestion greatly appreciated.
Red.

Hi Andy,
I know the theory but replication and seeding NEVER revert on my working MAPI network
"In the event of a failure affecting the Replication network, if the MAPI network is unaffected by the
failure, log shipping and seeding operations will revert to use the MAPI network, even if the MAPI network has it's ReplicationEnabled property
set to False."
This is NOT true in my environment (Ex 2010 SP3 RU4)
Red.
Well, in your case just the indexing is failing yes when this happens? Or is all replication failing?
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Network Outage !!

I live in the Finger Lakes Region in Upstate NYS. My Iphone has a complete network outage.. shows that I have signal and 3g data but will not call, text, or use any data applications. I have restarted, reset network preferences, and have done a hard reset, nothing has worked. I found out talking to people around the office that all of their phones are doing the same thing and we (30 people) have different phones. Checked with my friend who has AT&T and he has no interruption in service at all. Anyone else experiencing this? Is this just another crash from the "dependable" Verizon?

@anch368 Thank for posting. I find it regrettable that you are having service issues with your iPhone. Are you still experiencing the interruption? If so and since you’ve done the master reset please PM me your name and number and I can see what other options we have for you. I hope this helps. Thanks.
SammuelP_VZW
VZW Support
Follow us on Twitter @VZWSupport

Blackberry Network Outage

My boss is asked me why is his Verizon Blackberry working great for 3 months with BES and Enterprises server.
all sudden on half of Saturday and Sunday he won't be able to sent any emails out.
He want explaination of why, any one can help.
Is there an network outage from Verizon, because i checking my BES Enterprises and test all routing, LDAP is fully function.
exchange is working flawlessly.
I have to glue of what exactly is going on.

Hi,
Did you tell him to try a battery pull? Pull the battery for a minute or so and then put it back, allowing the device to reboot. See if it works then. There is a place in the Crackberry.com forums where service outages are reported. You might check there to see if there is a problem.
Doc

Brief random network outages

Hi
We have a networking issue that I hope someone may be able to help me with.
We run a Windows domain - single domain, single subnet. Three domain controllers: Windows 2012 R2 Standard, Windows 2008 Standard (32bit) and Windows Server 2003 Standard. The Win 2008 DC holds all the FSMO roles. DNS is setup on the 2008 and 2012 DC's
with the 2008 DC having a secondary DNS server installation. DHCP is setup on the 2008 DC. The 2003 server only functions as a DC - no roles apart from that are installed and it will be demoted very soon.
Two member servers: Windows Storage Server 2008 (64bit) and Windows 2012 Standard. The Storage server hosts 99% of our data with the other 1% being on the 2008 DC. Two email server software installations (not Exchange) - one on the storage server and one
on the 2012 R2 member server. NPS Routing and Remote Access is configured on the 2012 member server to handle VPN connections.
35 client PC's: 34 run Windows 7 and one runs Vista.
We have two Draytek routers on the network - one acts as the gateway to the Internet and the other provides wireless coverage. There are two networked printers - a Ricoh MFD 'workgroup' printer and a small mono Brother.
Network shares are accessed via DFS. The Servers, the Ricoh printer and routers have static IP's, most of the clients and the Brother printer use DHCP.
All cables terminate at one of two patch panels which then feed to one or more switches. Small desktop switches are used to expand the network where needed. The network is divided into two segments, hence two patch panels, but both run under the same 192.168.0.xxx/255.255.255.0
subnet.
Before we upgraded all our computers to Windows 7 the network was fine. The present network was built using CAT5 cabling in 2004 (we'd used BNC before that). We rarely had any network issues and when we did it would affect all clients. When
I first introduced Windows 7 it was on three PC's and one or more of them would randomly have problems accessing the network and Internet.
When I upgraded all our machines to Windows 7 we are seeing one or more machines experiencing network problems most days.
What happens is the (any) computer will suddenly stop - Applications accessing files across the network e.g. email and Access will hang and report as (not responding) and the 'busy' cursor appears. Try and save an office document and the busy cursor appears
and the application hangs. The Start menu is not accessible - for example I always have my Taskbar hidden and when this happens on my machine moving the mouse to the bottom of the screen does nothing, the Taskbar stays hidden. Sometimes, the Taskbar may
appear, but nothing happens when the Start button is clicked. When trying to access shared folders via Computer the green bar slowly moves through the Address Bar and after a while it reports the share is not accessible. The affected computers are also unable
to open any web pages.
The hang will last for anything from 20 secs to a minute or more after which the computer will continue operating normally. On very rare ocassions the the computer will not recover after 10mins or more and I have to force a shutdown but I assume this is
not directly related to the issues I am seeing.
The short outages are completely random and leave no trace of a problem in the System or Application Logs. When a machine does not recover (which is very rare) the System Log reports that a DNS server could not be reached.
This will happen on a single PC and others will be fine. But, it may affect several PC's over the course of a day.
When the outage happens I can Winkey+R, open cmd.exe and successfully ping the DNS servers by IP and name.
All the systems are up to date. I ensure that Windows Updates are installed on the Servers when they are released and the clients are updated the next day via WSUS.
I am pretty sure that this is also affecting Active Directory. I am seeing transient errors on the Domain Controllers where, for example, a Global Catalog can not be contacted. Both DC's are GC's and when I run nltest to test the connection to a GC within
30 minutes of the error being reported the test passes. I assume the servers are also experiencing these random outages.
The problem I have is that because they are random and because, on the clients at least, no errors are logged I cannot reproduce the problem and have no idea what may be causing the issue.
The problem is not a general network issue as it randomly affects one client at a time - if was a general network problem I would expect all the clients to lose connectivity.
Has anyone else seen a similar issue and know what the cause was, please?
Thanks

how old is the server?
How old is your network switches?
Any computer or server with NIC or network switches going south, may cause the intermittent issue.
They may flood the network with packets thus hang the system.
Every second counts..make use of it. Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
IT Stuff Quick Bytes

Prepare Exchange 2010 for a Major Network Outage

We are planning to replace our Core networking switch in our production environment. I am looking for a best practice option for Exchange to be placed into during this outage. This will be an approximate four hour outage.
Our current environment for Exchange is this:
Exchange 2010 SP3 rollup 8v2 two CAS servers and Three MBX/HT servers.
I read a few articles and they recommended different things, one was to just power down all of the exchange servers before the outage and then bring them back up after the outage. To me this just seems like a bad idea. The other was to put the MBX servers
into maintenance mode prior to shutting them down. This seemed more practical.
Can anyone provide feedback, insight, and guidance in this case? Has anyone gone through this type of outage and if so how did you handle your exchange environment and what was your success or failures with the scenario you used?
Thank you

When the server is in maintenance mode it moves all the active databases to other DAG members. It pauses the node in the cluster, and sets the DatabaseCopyAutoActivationPolicy mailbox server setting to Blocked. The Suspend-MailboxDatabaseCopy cmdlet is run
for each database hosted by the DAG member, and the cluster core resources will be moved to another server in the DAG if needed. This prevents data bases from auto activating in the case of a server failure. Just powering down an exchange MBX server would
cause the active data bases to failover to the alternate server, but once Quorum is lost due to more than half of the servers being shut down, I am not sure how the data bases would react after being brought back on line. Based on
this it seems to me that putting the servers in maintenance mode prior to powering them down would be the safest bet.
TL;DR What I am really looking for is advice or experience from an Admin who has already gone through a similar exercise.
Thanks for your input.

GDC problem or network outage

Hi Friends,
As this is related to SAP i am posting it here.
Because of the GDC outage we had 118 short dumps in SAP, In SM59 we have the WORKFLOW_LOCAL_900 and user WFbatch is used .
Our manager has a question i don't know what exactly to answer, his question is Why did the system have dumps if the outage was only on the network and did not cause SAP to crash ?
Please some one help me . If you want more information i can give.
thanks.
pl help friends.

SAP needs a working network to function prperly, This is even more true for RFC which interconnects servers/services through the network.

ATT Network outage and 3G phone

I have been having lots of problems with the network ever since getting my phone. I am on my 3rd 3G iphone. The network went down all across the country last week and since it came back up I have not had any problems. I was wondering if anyone else has noticed better service.
When I called ATT the morning of the outage the rep told me the outage was a planned outage and the network would be back up by 11am EST. The network came up at 12 and has been working ever since. No dropped calls!
Is this just wishful thinking or did ATT fix the network problems!
I read that ATT was having the same problem with a new Blackberry called Bold. They would not release it because of the network problems.

Wishful thinking. The outage was not planned, despite what you were told by a rep (personally, I was told it was a "major problem with their data network affecting many cities") - it was a routing problem. AT&T reps don't always have accurate information. You don't have to take my word for that, AT&T admitted the problem publicly, see this linked Reuters article, for example.
Dropped calls are still occurring. Reportedly (according to statements at Apple's iPod event yesterday), v2.1 released on Friday will address that issue.

San Francisco - LTE Network Outage

Once again LTE is either non existent or not even working in my location in San Francisco. I live near GG park 94117 (Cole / Page/ Waller/ Haight area and all day (sat. sept 28th), I've haven't been receiving any data and keep receiving "Network Communication issues". The 4G network in SF has been suffering for months. There's been multiple posts about this issue. I've performed multiple speed tests using 2 different devices in different parts of the city and get the same results. Can't even call support from the phone since the web-app pop ups when calling a verizon number and freezes since there's no data connection. Terrible. Why am I paying a premium for Verizon?
https://community.verizonwireless.com/thread/802217
https://community.verizonwireless.com/thread/802541

Verizon,
What are you doing about this??

Network outage don't bring down layer3 isdn

Hi Everyone,
Just wondering if someone ran through this case over the years...
Scenario :
2 routers in mgcp with 1 T1 on each. The DMS switch cascade the calls to the second T1 if the first one fail.
In a case you lose network connectivity on the first router, thus having the mgcp in a down state the calls should go to the second T1 but having mgcp down doesn't bring down the layer3 on the isdn link... I still ses the isdn status as MULTIFRAME ESTABLISHED...
I tried the busyout command but this only put channels in a busy state ... the first T1 still receive the incomming calls thus not cascading...
Anyone have an idea of what I could do to make the isdn link go down when the mgcp go dwon as well ?

Look into busy-out monitor feature:
http://www.cisco.com/en/US/docs/ios/12_0t/12_0t7/feature/guide/busy_t7.html#wp30177
HTH,
Chris

Network outage/problem this morning?

Anyone else experiencing network issues? My iPhone 3G is jumping back and forth on 'No Service' to EDGE to 3G, but then back to No Service. I am in Washington, DC.

YES!!! I'm experiencing the same exact problem. It started yesterday. It says no service and every now and then, it'll get service for about a minute and then just go back to no service. i'm on the phone w/ att/apple support now. this *****!!!! i'm in dc right now and it has no service.
Message was edited by: Rottsko

After recovering from a network outage firefox5 takes much longer time to be able to connect to web pages ( vs chrome).

system is running windows 7, ATT DSL .

Maybe try this, i am not sure that it will resolve the problem, but it is worth trying anyways.
http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/eef49e64-157c-4082-8e80-52e48309691f
Hi All,
I've seen this problem multiple times, especially with Windows 7 64-bit versions and Enterprise edition. The source of the problem appears to be the Bonjour service that is installed in the background and set to "Automatic" when installing certain 3rd
party applications. Apple applications like iTunes and Adobe applications like Acrobat Professional and Creative Suites have been known to cause this problem. I've also seen virtualization software like VMWare and VirtualBox cause similar issues
with network adapters.
The solution in most of the cases I've come across has been to stop and disable the Bonjour service. The Bonjour service also masquerades as a service with a name of the format "##Id_String1.6844F930_blahblahblah". Here's how to disable this service
in Windows 7:
Right-Click on Computer > Select 'Manage'
Expand the 'Services and Applications' section in the bottom of the Left-Nav dialog and Select 'Services'
Sort the Services list by name and look for either "Bonjour" or the "##Id_String..." name mentioned above
Right-Click on the service and select 'Properties'
Click the 'Stop' button to stop the service
Select 'Disabled' from the 'Startup type' drop down list
Click 'Apply' and then 'OK'
Reboot your machine and see if the "Multiple Networks" issue is resolved. If so, you should have internet connectivity again.
Hope this helps.
cheers,
Aaron

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.

Report Subscription - Failure writing file - The network path was not found.

I have several subscriptins which have been working fine.
All suddenly stopped with same error - Failure writing file - The network path was not found.
The subscriptions write to a number of different network paths, all of which exist and are accessible.

Is this a repeating failure or one time occurrence? If it's a one time occurrence it could have been a short network outage. If repeating look and ensure the user that the subscription is using to write the files still has the appropriate permissions,
is enabled, not locked, etc. Other things to possibly consider would be flushing the dns cache on the server. It's possible a firewall rule could have been put in place that would block the ability to access said location as well. The best
thing you can do is start by asking "what has changed".

Mysterious Network Outage

Similar Messages

Maybe you are looking for