** Dell Computers - No Longer Networkable ** 1

[markjrees]

A client of ours purchased 4 Dell Dimension 3000 computers and asked us to network them in a peer to peer workgroup environment. the 4 workstations were running XP Home.

We arrived on site and began networking the 4 systems. We simply plugged the four computers into an 8 port switch and joined each computer into the same workgroup (called Workgroup). Each computer had an ip address (192.168.254.1 through to 5).

As always to verify connectivity we issued the Ping command from dos however we got 4 x destination unreachable messages. none of the workstations could successfully ping any of the other workstations.

we swapped both the switch and the network cables with known working ones but still no connectivity could be established. We even went back to basics and ran the XP networking wizard. no joy.

We called Dell support (india) who were no use at all. We're MCSE's and they knew next to nothing about anything.

In the end we had to put the problem down to a hardware fault and as Dell will not confirm this our client has basically cancelled the credit card payment so Dell don't get their money.

Anyway. We've since spoken to our sales contact at Dell and it looks like they may be modifying the Dimension range of computers so that they cannot be networked (in a workgroup environment). Possibly a hardware modification.

Either way we couldn't get the 4 dimensions to network and it's something we do (with other models/makes) on a daily basis.

has anyone else had a similar encounter?

http://www.accountantjokes.co.uk

http://www.markjrees.co.uk

http://www.mjrcomputersolutions.co.uk

http://www.mjrfm.co.uk

 

[markjrees]

the switch is a basic 8 port thing. not configurable at all.

we tried different cables and different switches.

we are however taking delivery today of 4 identical dimension 3000 workstations for use in our office. we intend to replicate the network of our client and see if we have the same problem.

if we dont then chances are it's the nics

http://www.accountantjokes.co.uk

http://www.markjrees.co.uk

http://www.mjrcomputersolutions.co.uk

http://www.mjrfm.co.uk

 

[bcastner]

markjrees,

The switch issue is unlikely, but possible.
The NIC issue is possible, but unlikely.

Focus on the ping issue. Uninstall, not disable, all firewalls and AV software.

Once the ping issue is resolved, everything else will be easy.

I am sorry you found my earlier advice 'ludicrous'.

No matter, what is important is that there are people on this Forum with substantial technical resources available that are willing to help you with this issue.

Bill Castner
MS-MVP Windows Networking

 

[markjrees]

we really do appreciate all the help so far - even as MCSE's this problem stumped us

http://www.accountantjokes.co.uk

http://www.markjrees.co.uk

http://www.mjrcomputersolutions.co.uk

http://www.mjrfm.co.uk

 

[bcastner]

There has been some serious head scratching going on in the private newsgroups for MVPs.

The missing ACE permissions on Guest, for recent XP Home images was tough, complicated by the fact that XP Home does not have the weapons of XP Pro.

The further complication is the post-Service Pack 2 distributions of Norton/Symantec, and McAfee that are often included as a base install for new systems.

Right now I just use an unattended install or RIS to re-image Dell, HP, and IBM new boxes. It is easier to have a known base install that you control, rather than depend on the OEM image.

The OEM image is likely fine for most users, and provides a valid license for the machine. But it is not my image, and I feel more comfortable controlling the entire setup.

With the new boxes you have a valid license. 4 boxes is tough, but ask the VLK folks at Microsoft anyway. A properly done re-image of the machine as you want is perfectly valid.

http://www.msfn.org/unattended/xp/index.htm

 

[markjrees]

to be honest when we buy new machines for the office we clear them down and put our own install of XP Pro on them. with client computers as we don't supply them, and because the client pays hourly we tend to just use the OEM install.

http://www.accountantjokes.co.uk

http://www.markjrees.co.uk

http://www.mjrcomputersolutions.co.uk

http://www.mjrfm.co.uk

 

[bcastner]

I understand.

 

[bcastner]

markjrees,

The Forum would benefit from any results, good or ill, that you obtain.

I know I would be very curious as to how this issue sorts for you.

Bill

 

[aquias]

I'll second Bill's thoughts there!

 

[DTracy]

Hey markjrees,

Just for the heck of it connect two of those computers back to back via the NIC's and see what happens.



Best Regards,
David Tracy

 

[markjrees]

our 4 computers arrived this afternoon. same problem - no network connectivity.

we uninstalled mcafee firewall software and still no joy. we then stopped the windows firewall and everything worked. we then re-enabled the windows firewall and we had network access fine.

we're going to the client tomorrow to do the same and finish off their network.

at last!

http://www.accountantjokes.co.uk

http://www.markjrees.co.uk

http://www.mjrcomputersolutions.co.uk

http://www.mjrfm.co.uk

 

[bcastner]

Great news.
And thanks for the feedback.
Bill

 

[bcastner]

An important issue was raised in this thread, and I wanted to make a comment.

The Service Pack 2 firewall is surprisingly adaptive. It waits until a listening port is attempted before it offers an exception. You can "add ports" or "add programs" to its formal Exception list, or just wait until a program attempts to open a port.

The above experience in this thread is quite interesting, as usually the SP2 version of the firewall is much quicker to figure out that File and Printer sharing is required. None the less, always check that an Exception in the firewall has been made for Netbios traffic by clicking the program exception for File and Printer sharing.

Moreover, be a little leery of firewall and antivirus programs if your machines come pre-installed with XP Service Pack 2. The software I have seen shows signs of not having completely "gotten it" about Service Pack 2. This will come, but as in this instance I would remove any third-party program, sort any other issues, and then reinstall with a fresh update from the Third-party firewall or AV company.

 

[AV1611]

I have run into this several times with XP and Service Pack 2.

Onece I have XP to XP sharing internet. I couldn't ping from A to B but I could ping from B to A. And yes I turned the firewall on and off. Still didn't work. After running network wizard until my fingers about fell off I got it to share the internet but still wouldn't ping. Yes, I enabled the ping option in the firewall and it still wouldn't ping.

Don't tell me they got the bugs out with this SP2. Its junk.

Also I had another XP that wouldn't let a 2k machine ping it. If I ran a continuous ping such as ping 192.168.1.1 -t it would fail until I rebooted the XP machine and right after the explorer started closing the 2k machine could hit it and right before I put in the username and hit enter it could find it.

XP SP2 has problems.

AV