Connection there but Lost 1

[ArsePit]

As far as I know, the problems began yesterday (I had the previous day off). I know a temp Mech.Engineer was on the workstation(which was moved to a makeshift office temporarily) for about a week and he prob messed around because the computer was set for a Head Engineer with admin properties.

Problem 1: A WIN2000PRO Workstation has 'lost' its connection to the ISP(DSL Modem|Gateway) through our LAN. I have tried uninstalling and reinstalling TCP/IP and switching IPs. I have checked the DNS entries and they are correct.

Problem 2: Another weird thing, on the LAN it can 'see' several workstations in its Workgroup and several in another Workgroup but when you try to gain access to any of them it responds with an error of

"//comp_name is not accessible
The network path was not found."​

The ONLY connection it can make is one to the WIN2000SERVER(Workgroup right now, no Domain setup or DHCP) in its workgroup which it makes after the user logs in.

To recap, I can ping the hell out of the W2K Server but can't get through to the gateway(DSL Modem 192.168.0.1) or any other IP address. I can see several computers in two workgroups on of which the computer is a part of.
I am pretty sure that both problems stem were caused by one error.
There is a fire lit under me by the Head Engineer to get it fixed. Please respond with any comment/help ... it is greatly appreciated.

8]
Jerm

 

[StarTAC]

check that you have TCP/IP protocols properly installed and configured... then, u might want to test the Ethernet cable that goes to your hub/switch... if that's ok, ensure there's no IP conflict on the network.. ensure IP and netmasks conform to your network

after this, u may need to give the DSL modem a reboot.. just to clear any ARPs it might have had... try this and see whether it works....

good luck...

 

[ArsePit]

!!!SOLVED!!!I didn't think this was affecting it but I told the user to change it.

Under the configuration of the ethernet adapter there are settings for 802.1p Support(disabled on my comp), it was enabled on his computer. He disabled it to see what would happen. It asked to reboot ... in Win2000Pro when it asks you to reboot you know it is doing something important with the hardware! Well, it worked. PLEASE see "

http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q222020

" for further information. I do not understand why it worked yet but I soon will. Maybe you have to have it in all your hardware across the network or else it won't see that hardware. I do not know why the temp(problem causer) would enable it just to simply talk to the Server.

 

[Maruis]

Well done!!!
Just a tip if I may?
Never ever give admin rights to a temp worker or a brand new employee, not even local admin rights!!!!!

They always tend to play around and too often they do not know what they are doing.

To save yourself a lot of headaches restrict admin rights to as little people as possible.

Hope this helps.