Older G5 & new network card

I have a older G5 with what I think is PCI X and I need to install a second network card. I have 2 cards form a PC one is intel and the other a 3com. If i was to try these could it damage the g5?

Well I tried it and it worked fine

Similar Messages

  • Installing New network card on a Cisco Catalyst 6500 VSS mode

    Hi All.
    I need to install a new network card on Cisco Catalyst 6500 VSS mode, I need to follow any special procedures or is it only insert the new card and the Catalyst automatically recognizes the card?
    Thank you So mucho. 

    Hi,
    Just insert the blade and the switch should recognize it. For the 6500 series the blades are hot swap able.
    HTH

  • New network card

    I want to change network cards. Is is possible to change the network card without going through the install process? I would like very much to retain the other contents of the disk. Any suggestions?

    I hope you don't mean redo the "whole 3-CD" deal! (I did that twice till I found the right docs).
    I read to use "touch /reconfig ; shutdown -g0 -y -i 0" when a new network card is installed. When I boot the file is gone - so I think that is supposed to be, well, less destructive than "sys-unconfig".
    There's allways "sys-unconfig ; boot -r" (on my machine booting was automotic!). It doesn't do everything but it will let you re-do the network config screens (it returns mny items to "factory default" state). Better read the manpage first though! It might "factory default" something you've setup!

  • Installing new network card...how?

    The built in ethernet on my computer does not appear to be working. How do I get the Mac to see a new network card once i plug it into the board? Same for a sound card. I know that the built in sound is bad.
    I have extensive knowledge of these processes for a PC, but not at all for a Mac. A PC will automatically detect new hardware, but the Mac doesn't appear to see it.
    Thanks for any help.

    The built in ethernet on my computer does not appear
    to be working. How do I get the Mac to see a new
    network card once i plug it into the board? Same for
    a sound card.
    There aren't a lot of PCI Ethernet cards supported natively in OS X, and even then those that are usually still need a driver installed for them to function. D-Link is the only one I know off-hand that markets a 10/100 card billed as Mac-compatible. A Mac-compatible generic sound card will be even harder to track down.. the only ones I know of are very expensive ones aimed at digital audio production.
    -Douggo

  • Xennet error, when tried to add new network card

    Hi,
    I got an error when I tried to create new virtual network thru VM manager,
    I have add a new virtual network card thru VM manager in the same Xen bridge "xenbr0" , then i reboot the virtual machine, but when i tried to activate this network I got the below error:
    cannot activate network device
    xennet device eth1 does not seem to be present, delaying initialization.
    ifconfig in the virtual machine:
    dev13248 Link encap:Ethernet HWaddr 00:16:3E:0B:DD:E4
    BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    eth0 Link encap:Ethernet HWaddr 00:16:3E:5A:3E:6E
    inet addr:192.168.2.102 Bcast:192.168.2.255 Mask:255.255.255.0
    inet6 addr: fe80::216:3eff:fe5a:3e6e/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:204 errors:0 dropped:0 overruns:0 frame:0
    TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:47253 (46.1 KiB) TX bytes:5623 (5.4 KiB)
    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:1045 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1045 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1458998 (1.3 MiB) TX bytes:1458998 (1.3 MiB)
    sit0 Link encap:IPv6-in-IPv4
    NOARP MTU:1480 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    ifconfig in the VM server:
    eth0 Link encap:Ethernet HWaddr 00:1C:C4:46:AF:3D
    inet addr:192.168.2.101 Bcast:192.168.2.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:110 errors:0 dropped:0 overruns:0 frame:0
    TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:13177 (12.8 KiB) TX bytes:17612 (17.1 KiB)
    eth1 Link encap:Ethernet HWaddr 00:1C:C4:46:AF:3E
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:2052 (2.0 KiB)
    eth2 Link encap:Ethernet HWaddr 00:1C:C4:A6:B8:0E
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    eth3 Link encap:Ethernet HWaddr 00:1C:C4:A6:B8:10
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:127 errors:0 dropped:0 overruns:0 frame:0
    TX packets:127 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:11984 (11.7 KiB) TX bytes:11984 (11.7 KiB)
    peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:127 errors:0 dropped:0 overruns:0 frame:0
    TX packets:92 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:14405 (14.0 KiB) TX bytes:17422 (17.0 KiB)
    Interrupt:21
    peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    UP BROADCAST NOARP MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Interrupt:23
    peth2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    UP BROADCAST NOARP MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    Interrupt:16 Memory:f8000000-f8011100
    peth3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    UP BROADCAST NOARP MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Interrupt:23 Memory:fa000000-fa011100
    vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:98 errors:0 dropped:0 overruns:0 frame:0
    TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:17612 (17.1 KiB) TX bytes:13177 (12.8 KiB)
    vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:6 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2052 (2.0 KiB) TX bytes:0 (0.0 b)
    vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:12 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2236 (2.1 KiB) TX bytes:0 (0.0 b)
    xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:6 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1968 (1.9 KiB) TX bytes:0 (0.0 b)
    xenbr2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    xenbr3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

    Don't inject the Windows 7 version of the driver into your WinPE image. Depending on what version of ADK you are using determines what version of the driver you will inject into WinPE.  If you are using MDT 2013 with ADK 8.1 you are using WinPE 5.0/5.1
    which is basically Windows 8.1. Make a selection profile explicitly for your WinPE drivers to inject. Only include the drivers you want in the WinPE image. And match the architecture of the network and storage drivers (Windows 8.1 versions).
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • New network card caused: Error Codes: OAMP2OPY:GIQKCQ7V

    after installing a network card in my OBIEE 11g server
    I get this error:
    Error
    View Display Error
    Error generating view. Error getting cursor in GenerateHead
    Error Details
    Error Codes: OAMP2OPY:GIQKCQ7V
    Too many running queries. Server is too busy to process any more queries at this time.
    the server can still connect to the database..
    the IP address has not changed..
    how do I fix this?

    Metalink ID 1462776.1
    1. The Oracle Database instance is configured by default to run only 150 PROCESSES;
    the maximum load for dedicated connections is determined by the PROCESSES parameter.
    When the listener believes the current number of connections has reached maximum load, it may set the state of the
    service handler for an instance to "blocked" and begin refusing incoming client connections with the following error (in biserver1.log set in debug level):
    "TNS-12516 TNS:listener could not find instance with matching protocol stack"
    Tip:
    Verify the Oracle database processes parameter setting. It is also a good idea to make sure the Oracle database sessions and open cursors settings are large enough.
    2. Increase the number of concurrent client connections (sessions) to OBI server.
    Each client request to OBI Server uses one SERVER_THREAD.
    Each SERVER_THREAD uses 0 or more DB_GATEWAY_THREADs depending upon the number of DB queries executed.
    Following NQSConfig.INI parameters need to be tuned (refer to OBIEE tuning guide for details on initial values to be set):
    [ SERVER ]
    MAX_SESSION_LIMIT
    SERVER_THREAD_RANGE
    DB_GATEWAY_THREAD_RANGE
    3. Cleanup Web catalog via instanceconfig.xml using the steps documented in "Validating the Catalog" in System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
    4. In instanceconfig.xml file for each instance, add the following parameters within Cache/Query tags:
    <Cache>
    <Query>
    <MaxEntries>10000</MaxEntries>
    <AbsoluteMaxEntries>20000</AbsoluteMaxEntries>
    <CruiseEntries>3000</CruiseEntries>
    <ForceLRU>true</ForceLRU>
    </Query>
    </Cache>
    5. Make sure you have enough system resources available on BI Servers (sawserver, nqsserver).
    6. Unstable network connection link between OBIEE servers and Database server.

  • Network cards

    I have a Satellite P775-S7320, does anyone know if it is possible to add a new Network card?  I have a new router with the ac band, and my other devices can use ac also. I would like to get a new card that can connect and use ac.  Thanks.

    Did a traditional, JETless jump overnight, and had the same effect. So it's not JET.

  • "Unable to load network list" on new sim card overseas on unlocked iphone 4

    I recently bought an Iphone4 (unlocked) from australia. While traveling overseas I inserted a new sim and got the message "unable to load network list", and could not activate my new sim card. Could not find the answer on the discussion board here but got in touch with my provider back in oz who helped me.
    Solution: You need your laptop with Itunes on it. Turn the phone off, then connect to your laptop with Itunes already running and then turn the phone on. When you click on your phone icon in Itunes it will say "Congratulation, your iphone is unlocked". You can then eject your phone and your new sim is activated.
    Hope this helps

    Sorry not sure why your new sim card isn't supported...not sure if it helps but I had my laptop connected to wifi at the time also, but I don't think it should matter. Its worth a try connecting to internet with ITunes on, connect your phone and then turn it on and see what happens.

  • Configuring the HP PSC 2510 on a new network

    I'm posting at the end of a long weekend setting up my psc 2510 on a new wireless network. I'm pretty much done, and I'm posting to share what I've learned with others in the hope of saving them trouble. I'm beyond my warranty period, so my advice is based on a few hints from phone tech support and a lot of work by trial and error.
    I have four machines total, two of them running OS X 10.4, the others running 10.3.9.
    1. Start by hooking the printer up to a wired (ethernet) network. Print out a network config page (setup, 6, 1) when the printer shows its blue "networked" light. Dial the printer's URL into your web browser and enter the new network's info into the printer's embedded web server. If you get everything right, when you turn off the printer, disconnect the ethernet cable, and turn on the printer, you'll get that blue "networked" light after a minute or so.
    If you don't see the light, print out another config page and check the "Wireless Status": "Scanning" means that the printer's having trouble connecting to the network. Your best bet is to temporarily turn off all wireless encryption/security and reconfigure the printer's connection. Once you have a connection, then try adding various sorts of security/encryption. In my experience, the printer doesn't do well if the SSID of the network isn't being broadcast or with a list of acceptable MAC addresses. In my old network I managed to get the printer running with WPA security, but this time I had to settle for WEP 128 bit security.
    The Wireless Status will read "Disabled" if the printer has a USB cable or Ethernet cable attached. This means you need to unplug all cables (and possibly turn the printer off and on) to enable the wireless card. If the Wireless Status is "Disabled" even though you have no cables attached, you have probably reset the printer to factory defaults (see #2 below).
    Things to watch for: is the default gateway of the printer the same as that of your new network? I had to change my new network's gateway to "192.168.1.1 addressing" from "10.0.1.1 addressing" because the printer was expecting "192 etc." after being hooked up to a Linksys router for several years.
    Also, you may find you need to give the printer a self-assigned (manual) IP address, if other computers, once linked to the printer, lose printing and/or scanning capabilities a few days or weeks later. This can be set in the printer's web access server, but make sure to assign the printer an IP address that's compatible with the range of IPs that your router's is leasing to the network. I'm a novice at this network stuff, so sorry if I'm being vauge on this point.
    2. It's possible I could have saved myself a lot of trouble setting up the printer for the network if I had reset the printer's network settings to factory defaults right at the start. But if you decide to follow HP's instructions and reset network settings to factory defaults, BEWARE: the printer's embedded web server can't for some reason configure the printer to re-enable wireless networking. And the latest download of the hp all-in-one installer doesn't contain the network config utility found on the original HP installation CD. (On this old CD, the config utility isn't part of the install package, but it is invoked automatically during the installation process.)
    SOLUTION: Run the PSC 2500 Series installer found on the HP CD, preferably from a Mac running an system older than Tiger. It might also be possible to avoid running the installer and just run the config utility.
    From this point on, I'll assume you've managed to get the printer on your network. Here's how to get all your computers configured to use the psc's printer and scanner functions.
    HP tech support advised me to download the latest installer/print driver and use that to install and configure the psc 2150. This is good advice, insofar as the old HP Director software has a memory leak and the old HP Scan was prone to crashing whenever the 2510 went into Energy Saving mode. But if your mac isn't running OX X 10.4 (Tiger), you'll find that your system doesn't seem to recognize the new print drivers installed with by the download. This is especially a problem if you follow HP tech support's advice and delete a bunch of files prior to upgrading from the old installer to the new one, as (I suspect) it was at this point that I deleted working printer drivers from my Macs running Mac OS 10.3.9.
    So if you're running 10.3.9 or earlier, I advise you not to delete any files and to configure your computer for the print and scanner functions in the opposite order that HP advises.
    Most important: through trial and error I discovered that the HP Setup application isn't able to configure the printer if more than one user is logged in (Fast User Switching!). (This is a particularly tricky error to diagnose as the only symptom is that the setup app keeps claiming that it "can't find device" even though in the stage just prior it had successfully detected it!) Log out all other users, then proceed with the following steps:
    1. Go to Print Center (called Print Setup Utility in Tiger), delete your old psc printer (if any) and click "add printer". The psc should show up in HP IP printing or under Rendezvous (called Bonjour in Tiger), and when you click on it, the Add Printer utilty should automatically find the "HP All-in-one" printer driver. If something's gone wrong, though, you may get the message "Print Driver not installed". That's what happened to me after I deleted files (see above).
    SOLUTION: Run the PSC 2500 Series installer found on your original HP CD. When it finishes, it will start the HP setup assistant, in the course of which you'll be directed to go to the Print Center and add your printer. Do so.
    2. Once you've added the printer successfully, run the latest HP installer, a download from the HP website. You should be able to skip the step where it asks you to add the printer, as you did this in step one.
    3. Finally, since you didn't delete any files earlier, be sure to remove HP Director from your dock and from your Startup items (Login items in Tiger) by opening Mac System Prefs - Accounts - Startup/Login Items. HP Director has a memory leak. And it is superceded by the newer HP Device Manager when you download and run the latest HP installer. You should find the new HP Device Manager in your dock after step 2 (above).
    If you have questions, write me at the following email (account name reversed to foil spam bots):
    [email protected]
    Powerbook 17"   Mac OS X (10.4.3)   Airport Express base station

    Hello dgt228, welcome.
    I am not sure why you are choosing EAP.  If you have set your router to use WPA, you should just set your printer to enable WPA. Is your wireless light illuminated on the front of your printer?  Run a Wireless Network Test from the front of the printer to self-test the radio. If you can connect this printer with Ethernet to your router its connection will be more secure and more reliable.

  • Awful new Network Map -- how can I get rid of it?

    The latest upgrade, to Network Magic  5.1, is awful.  There is a terrible new circular version of the Network Map.  Many of the devices now are listed off the screen on three pages.  The display is very confusing, with some devices on the screen, and others off the screen to either side. 
    Where is the the option to go back to the old version of the Network Map which was much, much easier to use?
    Is there a way to select the old network map as an option?
    If not, how can I go back to an older version of Network Magic?

    Hi gabrielse, Right now the only version of NM that you can go back to is 4.9, which you can find on the download page on PureNetworks.com
    ...but I think you should wait a bit before going back to 4.9 
    My Cisco Network Magic Configuration:
    Router: D-Link WBR-2310 A1 FW:1.04, connected to Comcast High Speed Internet
    Desktop, iMac: NM is on the Windows Partition, using Boot camp to access Windows, Windows 7 Pro 32-bit RTM, Broadcom Wireless N Card, McAfee Personal Firewall 2009,
    Mac Partition of the iMac is using Mac OS X 10.6.1 Snow Leopard
    Laptop: Windows XP Pro SP3, Intel PRO/Wireless 2200BG, McAfee Personal Firewall 2008
    Please note that though I am a beta tester for Network Magic, I am not a employee of Linksys/Cisco and am volunteering my time here to help other NM users.

  • PLEASE Help on two network cards in server

    Hi all,
    (Sorry my spelling Im danish)
    We have a 10.4.5 server with 2 network cards in it. How does I get the server to route betwin the two networks so that mac's on net 1 (en0) can see mac's and printers on net 2 (en1) and visa versa
    The mac's on net 1 can see and use the server (but not print on net 2) The mac's on net 2 cant see or use the server!
    The mac's on net 1 get backuped by Retospect on the server. Retospect can't see the mac's on net 2
    How does I get this to work?

    "sudo sysctl -w net.inet.ip.forwarding=1"
    That will start forwariding immediately but woun't survive a reboot.
    In Tiger Server Admin NAT setup you can make this permanent by choosing "start Ipforwarding Only".
    (Or by adding a line to /etc/hostconfig:
    IPFORWARDING=-YES-
    Or by adding a new file /etc/sysctl.conf
    with this line in it:
    net.inet.ip.forwarding=1)
    "Devices on each network need to know how to get to the other network, and that's usually done by editing the routing table on each system."
    Not necessary. What's necessary is a static route in each Internet router that use the server IP for each LAN as the gateway/router for the other LAN.
    Example network 1: 192.168.100.0/24
    Internet router 192.168.100.1
    Server IP for that LAN 192.168.100.254
    Static route in Internet router: 192.168.200/24 gw 192.168.100.254
    Example network 2: 192.168.200.0/24
    Internet router 192.168.200.1
    Server IP for that LAN 192.168.200.254
    Static route in Internet router: 192.168.100/24 gw 192.168.200.254
    "In addition it's not common for a printer to have an option to manipulate the route table in this way"
    Correct, but you need to add the correct gw/router and netmask to the printer IP settings for this setup. This is sometimes achievable via Telneting to the printer in question to set it up (older Apple printers).
    For performance reason it could be better using a static route in each machine if the internet router doesn't send out route redirect packets.
    Some DHCP servers should be able to send out a static route to it's clients with the rest of the IP info thus making it easier to provide each machine with a static route.

  • VIA KT400 Network Card Problems!

    I've read allot about the problems I've been having and done many searches on Google and it all seems to come down to this: ALL VIA Motherboards in the KT400 series(and many other chipsets) lock up when using ANY Wireless Card\Usb Adapter. The frusterating part is nobody seems to have a clear answer on how to fix this or if it's even fixable  
    The forum linked down below tries to claim this only happens with Linksys cards.. This is false as I have a Microsoft Wireless G USB adapter and the EXACT SAME thing happens to me.
    The strange part is if you are just browsing the web and reading text, everything works 100% fine. But as soon as you do something that uses DirectX or 3D Acceleration, like say Streaming Videos.. it freezes with the mouse curser just sitting there and I must hard reset the system.
    Does anyone out there know of ANY kind of fix? I'm dying to know.
    You can view someone elses post referring to the exact problem I have in the VIA Arena Forum
    AMD Athlon XP 2500+ @ 2.00 Ghz
    512 MB Ram
    GeForceMX 5900XT
    Antec 420 Watt Power Supply
    Windows XP SP2
    Latest VIA Hyperion Drivers

    Hey guys it's me again.. Well the computer now seems to freeze less than it did before, but it still freezes.  
    After all this going back and forth and troubleshooting hassle ive decided it has to unfortunatlely be a hardware problem. I've stated before that it only freezed when running a 3d app and network card running.. but now it freezes even when I'm just on the web. It's just so totally random, sometimes it will freeze twice in one minute and sometimes it won't freeze for almost a whole day.
    I've narrowed it down to 3 things: Bad HD, Bad Processor, and worst of all Bad Motherboard. Another possibility, does a the lithium battery on the motherboard ever cause problems if it's almost dead?(Assuming it's the CMOS battery?) And could that cause problems?
    I had an episode before that I didn't tell you guys before. This was still after i had the network card, but probably unrelated. The computer once or twice made a very strange electrical zapping noise or screetching noise before and the whole system would almost fail and then try to resume again, and then just shut down.
    After this event happened I figured it was the PSU not putting out enough power as I had installed new hardware lately. I bought a new 430W psu and while I haven't had the strange problem I had before, I still get random lockups.
    I'm pretty sure it is the harddive, because it would make sense since I heard this noise before and the fact that it just freezes could just be the HD getting stuck and not spinning anymore.
    It's funny because I had just replaced a faulty harddrive before in one of my older computers. However that one was much more obvious as it would constantly have to repair files in sectors. The HD I have now never comes up with errors, but maybe It is running fine before it decides to lockup.
    Yet another thing it could be is the processor maybe just not generating enough juice to keep the processes going or something.
    I did have problems with freezing before the network adapter now that I think back, but they were far and few between and now the problems are more pronounced. I'm going to hope it just the HD, if not it's really going to suck to already have to buy another motherboard or processor. I just built the system from scratch last year.
    Sigh, Oh well. Glad for anymore insight on this issue and your opinions on what is most likely the problem. I'm going to go looking for a HD in the mean time.

  • RE: Is there a way to have 2 network cards on the samemachine

    Sean,
    I mean I am always connecting to the nodemgr of the 2nd environment
    successfully. Only when I run the client part of the application that I know
    is up, I get a response from the Name Server that it is actually the first
    IP address.
    I checked again. I defenitely have FORTE_NS_ADDRESS set to IP:5004, in my
    case, and not the hostname. I don't have FORTE_LOCATIONS set any where. the
    NS_ADDRESS for env2 has only 1 IP address associated with it. My Forte
    Control Panel on the client, and hence the NS address has only one entry.
    I tried going into escript like you said, and the name service still thinks
    it is IP1.
    Venkat Kodumudi
    Price Waterhouse LLP
    Internet: [email protected]
    Internet2: [email protected]
    -----Original Message-----
    From: Sean Brown [SMTP:[email protected]]
    Sent: Monday, June 22, 1998 1:31 PM
    To: Venkat Kodumudi; 'Sean Brown'
    Cc: [email protected]
    Subject: RE: Is there a way to have 2 network cards on the same
    machine
    Hmmmm? That is a little odd! Let me rehash what I think you are saying.
    You now have two environments each with their own name service with
    FORTE_NS_ADDRESS set to a different IP:Port combination. For example you
    are doing the steps:
    FORTE_NS_ADDRESS=255.255.255.1:5000
    start the nodemgr for env 1
    FORTE_NS_ADDRESS=255.255.255.2:5000
    start the nodemgr for env 2
    Now when you start a client you are always getting the address for env 1
    back from the nodemgr. I assume you actually mean the name service? Or, do
    you mean you are always connecting to the nodemgr & name service for env
    1?
    If the first scenario is the case and you are connecting to the nodemgr
    for
    env 2 but getting back IP's for services listening on the card for env 1 I
    would ask you what you are setting the FORTE_LOCATIONS value to before you
    start each service. If you are not setting it or are using the host name
    it
    will register using the IP for the primary network card associated with
    the
    machine name and I am again assuming that this is env 1. You need to set
    the FORTE_LOCATIONS variable to 255.255.255.2:0 (based on the steps above)
    before starting your services.
    If the second scenario is the case I would have you check what the
    FORTE_NS_ADDRESS is set to before you start up the client. Once again it
    must be the IP:Port combination not host:port combination if you want to
    get
    anything other than the primary card.
    I would also suggest that you do the following. After everything is up
    and
    running execute the following commands:
    escript -fns "ip for env1":port
    findsub nameservice
    showpart
    What you should see is everything currently registered under the name
    service. It will have the name and any "locations" (IP and port) that it
    is
    registered as listening on. I would look for the nodemgr and see where it
    has advertised itself. I would then look for any services you expect to
    be
    registered there and also verify where the have advertised themselves. If
    there are multiple locations listed for any one service, the client will
    use
    the first one in the list.
    Do the same for env 2.
    Sean
    -----Original Message-----
    From: Venkat Kodumudi [mailto:[email protected]]
    Sent: Monday, June 22, 1998 9:57 AM
    To: 'Sean Brown'
    Cc: [email protected]
    Subject: RE: Is there a way to have 2 network cards on the same machine
    I am giving the actual IP address. and not the host name. That is why I
    don't understand what is going on.
    Venkat Kodumudi
    Price Waterhouse LLP
    Internet: [email protected]
    Internet2: [email protected]
    -----Original Message-----
    From: Sean Brown [SMTP:[email protected]]
    Sent: Monday, June 22, 1998 10:53 AM
    To: Venkat Kodumudi; 'Sean Brown'
    Cc: [email protected]
    Subject: RE: Is there a way to have 2 network cards on the same
    machine
    Hello Venkat,
    I probably should have mentioned this before. Your are correct. Forteis
    doing a host lookup if you are providing a name for examplemachine1:5000.
    You can bypass the host lookup by using the actual ip dot addressinstead
    for example 255.255.255.255:5000. This way you are taking the name
    service
    out od the picture and Forte will use the address provided.
    Sean
    -----Original Message-----
    From: Venkat Kodumudi [mailto:[email protected]]
    Sent: Monday, June 22, 1998 9:27 AM
    To: 'Sean Brown'
    Cc: [email protected]
    Subject: RE: Is there a way to have 2 network cards on the same machine
    My requirement is that my second card serves as best case performance
    testing piece. This eliminates the network completely. We went one step
    ahead and created a new enviromnent for the second card. Whatever I do,
    the
    nodemgr is returning back the IP address of the first card, even thoughmy
    FORTE_NS_ADDRESS does not have the first card in the picture any where.
    I think Forte is doing a host look up and returning the first IP address
    it
    finds, as opposed to returning the IP address specified in theenvironment
    variable FORTE_NS_ADDRESS. Is there a way to trick it?
    Venkat Kodumudi
    Price Waterhouse LLP
    Internet: [email protected]
    Internet2: [email protected]
    -----Original Message-----
    From: Sean Brown [SMTP:[email protected]]
    Sent: Thursday, June 18, 1998 9:54 AM
    To: Venkat Kodumudi
    Cc: [email protected]
    Subject: RE: Is there a way to have 2 network cards on the same
    machine
    OK, you ran into one of the issues. That is, if both addresses areknown
    to
    the client that is trying to contact the partition it will always usethe
    first address in FORTE_LOCATIONS. This is because FORTE_LOCATIONS was
    designed more as a failover mechanism. So it will always try the
    first
    address in the list and if it succeeds, there is no reason to move onto
    the
    second.
    Now, the second issue is that there is currently a problem with theclient
    failover to the secondary address in FORTE_LOCATIONS. If the firstentry
    fails it is supposed to retry on the second entry. Instead, it
    retries
    the
    first entry again. I know that Forte knows about this but I do nothave
    a
    bug number on it.
    With that said, lets look at a possible solution for you. If the real
    objective here is to have a back up network card available for fail
    over
    on
    the same machine, or use one card to advertise outside your firewalland
    one
    to use inside, then you will have to contact Forte to determine whenthe
    failover problem will be fixed. But, if the objective is to loadbalance
    across the network cards you could have the environment manager listenon
    both ports and then alternate your server partitions across both
    cards.
    For
    example:
    set FORTE_NS_ADDRESS=card1:5000;card2:5000 and then start up the
    environment
    manager
    set FORTE_LOCATIONS=card1:0 (the 0 in the port causes the OS to pick a
    port)
    and start partition one
    set FORTE_LOCATIONS=card2:0 and start partition two
    and so on....
    In this scenario the environment manager will be listening on bothcards
    but
    each server will be listening on only one of the two cards. So if a
    request
    comes in for partition1 it will go through card one and if it is for
    partition two it will go through card two. You could assign your
    partitions
    to cards based on expected load.
    Well, I am done. I hope this helps!
    Sean
    -----Original Message-----
    From: Venkat Kodumudi [mailto:[email protected]]
    Sent: Thursday, June 18, 1998 8:06 AM
    To: 'Sean Brown'; 'John Jamison'
    Cc: [email protected]; Jose Suriol
    Subject: RE: Is there a way to have 2 network cards on the samemachine
    Sean,
    Thanks for your reply. I tried the approach. I was not very specificin
    my
    question. I do need the ability for server applications to listen and
    server
    on both the network cards.
    I was succesfully able to make the nodemgr listen on both the cardsand
    actually serve requests coming in from both the cards. But, followingyour
    advise, I took a cautious step with FORTE_LOCATIONS. Here is what I
    noticed.
    I have an application that has 6 partitions in total. I used
    FORTE_LOCATION
    to make it listen on 1. Both the cards. 2. Swapped the IP addresses
    for
    both
    cards for this application. 3. One card that I want it to listen on. I
    tried
    all approaches by exporting the locations variable for just this
    application. The nodemgr recieves a request from this pc connected onthe
    second card to talk to one of the partitions. The node mgr responds
    with
    a
    proxy - with the ip address and socket number of the first card. The
    FORTE_NS_ADDRESS variable looks like this:
    IP1:5002;IP2:5002.
    Is it possible atall to resolve my problem, without having a seperate
    environment?
    Thanks
    Venkat Kodumudi
    Price Waterhouse LLP
    Internet: [email protected]
    Internet2: [email protected]
    -----Original Message-----
    From: Sean Brown [SMTP:[email protected]]
    Sent: Wednesday, June 17, 1998 10:42 AM
    To: 'John Jamison'; Venkat Kodumudi
    Cc: [email protected]
    Subject: RE: Is there a way to have 2 network cards on the
    same
    machine
    Venkat,
    Actually, it is possible for Forte to listen on more than one IP andport
    combination. The first reply to your message was correct. If you
    set
    the
    FORTE_NS_ADDRESS to contain multiple entries before starting the
    name
    service, it will advertise on both. For Forte servers you use the
    FORTE_LOCATIONS env variable to get it to advertise on multipleip:port
    combinations.
    We were doing something very similar with another customer I was at
    to
    get
    around a firewall. I will warn you that there are some issues with
    FORTE_LOCATIONS that may keep that portion from working. However,
    from
    reading your note, it appears that all you need is for the nameservice
    to
    advertise and listen on multiple ports and that works fine. I justtested
    it again for sanity sake and it worked. I ran my test on NT using
    Forte
    3G2.
    Sean
    -----Original Message-----
    From: [email protected]
    [<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of John Jamison
    Sent: Tuesday, June 16, 1998 4:51 PM
    To: Venkat Kodumudi
    Cc: [email protected]
    Subject: Re: Is there a way to have 2 network cards on the samemachine
    Venkat,
    Technically yes this is possible, though not in Forte. A nameserver
    can
    only listen on one port.
    To implement this scheme you will have to write a proxy service (insome
    language
    including perhaps forte) which listens on the well-known port on the
    second card, reads requests, then forwards them to the realnameservice
    (wkp on the first card), and forwards replies back. This is not
    trivial, but some firewall toolkit vendors supply stub code to write
    application specific proxies.
    -J
    Venkat Kodumudi wrote:
    Folks,
    Here is what we would like to do:
    We want to have 2 network cards on a unix box - which means I have
    2
    ip
    addresses, and the connection between the two is the unix box and
    only
    the
    unix box. I have a pc connected to the 2nd network card and I want
    it
    to
    connect to the nameserver that is listening on a well known port
    on
    the
    first network card. We don't want to turn IP forwarding between
    the
    two
    cards. We want Forte to address both cards to talk to clients, in
    one
    environment.
    Can this be done? If so how?
    Thanks in advance.
    Venkat Kodumudi
    Price Waterhouse LLP
    Internet: [email protected]
    Internet2: [email protected]
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive<URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
    >>>>
    John Jamison [email protected]
    Vice President and Chief Technology Officer
    Sage IT Partners, Inc.
    Voice: 415 392-7243 x 306
    Fax: 415 391-3899
    Internet Enabled Business Change
    <a href=
    "http://www.sageit.com">http://www.sageit.com</a>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

    Hello Venkat,
    I probably should have mentioned this before. Your are correct. Forte is
    doing a host lookup if you are providing a name for example machine1:5000.
    You can bypass the host lookup by using the actual ip dot address instead
    for example 255.255.255.255:5000. This way you are taking the name service
    out od the picture and Forte will use the address provided.
    Sean
    -----Original Message-----
    From: Venkat Kodumudi [mailto:[email protected]]
    Sent: Monday, June 22, 1998 9:27 AM
    To: 'Sean Brown'
    Cc: [email protected]
    Subject: RE: Is there a way to have 2 network cards on the same machine
    My requirement is that my second card serves as best case performance
    testing piece. This eliminates the network completely. We went one step
    ahead and created a new enviromnent for the second card. Whatever I do, the
    nodemgr is returning back the IP address of the first card, even though my
    FORTE_NS_ADDRESS does not have the first card in the picture any where.
    I think Forte is doing a host look up and returning the first IP address it
    finds, as opposed to returning the IP address specified in the environment
    variable FORTE_NS_ADDRESS. Is there a way to trick it?
    Venkat Kodumudi
    Price Waterhouse LLP
    Internet: [email protected]
    Internet2: [email protected]
    -----Original Message-----
    From: Sean Brown [SMTP:[email protected]]
    Sent: Thursday, June 18, 1998 9:54 AM
    To: Venkat Kodumudi
    Cc: [email protected]
    Subject: RE: Is there a way to have 2 network cards on the same
    machine
    OK, you ran into one of the issues. That is, if both addresses are known
    to
    the client that is trying to contact the partition it will always use the
    first address in FORTE_LOCATIONS. This is because FORTE_LOCATIONS was
    designed more as a failover mechanism. So it will always try the first
    address in the list and if it succeeds, there is no reason to move on to
    the
    second.
    Now, the second issue is that there is currently a problem with the client
    failover to the secondary address in FORTE_LOCATIONS. If the first entry
    fails it is supposed to retry on the second entry. Instead, it retries
    the
    first entry again. I know that Forte knows about this but I do not have a
    bug number on it.
    With that said, lets look at a possible solution for you. If the real
    objective here is to have a back up network card available for fail over
    on
    the same machine, or use one card to advertise outside your firewall and
    one
    to use inside, then you will have to contact Forte to determine when the
    failover problem will be fixed. But, if the objective is to load balance
    across the network cards you could have the environment manager listen on
    both ports and then alternate your server partitions across both cards.
    For
    example:
    set FORTE_NS_ADDRESS=card1:5000;card2:5000 and then start up the
    environment
    manager
    set FORTE_LOCATIONS=card1:0 (the 0 in the port causes the OS to pick a
    port)
    and start partition one
    set FORTE_LOCATIONS=card2:0 and start partition two
    and so on....
    In this scenario the environment manager will be listening on both cards
    but
    each server will be listening on only one of the two cards. So if a
    request
    comes in for partition1 it will go through card one and if it is for
    partition two it will go through card two. You could assign your
    partitions
    to cards based on expected load.
    Well, I am done. I hope this helps!
    Sean
    -----Original Message-----
    From: Venkat Kodumudi [mailto:[email protected]]
    Sent: Thursday, June 18, 1998 8:06 AM
    To: 'Sean Brown'; 'John Jamison'
    Cc: [email protected]; Jose Suriol
    Subject: RE: Is there a way to have 2 network cards on the same machine
    Sean,
    Thanks for your reply. I tried the approach. I was not very specific in
    my
    question. I do need the ability for server applications to listen and
    server
    on both the network cards.
    I was succesfully able to make the nodemgr listen on both the cards and
    actually serve requests coming in from both the cards. But, following your
    advise, I took a cautious step with FORTE_LOCATIONS. Here is what I
    noticed.
    I have an application that has 6 partitions in total. I used
    FORTE_LOCATION
    to make it listen on 1. Both the cards. 2. Swapped the IP addresses for
    both
    cards for this application. 3. One card that I want it to listen on. I
    tried
    all approaches by exporting the locations variable for just this
    application. The nodemgr recieves a request from this pc connected on the
    second card to talk to one of the partitions. The node mgr responds with a
    proxy - with the ip address and socket number of the first card. The
    FORTE_NS_ADDRESS variable looks like this:
    IP1:5002;IP2:5002.
    Is it possible atall to resolve my problem, without having a seperate
    environment?
    Thanks
    Venkat Kodumudi
    Price Waterhouse LLP
    Internet: [email protected]
    Internet2: [email protected]
    -----Original Message-----
    From: Sean Brown [SMTP:[email protected]]
    Sent: Wednesday, June 17, 1998 10:42 AM
    To: 'John Jamison'; Venkat Kodumudi
    Cc: [email protected]
    Subject: RE: Is there a way to have 2 network cards on the same
    machine
    Venkat,
    Actually, it is possible for Forte to listen on more than one IP andport
    combination. The first reply to your message was correct. If you setthe
    FORTE_NS_ADDRESS to contain multiple entries before starting the name
    service, it will advertise on both. For Forte servers you use the
    FORTE_LOCATIONS env variable to get it to advertise on multiple ip:port
    combinations.
    We were doing something very similar with another customer I was at toget
    around a firewall. I will warn you that there are some issues with
    FORTE_LOCATIONS that may keep that portion from working. However, from
    reading your note, it appears that all you need is for the name serviceto
    advertise and listen on multiple ports and that works fine. I justtested
    it again for sanity sake and it worked. I ran my test on NT using Forte
    3G2.
    Sean
    -----Original Message-----
    From: [email protected]
    [<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of John Jamison
    Sent: Tuesday, June 16, 1998 4:51 PM
    To: Venkat Kodumudi
    Cc: [email protected]
    Subject: Re: Is there a way to have 2 network cards on the same machine
    Venkat,
    Technically yes this is possible, though not in Forte. A name server
    can
    only listen on one port.
    To implement this scheme you will have to write a proxy service (in some
    language
    including perhaps forte) which listens on the well-known port on the
    second card, reads requests, then forwards them to the real nameservice
    (wkp on the first card), and forwards replies back. This is not
    trivial, but some firewall toolkit vendors supply stub code to write
    application specific proxies.
    -J
    Venkat Kodumudi wrote:
    Folks,
    Here is what we would like to do:
    We want to have 2 network cards on a unix box - which means I have 2ip
    addresses, and the connection between the two is the unix box and onlythe
    unix box. I have a pc connected to the 2nd network card and I want it
    to
    connect to the nameserver that is listening on a well known port onthe
    first network card. We don't want to turn IP forwarding between thetwo
    cards. We want Forte to address both cards to talk to clients, in one
    environment.
    Can this be done? If so how?
    Thanks in advance.
    Venkat Kodumudi
    Price Waterhouse LLP
    Internet: [email protected]
    Internet2: [email protected]
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive<URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
    >>
    John Jamison [email protected]
    Vice President and Chief Technology Officer
    Sage IT Partners, Inc.
    Voice: 415 392-7243 x 306
    Fax: 415 391-3899
    Internet Enabled Business Change
    <a href="http://www.sageit.com">http://www.sageit.com</a>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

  • TS4611 Guys if you have these build: 12E3200 and your wifi is dropping, is not the your mid 2013 macbook air, is your router, I solve it by setting up my time capsule as a new network problem solved

    Here is what I have been doing:
    I got my new macbook air 11" two weeks ago, and have been haven problems with wifi connection dropping, I'm using verizon fioz at home, and their router
    I also have a time capsule not set up as a network just join it to my current one.
    After looking online all these days, I though, maybe is the verizon device that is updated..
    I then reset the time capsule, created a new network
    connected my system to the time capsule network, and there it is
    DONE, everything works now.
    So if you are haven the same problem,, that is the fix
    hope that helps.
    Oh  before I did these I try everything, the wifi update from apple don't work it keeps dropping it
    I try everything, so don't and delete the system as some people have done, I read somewhere.
    try my fix hopes that works.
    Message was edited by: rawreviewer

    I have seen lots of issues on Yosemite with Wifi (and have been having issues myself), but yours seem different. It is a pretty new computer, have you tried taking it in under Applecare (if you live somewhere this is convenient)? Maybe you just got a defective wifi card.  I won't defend Apple over this wifi mess, because it really is terrible, but your issue seems not the same as the ones I've read about while researching how to fix mine (unsucessfully....).

  • Do I need a new Wireless Card?

    Please bare with me while I tell the whole story...
    Ever since I installed Leopard, my MacBook has been having a big problem. 25% of the time, when you closed the lid, it would crash instead of going to sleep. It seemed to even be getting worse. So last night, when I was leaving an appointment, I closed my MacBook and put it in my bag. I talked to my customer for a few more minutes then I headed home. It was rush hour so it took a while. I stopped at the post office to check my PO BOX, and I had mail yay. When I got home, I looked through the regular mail to see if I had anything. I brought my bag upstairs, checked my email and IM's on my Mac Pro. Finally, about an hour and a half after putting it in the bag, i opened my bag to take out the macbook and plug it in. It was on FIRE. Hotter than it's ever been before. The fans were running full speed, and it was hard to hold. So I turned it off and let it sit for a while. When I turned it back on, my airport card was showing as turned off, and I couldn't turn it back on. Clicking 'turn airport on' wouldn't do anything. I had this happen once before and a few minutes later it came back on. But not this time. A day later, and several restarts and shutdowns later, still nothing. I did to an archive & install, which was something I was planning on doing anyway to try to solve the crash on lid close problem. Oddly enough it doesn't seem to be crashing when I close the lid anymore. So did the archive and install fix the crash problem, and did the crash problem cook my airport card? Or did I have a defective airport card all along and was that causing the crash on close problem? I also ran the Hardware Test several times and it found no problems at all. I'm also 3 months out of warranty. I know where to get a replacement card, they are only about $60, but is there a way for me to verify for sure, that is what the problem is?

    So forget the whole thing.
    I got my airport working again. How? By unchecking "Ask to join new networks". Location by location, unchecking this option would instantly turn AirPort back on. Looks like Leopard still has some bugs to be worked out.

Maybe you are looking for