Possible ethernet adaptor corruption?

Yeah you gotta get a router so that they can both get an address from a 3rd machine (the router) to create a network that they can communicate across.

Sorry to disagree but you do not need a router... you are referring to DHCP which is one of the many services some routers can perform.

The only thing he is going to have to do is configure the tcp/ip stack on each computer with a static ip address/subnet mask otherwise he will get an APIPA(automatic private ip address address)... anyone in the network field will know what i am talking about.....

have you tried uninstall/reinstall of nic drivers.

Allow me to rephrase then. To do it EASILY get a router. You plug stuff in, it works, no questions asked.
(I AM in the network field, sheesh )

A router is precisely what I am getting in prep for the arrival of bband. At the moment though I have changed the IP addresses on both PC's to 192.168.0.x and have disabled the firewall. I personally think that this is my major problem though :

The COM+ Event System detected a bad return code during its internal processing. HRESULT was C0000005 from line 44 of d:\qxp_slp\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

It always happens whenever I turn on the adaptor. Unless of course it's just my PC telling me that it's getting a bad return call from the network, as I don't get this error if the cat5 cable is unplugged from either my PC or the actual hub.

I'll have a go with another HUB of mine, see if that changes anything.

Ok so updated all the 2 NIC's. Whats strange is that my one PC recognises the fact that the other PC is on the network. The PC's name is there in workgroup and yet when I select it it says ''Network Path not Found''. Both PC's also recognise that they are connected to a network they just simply will not communicate with each other, and it's not a problem with the HUB, just had 3 XBOX's linked to the very same HUB with no problems.

Sounds like a driver issue of some sort.

What happens if you uninstall your NIC driver and re-install? Do you get the same message?

Also, do you have Norton's installed by chance?

I found this thread in another forum that might be a start point.

http://eventid.net/display.asp?eventid=4609&eventno=1993&source=EventSystem&phase=1

I had the same problem too and it had to do with Norton Anit-Virus. For some reason, Norton AV blocked communication between the two computers connected through a router. I would think it's firewall or AV of some sort.

cT

tdeg said:

Sounds like a driver issue of some sort.

What happens if you uninstall your NIC driver and re-install? Do you get the same message?

Also, do you have Norton's installed by chance?

I found this thread in another forum that might be a start point.

http://eventid.net/display.asp?eventid=4609&eventno=1993&source=EventSystem&phase=1

Click to expand...

Tried rolling back the NIC drivers, and I don't have Norton but I do have AVG. Thing is, I used to use a wireless network card for my PC to connect to my other PC (which was connected to the very same HUB as I am using now, then connected to a WAP) but then I moved my room outside and could get no signal. So now I have created a 15m (Fully tested and operational) cat5 cable running from my room to the HUB. That link you gave me is where I first went, unfortunately I'm using XP Home which lacks ''Local Policies'' file. All I can think of is that my ethernet adaptor is configured incorrectly as this message points at a memory access violation. I will be trying with an external PCI NIC in about an hour so will see if that works. I doubt this problem has got anything to do with my other PC as that has used the same NIC on the same network for the past 3 years.

By the way should I manually be using my own IP's? Since my dad taught me about networking I always setup a particular network with IP address 192.168.0.x and subnet 255.255.255.0.

Another quick question, I was wondering if anyone could verify that the setup I plan to create in the near future will work, I've attached the file.

{EDIT} Just found in the BIOS that my ''onboard LAN boot ROM'' is disabled whilst Onboard LAN is enabled. Does this mean anything?

OK IT's WORKING! So what I did in the end was. I never got another PCI nic. Instead I got a HUB 10/100 put that in my room and did the following setup:

My PC --- HUB ------ HUB (via uplink port) --- Other PC

The network works perfectly now. However I am getting collisions in the HUB which is probably standard and doesn't mean anything as I'm currently playing music through my other PC and browsing it's files

{EDIT} No more collisions, pushed the wire fully into the socket

Yea, you need to use an uplink port or a crossover cable to connect 2 hubs.

Not to sure why this setup did not work :

My PC ------------ HUB --- Other PC

Perhaps it was because of the distance between the PC and the HUB (about 15-20m)? Anyway, I may rework the wires to act as a crossover wire, I heard that they have less collisions. I'm still getting a few occasionally, they don't do anything really.

Double check your cables, maybe one of them is a cross-over cable and you didn't realize it.

And 15-20m is nothing for ethernet if your cable is ok. You usually run into problems are you approach 100m.

I thought for new hubs you don't need crossover cable. It would automatically detect what you are using and config. it to make it work.

cT

I know switches will do that , but maybe he just got a cheaper one that doent auto correct for it?

The network is running great at the moment. Just got off a LAN game with my bro on Warcraft 3 with absolutely NO LAG or any collisions. All the wires I am using are standard ethernet cables, no crossover ones. I'm using 2 HUBS with one connector in the uplink port of one HUB and in a standard port of another. It's weird, I've got 3 HUBS and only using the current 2 in unison does this network work, any other combination of HUBS fails to work....The one I'm using at the moment is fairly new though (2002) and the others are like 1998 and 1999.