Search results for query: *

Fixed! Turned out one of our users had an insecure password and someone hacked in and dropped a backdoor trojan on the server. We will be buying a firewall for the server today to prevent this again and making sure everyone has a secure password.

There is some new developments here. It's looking like there is a serious problem with DNS on the server. I dropped a spare hard drive in one of the office machines and proceeded to do a fresh windows 2000 install. I now get the same error when trying to join the domain with the windows 2000...

I've got it resolving the domain server by name now but it's still not letting new machines onto the network. It's as if the domain controll has prevented new computers from being added or from existing users from browsing the network to the server.

Another strange thing happening on the network the last few days: I cannot browse to the server even on computers that are hooked to the domain. It's as if the server isn't broadcasting the domain exists or is rejecting any requests that the domain does exist. Obviously there is connectivity...

Host name: FieldLTTP Primary DNS Suffix: (Blank) Node Type: Unknown IP Routing Enabled: No WINS Proxy Enabled: No Ethernet NIC: Physical Address: (ect ect ect) DCHP Enabled: Yes Autoconfiguration Enabled: Yes IP Address: 192.168.0.27 Subnet Mask: 255.255.255.0 Default Gateway: 192.168.0.1 DHCP...

Okay we have the following: DHCP Enabled Auconfiguration Enabled IP Address 192.168.0.1 Subnet 255.255.255.0 Default gateway 192.168.0.1 DHCP Server 192.168.0.1 DNS Servers 192.168.0.1 Connection specific DNS Suffix above is blank. Still driving me nuts.

Hmm I tried both pinging by name methods again this morning and neither is working. The 2000 Box I'm on is set to use the NetBios setting from the DHCP server. Currently the windows XP Pro boxes are set to do the same. The problem is definitely not a license problem as we are only at 11...

My understanding was licenses was only for concurrent connections to the server and not actual computers connected. I may be wrong on this and if I can purchase another block of licenses to make this go away I certainly will. However I hate to spend money if I'm not sure it will fix the problem.

No Firewalls at all. In fact it's a fresh install of XP professional with no patches. I've tried patching it to SP2 with all security updates to no avail.

That's what happens when you are sick of a problem and are typing too fast to really pay attention. Pinging by IP works absolutely fine, however pinging by name does not. I set up WINS this morning but I did not reboot the server. I do have NetBIOS enabled over TCP/IP I just experienced the...

BTW I am trying to add windows XP Pro machines to the network. It seems like windows 2000 machines add just fine.

I've been having fits the past couple days adding some machines to our office windows 2000 server domain. Every time I try to join the domain I get the following error: The following error occurred attempting to join the domain "domain name". The network name cannot be found. It's driving me...