Network card not relinking..

Last night, our local router siezed up and had to be rebooted. When we brought the router back up, the network card in our proxy server(SuSE Linux) failed to link back up. I was asked to look into the situation and see what kind of sollutions I could come up with. Does any one have any suggestions. I've seen ifplugd and it seems to be what we need, but does anyone have any experience working with this or any other suggested sollutions? This is our first experience with a linux server in a production environment. Also..just a note, the server runs SuSE linux because the admins that I work with like the sescurity of a support contract(understandably so).
Thanks

medicated wrote:Wouldn't the system assume that the cable was uplugged? It will no longer be linking up to anything, so whats the difference between that and simply unplugging the cable?
dunno... I was just covering all the bases... I'm not sure how much of a "link down" ifplugd needs to reconnect... hitting a "reset" button might cause it to not relink... I dunno
Best to just try it out on a desktop of your own (run ifplgud, shut the router off, restart... checking pings and whatnot the whole time)

Similar Messages

Oracle Linux 6 update --- wirelees network card not working.

Hello,
The only problem I am having is with my wireless network card(built-in). Should I buy a new wireless card that can be used with Oracle Linux?
Here is some info about my laptop:
$ lspci -v | grep -i net
04:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05)
$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
virbr0 no wireless extensions.
virbr0-nic no wireless extensions.
$ lsmod
Module Size Used by
fuse 49340 0
ipt_MASQUERADE 1780 3
iptable_nat 4651 1
nf_nat 16615 2 ipt_MASQUERADE,iptable_nat
iptable_mangle 2603 0
tun 9430 1
bridge 39245 0
stp 1503 1 bridge
llc 4140 2 bridge,stp
autofs4 18216 3
sunrpc 168053 1
cpufreq_ondemand 6844 4
powernow_k8 12957 0
ipt_REJECT 1621 4
nf_conntrack_ipv4 7140 6 iptable_nat,nf_nat
nf_defrag_ipv4 1033 1 nf_conntrack_ipv4
iptable_filter 2123 1
ip_tables 8337 3 iptable_nat,iptable_mangle,iptable_filter
ip6t_REJECT 3390 2
xt_tcpudp 1879 6
nf_conntrack_ipv6 14880 2
xt_state 1042 5
nf_conntrack 59159 6 ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4,nf_conntrack_ipv6,xt_state
ip6table_filter 2231 1
ip6_tables 9601 1 ip6table_filter
x_tables 12478 8 ipt_MASQUERADE,iptable_nat,ipt_REJECT,ip_tables,ip6t_REJECT,xt_tcpudp,xt_state,ip6_tables
ipv6 225173 34 ip6t_REJECT,nf_conntrack_ipv6
uinput 5260 0
rfkill 13768 1
i2c_piix4 10150 0
joydev 7304 0
microcode 11243 0
uvcvideo 47429 0
videodev 29537 1 uvcvideo
v4l1_compat 11137 2 uvcvideo,videodev
i2c_core 23454 2 i2c_piix4,videodev
pcspkr 1386 0
serio_raw 3380 0
r8169 29689 0
mii 3889 1 r8169
snd_hda_codec_realtek 197227 1
snd_hda_codec_atihdmi 2039 1
snd_hda_intel 19505 2
snd_hda_codec 62689 3 snd_hda_codec_realtek,snd_hda_codec_atihdmi,snd_hda_intel
snd_hwdep 4852 1 snd_hda_codec
snd_seq 43513 0
snd_seq_device 5326 1 snd_seq
snd_pcm 63799 2 snd_hda_intel,snd_hda_codec
snd_timer 16064 2 snd_seq,snd_pcm
snd 49098 12 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer
soundcore 5387 1 snd
snd_page_alloc 6456 2 snd_hda_intel,snd_pcm
usb_storage 35626 0
ahci 28838 2
pata_acpi 2307 0
ata_generic 2403 0
pata_atiixp 2852 0
ohci_hcd 25812 0
video 16346 0
output 1723 1 video

The actual problem seems to be that you are using the wrong Linux distribution for you Laptop. Enterprise Linux was not designed for consumer grade hardware. To further troubleshoot the problem you will need to check for relevant output of "dmesg", i.e. check if the firmware and driver that was loaded for the device. You should also check "lspci -v" w/o grep to see more detailed information for the device.
Are you trying the latest Oracle Linux 6 update 2?
What is your hardware?
Beware that no Oracle database products are yet certified for EL6 yet, so you should better stick to Oracle Linux 5 update 7 instead.
If the purpose of your installation is research and development I suggest to install Windows as your primary OS and run Oracle Linux inside Virtualbox. Check the following link: http://www.oracle.com/technetwork/community/developer-vm/index.html

ThinkCentre M71e PCIe network card not showing up

I bought a ThinkCentre M71e (3134-C4U) with the intention of using it connected to several separate physical networks. I bought a PCIe Network card (SuperMicro AOC-SG-I2) with two additional network ports to use for this purpose. As far as I can tell, this network card should work with no problems - it's a PCIe 2.0 x4 card, which should work in the system's PCIe 2.0 x16 slot.
However, the computer does not recognize that the network card is there! To test whether it is an issue with the card, I pulled a similar card (known working HP NC360T) from another computer, and this computer did not recognize it either!
What can I do about this? The computer is useless to me without the additional network connection.
I noted that, while the specs explicitly say "PCI Express 2.0 x16", the Hardware Maintenance Manual calls it a "PCI Express x16 graphics slot" (emphasis mine). Does this mean that Lenovo deliberately prevents cards other than graphics cards fro mbeing recognized in this slot?
UPDATE: I see now that someone else had this exact question two years ago, with no response.

There a long thread about this on the 123MacMini forum. At page three, they mention drivers (you need drivers, right?) and there is a link...
http://www.123macmini.com/forums/viewtopic.php?t=22943&postdays=0&postorder=asc& highlight=pcie+sata&start=30
Actually, that thread might refer to a different, but similar, card.
Don't know if it finally worked. Be very interested to hear. (Not sure why Apple is/has always shunned eSATA?)

Network card not found after new installation [SOLVED]

I broke my filesystem on my Asus UL80V series laptop in trying to solve problems related to the latest glibc update, so decided to do a clean re-install. I had an installation disk at hand: 2009.08 with kernel 2.6.30.4-1 (which is supposed to have the module for my ath9k network device). However after a successful installation (including all the files from base-dev), my network device is not recognised:
dhcpcd: eth0: interface not found or invalid
although network connectivity (wired and wireless) worked perfectly before the installation attempt.
This happened yesterday (17th) and I have been scouring the web since trying to find out what the cause of this problem is, without luck.
I also burned a new installation CD with the latest stable version, but no luck there, either! Got a message at the beginning informing me that the install requires 64 Mb memory, although my laptop has 4 Gb.
I should say, the device is there and working:
lspci | grep Net
gives
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
I also did
modprobe ath9k
just to make sure. No luck.
Any help will be appreciated.
thanks
thea
Last edited by thea (2012-07-23 23:59:16)

Argh, ip may not be around in the 2009 image really ;-) .. Use "ifconfig" instead..
But: I meanwhile cross-checked your ath9k: http://wireless.kernel.org/en/users/Dri … h9k_driver
and it does not sound encouraging for the kernel you have there.
The image is far too old anyway, if you ask me (would be a darn hazzle to get that uptodate I am sure). Pity you get that memory error with the 2011 one. Maybe check forums on that. Sounds very strange, I am not aware of any post I read.
If you can burn another CD, you can try the recent ISOs as well: http://releng.archlinux.org/isos/
Beware that the ones from July dont have the AIF setup anymore.

Solaris 10 - Installation - Networked Option not display- RTL 8139 NIC Card

Hi,
when i installing Solaris, the Networkd (Yes/No) option not display. In my PC (x86) RTL 8139 Networkd Card is installed. Please advice, how can i enable Networked option and docs says that Solaris-10 Supports RTL 8139 Network card. (Ref: http://www.sun.com/software/solaris/self_help.jsp#installing )
Here pls refer "Network Devices (x86)" Section ).
Thanks

I'm not quite sureee, but you might want to run the SDDT test scripts...
http://www.sun.com/bigadmin/hcl/hcts/device_detect.jsp
This you can run from Windows, Linux on the same box, and it will list all the drivers for the hardware that solaris knows about. Inside the tool you can select, whether you want that list for Solaris 10 or SXDE...
Matthias
P.S.: I assume, the driver should be e1000g, but am not quite sure...

Network card: e1000g (Intel PRO/1000 MT) did not working properly

Hi to everyone!
I'm having some strange trouble.
All computers attached to one DLink gigabit switch
Server #1:
nf4-based motherboard, Intel PRO/1000 MT net card, onboard net card (forcedeth driver used) Ubuntu Linux 2.6.25 kernel version.
All just working.
Server #2:
nf6-based motherboard, same Intel net card, SunOS 5.11 snv_86.
All just working.
Server #3:
Same as server's #1 nf4-based motherboard. Same onboard card. Same SunOS 5.11 snv_86 as server #2 have installed.
Its work. BUT..
Intel card is not working as expected.
It is seen by system. It is properly up and running. It is sending packent and receiving packets. Ierrs=Oerrs=Collis=Queue=0.
But thru e1000g0 interface no one computer can reach this one, and from server #3 no one computer is seen thru e1000g0. Exept...
Except two old Sunray1 devices (attached to the same switch for testing purposes)! But even these devices seen only by arp requests, and is not pingable.
It is some mistery, but if I turn on jubmo frames, these rays got a picture from SRSS, testing on this sevrer! Not for long, heh, they hung up fast, but this is proof a physical connection :)
So, I can not disable onboard network card on Server #3 - server becoming unreachable :(
I know, those network cards must work on Solaris - as they did it on server #2. I know, those network cards work with my nf4-based motherboards - as they did it on server #1.
But I can't uderstand, whait is going on with e1000g driver on server #3!
P.S. Kernel driver e1000g settings are the same. All difference from servers #2 and #3 is: #2 had Intel netcard installed then Solaris was setting up, and #3 had Intel netcard installed later. All netcards are working (I trying to swap them from one computer to another - did not change anything).

*) #3 thinks it is sending, but a NIC/driver error prevents it.NIC is fully health. It is tested on another PC. Driver error - or driver's bad implementation - is the one I'm thinking.
*) #3 has a bad transmit pair of wires (would affect all communication)This patchcord works w/o problems on other PCs and even on onboard NIC of server #3.
*) Network problemsHeh :)
*) Firewall or other device is dropping the ARP repliesIt is some very stealthy and very selective firewall, affecting only external NICs :)
BTW, then cord is attached to NIC, it sends "who has this IP" requests, asking to be shure there will not be an IP conflict. No one seen this requests.
*) #1 has a NIC/driver error preventing it from seeing the reply.Only for send from #3? It is like a firewall on #3 :) And, there is more PCs, not only #1-#3. No one can see #3's replays (or asks), not only #1..
I'm repeating: this PC works in network now on onboard NIC w/o problems. But onboard NIC is only 100 Mb/s, and we need 1 Gb/s.
I was thinking, Solaris took wrong MAC for NICs - but not, ifconfig shows the same MACs as marked on NICs.
Even more, yesterday i plumbed e1000g1 - second Intel NIC in server #3. And I was surprised - it worked perfectly!
But I make "touch /reconfigure; init 6" - and after reboot, no one of two Intel NICs working again :( They both have the same behavior - no one can see packets they sends.)
I even try to restrict connection on 100 Mb/s by driver's .conf modify - it works, link become yellow instead of green (take a note, NIC is able to "speak" properly with switch!), but all other stay the same.
Strange, really strange behavior. More strange is a fact this NICs work on another instance of same SunOS, but on different motherboard, while the same MB with same NIC is working w/o problems under Ubuntu. Looks like some bug in Solaris driver.

Airport card 802.11b sees other networks but NOT my network!

Hi. Having a very strange tech issue today...
I have a 1ghz ti-book that no longer wants to connect or even SEE my home network after waking up from sleep. Up until today there has never been an issue. My home network is distributed via a Netgear 802.11b and g wireless router. Again, I have never ever had any issue whatsoever connecting to my network. WEP is enabled. There are also 6 other computers all connecting to the same network via wireless too. No problems.
The crazy thing is I know the card is still functioning properly because I can still see all the other available networks around in my area. Even when I place the ti-book RIGHT NEXT to the antenna on the netgear router, it refuses to acknowledge that it is there. Meanwhile, it is showing all of my neighbors networks just fine!
The only variable in this equation is that the hinge of the display is damaged, such that it won't stay open "by itself". The display normally has to be propped up against something. The machine works fine otherwise, no issues. The weak bezel breaking is an issue that many ti-book owners faced and it has been broken for a LONG time with no performance issues at all. The only thing I can think of is that maybe the wire to the antenna for the Airport card goes up the side of the display and somehow the wire is damaged or frayed. I don't know if this is how the ti-book was designed....does anyone know? Specifically, if the wire for the airport card runs along inside the case of the display on the 15 inch 1ghz ti-book?
If it does not...and it seems like it is not hardware damage to the cable because how else could I still be getting other networks but not my own...then I am stumped as to how to trick my machine into recognizing the network again. I have done the basic things such as booting into single user mode and rebuilding my index, logging in as root and other users to see if the preferences were corrupt, and even installing a bunch of wifi wardriving apps to force recognition of my network and still nothing!
Again the machine is right next to the access point, so what is causing it to no longer "see" it? I also updated the firmware in the router and checked configurations but no changes have been made and all the other machines work fine. Also it has NEVER done this before so I don't know how to troubleshoot it!
*What would cause an airport card to reject the signal that it is configured to connect to? How should I go about getting it to see the network again...without reconfiguring the network which would mean having to update all the other machines, etc.* I have macstumbler and istumble running and they see PLENTY of networks except for the closest one. It is so bizarre. It was working when I went to bed and now today, no network. I have rebooted numerous times, etc.
please help!! i need some ideas!!!
thanks!

a somewhat in depth search across the interwebs has lead me to the conclusion that this problem is also affecting Leopard users as well. (I am on old hardware and running the latest Tiger) To be honest, I can not remember if there was an Apple update right before this problem started to happen. However, it seems real enough and many users out there are having problems re-connecting to their home/work networks after waking from sleep.
just to clarify:
Using a ti-book with normal airport card installed (b not g)
Connected to a Netgear wireless router (configured to manage both b and g traffic)
WEP 64bit encryption key is being used for network
No problems whatsoever until a few days ago
what works:
unplugging the power to the Netgear router (cycling power)
what doesn't work:
waking from sleep
restarting
manually entering network name and password
using 3rd party apps to find network
resetting/deleting Network location preferences and creating new one
deleting AppleAirPort2.kext from /System/Library/Extensions/
using either Diagnostic or Assistant mode to reconnect from scratch
it should NOT be this difficult to solve a networking issue. what is going on here?

XP not seeing any network cards

I have XP running through Bootcamp but am not able to see a network card. I do not seem to be able to find any drivers to use. Any suggestions?

Stefan,
thanks for your response......... not looking for excuses but.... I am new to this 'Mac World' and I did not think for one minute that the OSX DVD would have anything to do with MS Windows once it was up and running!!!!!!
Unfortunately I'm away from my Leopard disk until tuesday but it sounds like my problem will be solved.....
Thanks very much,
Tim

OEL6.1 in VM manager does not see network card

I installed OL6.1 as a guest machine in VM manager. I started the install process and when I got to the network configuration it would not let me click on "configure network", it was greyed out. I thought that was a little bit odd but I just thought that I would configure it later. Once I got to the desktop of OL6.1 i checked for the eth0 settings but there was no eth0 at all. The OL6.1 did not even know a network card existed, but I tried to add it manually and still it did not see anything and would not connect to the internet. Has anyone seen this problem before? Thanks.

I will try to answer to the best of my knowledge your questions but I am a bit new at this. I downloaded the OEL 6.1iso media from Oracle site, I then imported it into the resources section in VM manager 2.1.
I then used the create new Virtual Machine and selected the server pool.
I selected the ISO file with OEL 6.1.
I gave it a name, memory size, console password.
Below that I can see the Virtual Network Interface is selected and it shows Bridge xenbr0.
It is showing Fully Virtualized machine not paravirtualized mode. As far as I know I did not install in Xen HVM or with PV drivers.
That is about all I did. Then I started the machine and when through the install process but it did not see the virtual network device.

X200s WiFi network Card is not shown in Device Manager

Hello,
I have a X200s laptop. WinXp is installed on it.
The problem is that the WiFi network card is not listed in device manager under network cards. And the Wifi led is always off. Only bluetooth and Wireless wan leds are on.
Can anyone help me, I need to let the XP detevt the WIFI adapter.
Thank you.

i have the same problem. Can you tell what to do

HT1349 before i do updates for my iphone(to 5.0.1) i close my SIM card, i can not complete the update proccess becouse SIM is closed also i can not activate iPhone becous the SIM must be opened. when i try to open it , the networks does not appear (no se

before i do updates for my iphone (to 5.0.1) i close my SIM card, i can not complete the update proccess becouse SIM is closed also i can not activate iPhone becouse the SIM must be opened. when i try to open it , the networks does not appear (no service).

Its a serious problem and many people are facing the same issue on both locked and factory unlocked phones.
I wonder when Apple will address to this issue. After all it is losing all its reputation!
See this thread, many users are encountering the same issue:
https://discussions.apple.com/thread/3425746?start=75&tstart=0
I believe its a software issue and could be solved asap Apple fixes it!

Boot Camp Windows 8.1 Installation Did Not Install Network Card

I just installed a Windows 8.1 Boot Camp partition on a new Mid 2013 MBA. The install ran the support software and installed the drivers. However I don't show any network cards in my Windows 8.1 installation. I reran the support sw manually and it went through and supposedly fixed any driver errors but I still don't see a network card or have a network connection. It works just fine in my OSX partition, so it is definately a driver issue. *** do I need to do to get the network driver installed?

In Thehatters defence, this was initially posted in the MacbookPro forum and then moved to Boot Camp,
If you have any joy solving your trackpad device driver issue, feel free to post here (there might be a similar fix for my wireless adapter device)
Thanks

X230 / mSATA SSD - Will not allow boot (unauthorized network card)

this is killing me. I just got a crucial msata ssd. i went to install and the thinkpad whitelist fcc crap is giving me trouble. the system thinks it a network card and is therefore stopping the boot. i see others have installed msata on x230 and I have done this on other models as well.
does anyone know a way around this that doesn't envolve changing the bios to a custom bios hack?

Hello,
I don't have an X230 myself, but have you tried using a different MiniPCIe slot? On my X220, only one of the MiniPCIe slots is mSATA compatible. Perhaps it is the same way with the X230.
Regards,
Aryeh Goretsky
I am a volunteer and neither a Lenovo nor a Microsoft employee. • Dexter is a good dog • Dexter je dobrý pes
S230u (3347-4HU) • X220 (4286-CTO) • W510 (4318-CTO) • W530 (2441-4R3) • X100e (3508-CTO) • X120e (0596-CTO) • T61p (6459-CTO) • T43p (2678-H7U) • T42 (2378-R4U) • T23 (2648-LU7)
Deutsche Community Comunidad en Español Русскоязычное Сообщество

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>>

Updated bios via Live Update and now my Network card isn't detected

I have an msi Z87-GD65 Gaming Motherboard and I updated some drivers and the bios via msi Live Update 6 last night and now my computer refuses to recognize my network adapter. The adapter is a TRENDnet N600, plugs into PCIe if I'm not mistaken. Wifi if my only option with this computer, I can't use ethernet, so it's really important I get the network card working again. I have had zero issues with it until this.
The reason I was updating was to try to get my third monitor to work when plugged into the mobo, while my other two were plugged into the graphics card (which I also installed yesterday, but it's working fine). Note that it still was not working, but I had enabled the IGD Multi-Monitor from bios.
Any suggestions would be appreciated. I did try uninstalling the drivers but it still won't detect the network card. I also tried disconnecting and reconnecting the network card (and I cleaned the port for good measure).
I've only been using Windows computers for a year, so bear with me if there's stuff I don't know. Thanks in advance. I can try to get a full list of what was installed later tonight, but all of it that I can find has been uninstalled at this point.
Note: I did not flash the bios when I installed, which I have now heard is a bad idea, apparently. l:

what OS you are running?
Quote
Note: I did not flash the bios when I installed, which I have now heard is a bad idea, apparently. l:
you said you've updated drivers & BIOS:
Quote
I updated some drivers and the bios via msi Live Update 6 last night and now my computer refuses to recognize my network adapter.
can you clarify is you update BIOS too or not?
and what is your current bios version?
Quote
and I updated some drivers
what kind of drivers?
Quote
I did try uninstalling the drivers but it still won't detect the network card. I also tried disconnecting and reconnecting the network card (and I cleaned the port for good measure).
have you tried to load last good known configuration or the last windows restore point?
or to reinstall OS?

Network card not relinking..

Similar Messages

Maybe you are looking for