SLM2024 port mirroring breaks network connections

Hi all, I got an SLM2024 that I want to use with my network probe app to analyze packets, I have my network probe PC plugged into the target port and uplink to firewall's trusted port to source port of 2024. Now whenever I enable port mirroring on the 2024, I lose all network connections on the 2024, I searched around here but didn't really find my answer. If anyone's seen this before, any pointers would be great.

Hi Crash, thanks for the reply, yeah it's a similar setting on that model just with a different layout on the admin page, what I meant on the trusted port part is, I have a netscreen firewall and the trusted port of the firewall goes into the source mirrored port of the slm2024, and my PC is on the target port. And I have those mirrored with a setting for both tx and rx, whenever I enable mirroring it halts traffic from the firewall, and others that are on the 2024 like server/workstns.
But network probe works and I can see traffic. We had a cisco catalyst before and that had no problems using the span feature.

Similar Messages

Kernel Upgrade Breaks Network Connection

My server uses:
[15:48] (tunix@kulupler ~)$ pacman -Qs kernel
local/kernel26 2.6.19.1-1
The Linux Kernel and modules
local/kernel-headers 2.6.19.1-1
Kernel headers sanitized for use in userspace
for kernel. The latest kernel upgrade (2.6.19.2-1) breaks network connection after ~5 minutes from the boot. When the network connections fails, kernel says:
Jan 12 15:10:44 kulupler ADDRCONF(NETDEV_UP): eth0: link is not ready
The connection never comes either after a network service restart, nor ifconfig eth0 up/down etc... The only solution is to restart, but after ~5 min. it fails again.
So, as a solution, I just downgraded the kernel to 2.6.19.1-1 again.

The AirPort Extreme base station (AEBS) is putting your PowerBook on a separate subnet. To solve the problem, configure the AEBS so that it does not distribute IP addresses.

43R8770 Port Replicator and network connection

I have a 43R8770 port replicator that I'm connecting to an SL500 Thinkpad running XP Pro sp2. Everything seems to be working correctly except the USB network adapter. Neither light on the adapter wll come on when it's plugged in and connected to the network. Anyone have similar problems? If so, how did you fix it?

I just uninstalled Access Connections, and now I can connect via ethernet through the USB port replicator.

Software upgrade breaks network connection

After upgrading the software for the Airport base station I have lost connection between my desktop unit and PB.
Prevously this worked without any problems.
The configuration is:
Cable modem connected to ASANTE 3004.
Desktop connected to ASANTE
AEB Connected via the WAN to ASANTE
PB using Airport to connect to ASANTE
eMac Connected to the ASANTE, this is seen by the desktop.
The PB sees the internet.
The Desktop sees the internet
But the PB using Airport doesn't see either of the Desktop units and vice versa.
If I connect the PB to the ASANTE with a direct ethernet cable both units see each other.
This seems to have been brought on by the upgrade to the base units software.
Can anyone suggest what might have changed as a result of the upgrade or what could be the source of the problem?
Richard Bullen
G4 MDD Mac OS X (10.4.3)
G4 MDD Mac OS X (10.4.3)

The AirPort Extreme base station (AEBS) is putting your PowerBook on a separate subnet. To solve the problem, configure the AEBS so that it does not distribute IP addresses.

Java update breaks network connect

The latest Java update has broken my junipe netwrok connect, anyone got any ideas?

This worked for me:
http://groups.google.com/group/macenterprise/browse_thread/thread/6368431a9c273a 53
The key is:
"This update also configures the Java web plug-in to disable the automatic
execution of Java applets. Users may re-enable automatic execution of Java
applets using the Java Preferences application. If the Java web plug-in
detects that no applets have been run for an extended period of time it will
again disable Java applets."

SG 300-28: port mirroring: the destination host looses network connectivity

Hi,
we have two SG 300-28. On one of them i configured port mirroring because one host behaves strangely. When i create the mirror, the host connected to the destination port is not accesible any longer, e.g. he does not answer to a ping. The packets from the source port appears on the destination port, but no packet intended for the host itself. Is this behaviour right ? I accepted that the host on the destination port is still accessible as it would be without the mirror.
Bernd

He Bernd,
Yes. This behaviour is right. That's how Port Mirroring works. The host connected to the Destination port loses its connectivity and it can only act as a monitoring device using softwares like WireShark (and monitor packets coming to and from the Source port(s)). All configurations on the destination port are overridden.
Let me know if you need further help,
HTH,
Vijay
Please rate useful posts

Adding a local site to Dreamweaver CC that is through a mapped network drive breaks ALL connections

I am using Dreamweaver CC on Windows 8 on a machine that is hooked up to a local network. My site files are stored on another drive on that network and I am mapped to that drive. I have always been able to open in individual file from that drive in Dreamweaver. But I noticed that with one site I am working on, Dreamweaver would hang trying to make minor revisions to the PHP code. It was suggested to me to add the whole folder as a local site in Dreamweaver, so I did. At first I thought it was moving along much better -- no hanging while I was typing code. Then suddenly I realized I could not save the files. I was no longer connected to the drive I was working on. Even outside of Dreamweaver, I was unable to access the drive. I thought it was a network issue. I rebooted the computer and opened a Windows Explorer folder and was able to access the drive. Then I opened Dreamweaver again and the connection was lost.
To test my theory, I rebooted again, accessed the drive, waited a little while, accessed the drive, then opened Dreamweaver and it was lost. I tried this several times, each with the same result.
Then I went into Dreamweaver, removed the site from Dreamweaver and rebooted. I accessed the drive, opened Dreamweaver, and voila... I could still access the drive. So I tried adding the site back to Dreamweaver and I cannot access the drive after opening Dreamweaver again.
Without having the site in Dreamweaver, the files/Dreamweaver hangs EVERY TIME I TYPE CODE. Adding a site on a mapped local network drive BREAKS MY CONNECTION and disables my ability to work on the files. Is there a reason for this and more importantly, is there a fix? It seems like a very specific but illogical problem.
My next step is to find and install my old Homesite 4.5.
Thanks in advance for any useful advice!

mpendill wrote:
I surely did not knowing change anything within the software!
I just tried adding another site. It seems like it is setting it up and reading the files but then at the end (apparently just as the connection breaks), it gives me these errors:
Cannot create [SITE NAME].
and
The local root folder, [FOLDER NAME], does not exist. Please select a new local root folder by clicking the Manage Sites button.
(I changed the out the actual site name and folder name above.)
I believe these were the same errors I got with the other site. At the time I was pushing a deadline and was too frantic to write it down.
Not that I think it has any relevance, but both sites are Wordpress sites.
Maybe what I should try next is mapping a different drive and trying to set up a site from there?
For that error you want you can try mapping it but it seems your sites root is just not defined... what DW is telling you is it could not find the specified folder when its trying to establish the new site. You might want to make sure your folder is there and all the spelling is correct, when making sure go your your Site Manager and make sure your root site is in your network drive.

Mirror and Witness Connection in a Disconnected state immediately after adding Witness Server to Mirror session.

After adding the Witness Server to the Mirror session, the Witness Connection state between the Mirror and Witness Connection is Disconnected and the state between Principal and Witness Connection is Connected.
The procedures defined in Books Online was used to setup Database Mirroring...when the Witness server was added to the Mirror session, only the alter database T-SQL statement was executed on the Principal server.
ALTER DATABASE <db_name> SET WITNESS = 'TCP://<servername>:<port>'
After executing the above statement, a few seconds later the state between Principal and Witness Connection changed to Connected and the state between Mirror and Witness Connection remains Disconnected.
The Mirror session is not using Certificates, every server is on the same domain, using the same domain login account, and all servers have SP2 installed running Enterprise Edition.
Any idea's why the state between Mirror and Witness Connection remains Disconnected?
Thanks,

I have the same problem. All 3 servers are on a workgroup and I'm using certificates. All three servers are connected via switch. This is a test environment, with the principal server being a 64 bit OS with Windows Server 2003 R2 with SQL Server standard x64, the witness server is a Windows server 2003 SP2 x32 with SQL Server Express, and the mirror is Windows XP x32 with Sql Server Standard. Using hard coded static IP addresses (FQDN makes no difference, and they get resolved to IP addresses anyway!). The mirror server log shows
'The server instance Witness rejected configure request, read its error log file for more information
but of course there are no errors logged on the witness server - not by SQL, nor in the event log. When the witness is set on the princial server, the Database mirroring monitor shows almost immediately that the witness and prinicapl servers are connected, but it takes quite a few seconds before the witness/mirror state is shown as disconnected. Until then the entry is blank. The monitor also shows High Saftey with automatic failover, which isn;t true - since the mirror and witness are not connected, no failover occurs when the principal is taken offline.
Since I'm running terminal services on the XP machine to interact with the witness and principal server, I find it hard to image that there are network issues.
If the witness can connect with the principal and the principal can conect with the mirror, under what circumstances will the witness NOT connect with the mirror? When I check the witness server for entries in the database_mirroring_witness view the following is shown:
RTJobs TCP://primary-sql:5022 TCP://192.168.100.14:5022 2 FULL 1 1 2263BD97-1004-4D73-9966-7AFB89E5626E A6EE18DF-19C4-48EC-8C06-77074EF5A275 0 1
Interestingly the IP address of the prinical server is replaced by the Sql Server instance name (primary-sql) but this doesn't happen for the witness.

Server Network Connection Loss with fast recovery.

Ok, so we are having an issue where our server is randomly losing network connection momentarily, but for long enough to boot everyone out. VMware seems to be related but we are having trouble understanding if VMware is just a symptom of something else happening or if VMware is indeed casuing this.
I was wondering if you guys might be able to offer your thoughts. At first we thought it was the MIC, and because we had a mirrored server we were able to swap to that and I think rule out that it's the NIC.
Thanks
Please see log below. This is just the first 100 lines.
19/08/13 12:07:56.084 PM vmnet-bridge[602]: Dynamic store changed
19/08/13 12:07:56.084 PM vmnet-bridge[602]: Adapter: en0, Inactive
19/08/13 12:07:56.000 PM kernel[0]: Intel82574L::setLinkStatus - not active 1face000, 0
19/08/13 12:07:56.000 PM kernel[0]: vmnet: bridge-en0: interface en is going DOWN
19/08/13 12:07:56.000 PM kernel[0]: vmnet: bridge-en0: interface en is going DOWN
19/08/13 12:07:56.000 PM kernel[0]: vmnet: VMNetDisconnect called for port 0xffffff80365aa000
19/08/13 12:07:56.000 PM kernel[0]: en0: promiscuous mode disable succeeded
19/08/13 12:07:56.000 PM kernel[0]: vmnet: bridge-en0: disabled promiscuous mode
19/08/13 12:07:56.000 PM kernel[0]: vmnet: bridge-en0: filter detached
19/08/13 12:07:56.000 PM kernel[0]: vmnet: bridge-en0: down
19/08/13 12:07:56.000 PM kernel[0]: vmnet: bridge-en0: detached
19/08/13 12:07:57.085 PM pppd[73135]: l2tp_wait_input: Address deleted. previous interface setting (name: en0, address: 192.168.29.4), deleted interface setting (name: en0, family: Ether, address: 192.168.29.4, subnet: 255.255.255.0, destination: 192.168.29.255).
19/08/13 12:07:57.134 PM configd[20]: network changed: v4(ppp0:192.168.29.4, en0-:192.168.29.4) DNS- Proxy- SMB-
19/08/13 12:07:57.135 PM vmnet-bridge[602]: Dynamic store changed
19/08/13 12:07:57.136 PM vmnet-bridge[602]: Could not retrieve media for interface ppp0: Operation not supported on socket.
19/08/13 12:07:57.000 PM kernel[0]: vmnet: VMNetDisconnect called for port 0xffffff80361d7400
19/08/13 12:07:57.000 PM kernel[0]: vmnet: bridge-en0: filter detached
19/08/13 12:07:57.000 PM kernel[0]: vmnet: bridge-en0: down
19/08/13 12:07:57.000 PM kernel[0]: vmnet: bridge-en0: detached
19/08/13 12:07:57.000 PM kernel[0]: vmnet: Freeing hub at 0xffffff8035474000.
19/08/13 12:07:57.139 PM pppd[73135]: starting wait-interface timer for l2tp: 20 secs
19/08/13 12:07:57.000 PM kernel[0]: ip4_output (ipsec): error code 22
19/08/13 12:07:57.000 PM kernel[0]: vmnet: VMNetSetopt: Set link state DOWN
19/08/13 12:07:57.000 PM kernel[0]: vmnet: VMNetSetopt: Set link state UP
19/08/13 12:07:57.000 PM kernel[0]: vmnet: VMNetSetopt: Set link state DOWN
19/08/13 12:07:57.000 PM kernel[0]: vmnet: VMNetSetopt: Set link state UP
19/08/13 12:07:57.000 PM kernel[0]: ip4_output (ipsec): error code 22
19/08/13 12:07:58.000 PM kernel[0]: 22
19/08/13 12:07:58.000 PM kernel[0]: ip4_output (ipsec): error code 22
19/08/13 12:07:58.085 PM vmnet-bridge[602]: Dynamic store changed
19/08/13 12:07:58.000 PM kernel[0]: Ethernet [Intel82574L]: Link up on en0, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,af48,0de1,0200,cde1,38ff]
19/08/13 12:07:58.000 PM kernel[0]: Intel82574L::setLinkStatus - active 1face000, b
19/08/13 12:07:58.000 PM kernel[0]: ip4_output (ipsec): error code 22
19/08/13 12:07:58.000 PM kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0xffffff8031dad400.
19/08/13 12:07:58.000 PM kernel[0]: vmnet: VMNetConnect: returning port 0xffffff8031dad400
19/08/13 12:07:58.000 PM kernel[0]: vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:e0:f7:b6
19/08/13 12:07:58.000 PM kernel[0]: vmnet: Hub 2
19/08/13 12:07:58.000 PM kernel[0]: vmnet:           Port 0
19/08/13 12:07:58.085 PM vmnet-bridge[602]: Started bridge for 2, en0
19/08/13 12:07:58.000 PM kernel[0]: vmnet:           Port 1
19/08/13 12:07:58.000 PM kernel[0]: vmnet:           Port 2
19/08/13 12:07:58.000 PM kernel[0]: vmnet:           Port 5
19/08/13 12:07:58.000 PM kernel[0]: vmnet:           Port 6
19/08/13 12:07:58.000 PM kernel[0]: vmnet: bridge-en0: media 20 dev 0xffffff8033a41428 family 2
19/08/13 12:07:58.000 PM kernel[0]: ip_output: can't update route after IPsec processing
19/08/13 12:07:58.000 PM kernel[0]: vmnet: bridge-en0: up
19/08/13 12:07:58.000 PM kernel[0]: vmnet: bridge-en0: attached
19/08/13 12:07:58.000 PM kernel[0]: en0: promiscuous mode enable succeeded
19/08/13 12:07:58.000 PM kernel[0]: vmnet: bridge-en0: enabled promiscuous mode
19/08/13 12:07:58.000 PM kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0xffffff8031dad400.
19/08/13 12:07:58.395 PM mDNSResponder[100]: mDNSPlatformSendUDP: sendto(8) failed to send packet on InterfaceID 0000000000000009 vmnet1/4 to 224.0.0.251:5353 skt 8 error -1 errno 55 (No buffer space available) 6348501084 MessageCount is 100
19/08/13 12:07:58.395 PM mDNSResponder[100]: mDNSPlatformSendUDP: sendto(8) failed to send packet on InterfaceID 0000000000000009 vmnet1/4 to 224.0.0.251:5353 skt 8 error -1 errno 55 (No buffer space available) 6348501084 MessageCount is 200
19/08/13 12:07:58.396 PM mDNSResponder[100]: mDNSPlatformSendUDP: sendto(8) failed to send packet on InterfaceID 000000000000000A vmnet8/4 to 224.0.0.251:5353 skt 8 error -1 errno 55 (No buffer space available) 6348501084 MessageCount is 300
19/08/13 12:07:58.396 PM mDNSResponder[100]: mDNSPlatformSendUDP: sendto(8) failed to send packet on InterfaceID 000000000000000A vmnet8/4 to 224.0.0.251:5353 skt 8 error -1 errno 55 (No buffer space available) 6348501084 MessageCount is 400
19/08/13 12:07:58.396 PM mDNSResponder[100]: mDNSPlatformSendUDP: sendto(9) failed to send packet on InterfaceID 0000000000000001   lo0/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 9 error -1 errno 55 (No buffer space available) 6348501084 MessageCount is 500
19/08/13 12:07:58.396 PM mDNSResponder[100]: mDNSPlatformSendUDP: sendto(9) failed to send packet on InterfaceID 0000000000000001   lo0/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 9 error -1 errno 55 (No buffer space available) 6348501084 MessageCount is 600
19/08/13 12:07:58.000 PM kernel[0]: code 22
19/08/13 12:07:58.000 PM kernel[0]: ip4_output (ipsec): error code 22
19/08/13 12:07:58.646 PM mDNSResponder[100]: mDNSPlatformSendUDP: sendto(8) failed to send packet on InterfaceID 000000000000000A vmnet8/4 to 224.0.0.251:5353 skt 8 error -1 errno 55 (No buffer space available) 8028798216342761815 MessageCount is 700
19/08/13 12:07:58.897 PM mDNSResponder[100]: mDNSPlatformSendUDP: sendto(8) failed to send packet on InterfaceID 0000000000000009 vmnet1/4 to 224.0.0.251:5353 skt 8 error -1 errno 55 (No buffer space available) 10643468882 MessageCount is 800
19/08/13 12:07:59.000 PM kernel[0]: 22
19/08/13 12:07:59.000 PM kernel[0]: ip4_output (ipsec): error code 22
19/08/13 12:07:59.142 PM mDNSResponderHelper[76029]: do_mDNSInterfaceAdvtIoctl: ioctl call SIOCGIFINFO_IN6 failed - error (22) Invalid argument
19/08/13 12:07:59.142 PM mDNSResponderHelper[76029]: do_mDNSInterfaceAdvtIoctl: ioctl call SIOCGIFINFO_IN6 failed - error (22) Invalid argument
19/08/13 12:07:59.000 PM kernel[0]: ip4_output (ipsec): error code 22
19/08/13 12:07:59.479 PM mDNSResponder[100]: mDNSPlatformSendUDP: sendto(8) failed to send packet on InterfaceID 0000000000000009 vmnet1/4 to 224.0.0.251:5353 skt 8 error -1 errno 55 (No buffer space available) 10643469463 MessageCount is 900
19/08/13 12:07:59.000 PM kernel[0]: 22
19/08/13 12:07:59.000 PM kernel[0]: ip4_output (ipsec): error code 22
19/08/13 12:07:59.690 PM pppd[73135]: l2tp_wait_input: Address added. previous interface setting (name: en0, address: 192.168.29.4), current interface setting (name: en0, family: Ether, address: 192.168.29.4, subnet: 255.255.255.0, destination: 192.168.29.255).
19/08/13 12:07:59.000 PM kernel[0]: ip4_output (ipsec): error code 22
19/08/13 12:07:59.000 PM kernel[0]: ip_output: can't update route after IPsec processing
19/08/13 12:07:59.705 PM racoon[265]: IKE Packet: transmit success. (Information message).
19/08/13 12:07:59.705 PM racoon[265]: IKEv1 Information-Notice: transmit success. (Delete IPSEC-SA).
19/08/13 12:07:59.705 PM racoon[265]: IKE Packet: transmit success. (Information message).
19/08/13 12:07:59.706 PM racoon[265]: IKEv1 Information-Notice: transmit success. (Delete ISAKMP-SA).
19/08/13 12:07:59.706 PM racoon[265]: Connecting.
19/08/13 12:07:59.706 PM racoon[265]: IPSec Phase1 started (Initiated by me).
19/08/13 12:07:59.706 PM racoon[265]: IKE Packet: transmit success. (Initiator, Main-Mode message 1).
19/08/13 12:08:00.000 PM kernel[0]: ip4_output (ipsec): error code 22
19/08/13 12:08:00.000 PM kernel[0]: vmnet: VMNetSetopt: Set link state DOWN
19/08/13 12:08:00.000 PM kernel[0]: vmnet: VMNetSetopt: Set link state UP
19/08/13 12:08:02.114 PM racoon[265]: IKE Packet: transmit success. (Phase1 Retransmit).
19/08/13 12:08:02.252 PM digest-service[76044]: label: default
19/08/13 12:08:02.252 PM digest-service[76044]:           dbname: od:/Local/Default

If you're not current on your VMware software, patch that to current.
Please then consider asking the VMware folks directly. They'll be looking for details such as your version and the guest operating system. Also probably for the network configuration within the virtual machine; the details of the virtual network set-up.
In general, there's not a whole lot of VMware discussion traffic here in the OS X Server forum. There's also little or nothing on that stack that looks specific to OS X Server in that log. That is mostly VMware chatter, with some generic OS X networking for mDNS (Bonjour) traffic.
Put another way, this forum probably isn't the best spot to get an answer. The folks in a VMware forum will likely have a rather better idea of what those log messages really mean, and may well have seen this sequence before.

Port mirroring on SG300 questions

Hi all,
I'm troubleshooting a LAN issue I have, and I wanted to hook up wireshark to record traffic over the course of a couple of hours for later diagnostics. I went into the web administration interface, clicked Administration > Diagnostics > Port and VLAN Mirroring, and added a port mirror from the port I wanted to watch to a port to which I had connected a laptop. I picked the Tx and Rx options, and clicked Apply.
I did receive lots of traffic in wireshark, but I noticed immediately that the server on the port I had mirrored was suddenly unavailable on the network -- pings timed out. This lasted until I removed the mirror, then the server was suddenly reachable once again.
Does this feature not work the way I had thought it does? What I saw looked more like a forward than what I would call a mirror. The documentation leads me to believe mirroring is intended to be used in just the way I was attempting to use it.
Am I missing something?

Hi Lamint,
I have a SG300-10P for my test, I did the same thing you did in my GUI.
I was mirroring port 7 to port 8 ticking the item to mirror RX and TX
My PC with wireshark was residing on port 8.
I started a comtinuous oibg from my PC on port 7 at IP address 192.168.10.60 to my WAN routers LAN address, 192.168.10.1 .
As you can see from my screen capture below, my PC on port 8 caprtured both RX and TX packets on port 7.
Because my wireshark PC was on port 8, I could not access the management interface of the switch to show you my configuration, so I grabbed the configuration via hyperterminal.
See screen caopture below ( with some configuration items excluded)..
I would suggest, if you are having issues to allow the Small Business Support Center to assist you.
http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html
Hope this helps
regards Dave

Port mirroring on SRW2048 kills Wireshark workstation IP

I have a workstation on this switch that is running WireShark and I need to get packets to it. However the moment I turn on port mirroring the station loses IP connectivity to the network. I tried Rx only, Tx only and both and all three settings knock the workstation off the IP network. Is there something I am missing? Also, I noticed that I can only mirror 4 source ports to this one target port. I would like to select pretty much all the ports as source port. Why can't I do this? I was previously using an older DLink switch that allowed me to mirror all ports and I am pretty sure that other switches like the Cisco 2900 series let you select all ports as source ports.
Thanks,
Diego

I fully understand what you are saying but that isn't consistent with previous experiences with port mirroring. I have used Cisco Catalyst type switches and also DLink switches that allow you to mirror all ports on the switch to one destination port. And even with all ports mirrored IP connectivity to the destination port is maintained.
This is not so surprising on the Catalyst stuff which is considered maybe a bit more "high end" than Linksys but the DLink which is a cheaper switch has the ability to do this just as the Catalyst. It seems that the Linksys is inferior in this regard to the Catalyst and the DLink.
Sorry to hear that and hopefully a future firmware version will change this behavior.
Thank you very much for your help.
Rgds,
Diego

PORT MIRRORING WITH SRW2048

HI ALL,
I am using SRW2048. When I am doing port mirroring, my target port is not working. it is disconnecting from lan.
Please suggest me how can I do port mirrioring with SRW2048.
Thanks

1. The source port is the one you want to mirror.
2. The target port is the one to which you mirror, i.e. the target port receives the mirror copies of the source port traffic, i.e. it is the port to which you connect the network analyzer.
3. On the SRW switches the target port does not allow LAN access. In mirror mode it ignores any traffic which you send from the device connected to the target port. If the network analyzer requires additional LAN access you'll need another LAN connection to another port, i.e. two LAN ports on the analyzer. There is no other way.

PCs losing network connection

We often have one of our ethernet-connected PCs lose its network connection. (not just the internet, the entire LAN connection). To get it back we either reset the Homehub 3 or simply swap the cables between ports on the hub. It isn't always the same PC that loses the connection, so pretty sure the problem isn't at the PC end.
I've spoken to BT in India and they sent a replacement Homehub 3, but the issue persists. Both Homehubs are Type A. The person I spoke with insisted they no longer make the Type B hub (which I wanted for its newer firmware).
Although we do have the workarounds above, this issue is annoying so I'd like to find a solution.

Hi foxycat,
Do you get any error messages on the computer when it loses connection? I presume the error messages are the same on each computer? I'm also presuming each computer is connected to the Homehub using a different ethernet cable so this would rule out the cable being at fault. Is there one computer that doesn't lose connection at all, or does the issue occur when you switch on a certain device?
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’.

Network Connection Failures Affecting Printing and Finder Access

I have a Canon MX320 connected via USB to my iMac running OSX 10.9.1. The latest Canon printer drivers are installed. Everything works fine with this printer and computer combination. The printer is enabled for shaing over the network.
The problem is that occasionally, the iMac seems to disconnect from any other laptop or desktop computer (Macs or PCs) connected through my wireless router. On a mac laptop (also with OSX 10.9.1) I may lose access to shared directories on the iMac, and more often, I lose the ability to print from the laptop. The print queues are unchanged on all Macs, but remote printing over the network fails with the message "printer not connected", even though the only change may have been that the iMac hosting the printer went to sleep.
Sometimes, waking the iMac allows the network print job to go through, but typically not if the print job is initiated before waking the iMac. The printer queue on the laptop will seem fine, with "printer idle", but as soon as the print job is submitted, it briefly reports "looking for printer", and then "printer not connected". Sometimes, everything (iMac and laptop) needs to be rebooted to re-establish a network printing connection through the iMac.
Trying to reset or delete and re-install the printer queue on the laptop does not fix the problem. I am assuming that this is because the remote connection to the server (the iMac) has effectively been interrupted or lost. The iMac may show up in a Finder window on the laptop as a simple PC icon, but with none of the connected directories visible. trying to re-mount the remote directories by connecting to the "server" (the iMac) often fails. It is as if something has happened to break the connection to the iMac, and both Finder and network printing are thereby disabled until everything is rebooted.
Printer error log entries:
E [13/Feb/2014:08:21:43 -0500] Unknown directive BrowseOrder on line 9 of /private/etc/cups/cupsd.conf.
E [13/Feb/2014:08:21:44 -0500] Unknown directive BrowseAllow on line 10 of /private/etc/cups/cupsd.conf.
This problem is intermittent but seems to be happening often after the Mavericks upgrade. One should not have to wake up a remote computer prior to connecting to it, or asking a printer connected to it to print a job.

Hello Rescue_2003
Check to see if Wake for network access is checked in System Preferences > Energy Saver.
OS X Mavericks: Share your computer’s resources when it’s in sleep
http://support.apple.com/kb/PH14244
Regards,
-Norm G.

My mid 2010 MacBook Pro loses network connectivity

I have four mac computers running on our home network. My mid 2010 MacBook Pro has become notorious for losing network connectivity with the other computers. It maintains it's internet connectivity consistently, but it's ability to see and connect with the other computers on the local network is finicky at best. The other three computers (2008 iMac, 2012 iMac, 2012 MacBook Pro) all connect to our Actiontec MI424WR Fios router via ethernet, whereas the mid 2010 MacBook Pro connects via WiFi.
If anyone could please help me troubleshoot the issue, that'd be much appreciated.
Sincerely.

Back up all data before making any changes.
Step 1
Take all the applicable steps in this support article.
Step 2
If you're running OS X 10.8.4 or later, run Wireless Diagnostics and take the remedial steps suggested in the summary that appears, if any. The program also generates a large file of information about your system, which would be used by Apple Engineering in case of a support incident. Don't post the contents here.
Step 3
If you're not using a wireless keyboard or trackpad, disable Bluetooth by selecting Turn Bluetooth Off from the menu with the Bluetooth icon. If you don't have that menu, open the Bluetooth preference pane in System Preferences and check the box marked Show Bluetooth in menu bar. Test. Continue if you find that Wi-Fi is faster with Bluetooth disabled.
From that same menu, select Open Bluetooth Preferences. If the box labeled Discoverable is checked, uncheck it. Click the Advanced button, and in the sheet that opens, uncheck the top three boxes, if any are checked. Click OK. Enable Bluetooth and test again.
If the application called "Bluetooth Setup Assistant" is running, quit it.
Step 4
This step will erase all your settings in the Network preference pane. Make a note of them before you begin, and recreate them afterwards. It may be helpful to take screenshots of the preference pane.
Triple-click the line below on this page to select it:
/Library/Preferences/SystemConfiguration
Right-click or control-click the highlighted line and select
Services ▹ Reveal
from the contextual menu.* A folder should open with an item named "SystemConfiguration" selected. Move the selected item to the Trash. You may be prompted for your administrator password.
*If you don't see the contextual menu item, copy the selected text to the Clipboard (command-C). In the Finder, select
Go ▹ Go to Folder...
from the menu bar, paste into the box that opens (command-V). You won't see what you pasted because a line break is included. Press return.
Reset the System Management Controller.
Step 5
Make a "Genius" appointment at an Apple Store, or go to another authorized service center.
Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional — ask if you need guidance.
If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
Keeping your confidential data secure during hardware repair
*An SSD doesn't need to be zeroed.

SLM2024 port mirroring breaks network connections

Similar Messages

Maybe you are looking for