A7N8X-E - Network problems...

  • Thread starter Thread starter Brian
  • Start date Start date
B

Brian

I have 3 computers connected via a DSL router. Previously, everything was
fine. After putting this mb in one of the computers, things are not quite
right. maybe someone can explain something.

When windows first booted up, it showed the network cable unplugged icon,
even though it was plugged in. I specified its TCP/IP info but it simply did
not work. Could not ping any other computer, etc. So I installed the gigabit
LAN driver, and disabled the regular one, and things are better. I can
browse the internet, I can establish remote desktop connections, but I still
can not browse the network. It says something about authorization. Anyone
know why everything seems to be fine except accessing the network? I mean, I
can ping the network computers, but I can't access any folders on them. Does
it have to do with the fact that none of the others are using gigabit LAN
drivers? Do I need to use the regular driver (in which case I am at a loss
because of what I said above...)?

thanks,

brian
 
sounds like an XP config issue..do you have the internal firewall enabled in
XP?...or are you running outside software..eg Norton Internet
security..etc..because of the LAN adapter everyting is probably being seen
as different..I know I have no issue connecting any computer to my Linksys
Router
 
Things seem to be ok now (with gigabit LAN anyway). I guess when I ran the
network setup wizard, I chose the wrong option. But I re-ran it, paying
closer attention to the options, and all is well.

-brian
 
Brian said:
I have 3 computers connected via a DSL router. Previously, everything was
fine. After putting this mb in one of the computers, things are not quite
right. maybe someone can explain something.

When windows first booted up, it showed the network cable unplugged icon,
even though it was plugged in

It? Which one? The Marvell (I think it's a Marvell - the Gigabit one) or
the nVidia one? You have two NICs.
I specified its TCP/IP info but it simply did not work.

Again, which one.
Could not ping any other computer, etc. So I installed the
gigabit LAN driver, and disabled the regular one, and things are better.

Right, so you were talking about the nVidia one? And you swapped the cable
over too?
I can browse the internet, I can establish remote desktop connections,
but I still can not browse the network. It says something about
authorization. Anyone know why everything seems to be fine except
accessing the network? I mean, I can ping the network computers, but I
can't access any folders on them.

Then you can be sure that IP works, if IP works, then the physical layer and
MAC stuff works, so stop looking atthe NIC and start looking at the
protocols for that NIC. Networking in Windows is an art I have not yet
mastered (since the terms they use are ambiguos - disabling DNS does not
disable DNS, for example). I would look at NetBEUI if you have any non
Win2K/XP machines on the network, and have a play with the netBIOS options
too.

When you say you can't access them, is that 'cos you can't see them or are
not authorised to?

I have found that setting up an account on the machine you wish to gain
access to ("server"), with the same username and password as the client
machine, is a pretty satisfactory way of enabling shares as it logs you in
automagically. So provided your username has access to those shares on the
server, it'll work.
Does it have to do with the fact that
none of the others are using gigabit LAN drivers?

Nope, the Gigabit card should just drop to the speed and duplexicity (new
word!) of the other end and just work.
Do I need to use the
regular driver (in which case I am at a loss because of what I said
above...)?

Ok, I'm a bit unsure of this regular driver/Gigabit driver stuff. I take it
there is a driver for the Marvell and a driver for the nForce.

If I was me (and I am, funnily enough) I'd use the nForce NIC, unless I was
getting gigabit speeds (which you won't be).

The only problem with the nForce NIC is that it can get assigned the wrong
MAC address (one that doesn't work) when you reflash the BIOS, but since
there is only one BIOS for the -E, I don;t know why that might have
happened. Do an IPCONFIG in a CMD prompt and check the MAC address against
the one printed on the IDE/Floppy connector.

I would look at your network config in Windows - NetBUEI

Ben
 
Back
Top