mikeabc27
asked on
XP PC cannot connect to SBS 2003 server
Hi.
Just got a call from someone working late who found after a telephone switchboard problem they cannot connect to their sbs2k3 server. It can't be pinged and the xp box isn't seen by the server.
Only one other computer on that network turned on and that's ok. So I'm remotely connected to the server and the two pcs.
The problem one shows a system event error of 1054 saying the server doesn't have details of the computer.
Any quick fixes other than disconnecting from and rejoining the network?
Thanks for any ideas.
Just got a call from someone working late who found after a telephone switchboard problem they cannot connect to their sbs2k3 server. It can't be pinged and the xp box isn't seen by the server.
Only one other computer on that network turned on and that's ok. So I'm remotely connected to the server and the two pcs.
The problem one shows a system event error of 1054 saying the server doesn't have details of the computer.
Any quick fixes other than disconnecting from and rejoining the network?
Thanks for any ideas.
You could try resetting the computer account in AD...If that don't fix it I'd recomend leaving the domain, delete the computer from AD then reboot the work station & join it again....don't forget to place the computer account back into the correct OU.
If the XP Box can't Ping the Server and Vice Versa, then the issue is Hardware, Firewall, or Viral.
Typically I haven't run across any Server 2003 firewall issues, which would lead me to look at a physical hardware connection problem, or possibly a Nic Driver issue (not likely, but good to keep in mind).
Unfortunately, it may fall into the nasty category of Viral. I know there are several out there that will disrupt internet connectivity, however I don't think I've run across one that interferes with Ping responses, but I could be wrong.
I would check, or have the user check, the physical connections, then check for viruses, just to make sure.
Typically I haven't run across any Server 2003 firewall issues, which would lead me to look at a physical hardware connection problem, or possibly a Nic Driver issue (not likely, but good to keep in mind).
Unfortunately, it may fall into the nasty category of Viral. I know there are several out there that will disrupt internet connectivity, however I don't think I've run across one that interferes with Ping responses, but I could be wrong.
I would check, or have the user check, the physical connections, then check for viruses, just to make sure.
ASKER
The DNS for the NIC is the SBS server so the PC cannot connect the Internet. From a hardware aspect the XP connects to the server and firewall (Netgear FVS318) via a switch and can ping the firewall but not the server.
All antivirus up to date, Symantec Endpoint and Malwarebytes Pro, so feel it's the computer account? Any quicker ways than leaving and rejoining?
All antivirus up to date, Symantec Endpoint and Malwarebytes Pro, so feel it's the computer account? Any quicker ways than leaving and rejoining?
I would clear the DNS cache on the client ( ipconfig.exe /flushdns ). Try pinging the server by IP instead of hostname (if that hasn't been done already). Make sure the cables in the closet where the server/switch may be located near the telephone equipment are all plugged in securely.
ASKER
Tried the flushdns - no luck. Already tried by IP and don't feel it's hardware as I am connected remotely and if I add the firewall as a DNS server on the PC it connects to the Internet.
I suppose it's a matter of removing and rejoining the network.
I suppose it's a matter of removing and rejoining the network.
Correct. If resetting the computer account in AD don't fix it, leaving the domain then rejoining it is the only fix I know of.
ASKER
What's the best way to do a reset in SBS 2003?
I cannot understand why I cannot ping server. If I cannot ping server by IP, surely I won't be able to join the network.
The office won't open for a couple of hours, but the two computer on at the moment are connected as follows:
Computers A and B are both connected to a switch which connects to an ADSL firewall/router (2wire - sorry I said this was a Netgear before) and the server.
Computer A can connect to server and Internet.
Computer B cannot connect to either, but can ping router, but not the server. If I add the router IP as a DNS server on computer B it can access the Internet.
Maybe virus, I'll do a scan now and talk someone through a combofix when they get in.
I cannot understand why I cannot ping server. If I cannot ping server by IP, surely I won't be able to join the network.
The office won't open for a couple of hours, but the two computer on at the moment are connected as follows:
Computers A and B are both connected to a switch which connects to an ADSL firewall/router (2wire - sorry I said this was a Netgear before) and the server.
Computer A can connect to server and Internet.
Computer B cannot connect to either, but can ping router, but not the server. If I add the router IP as a DNS server on computer B it can access the Internet.
Maybe virus, I'll do a scan now and talk someone through a combofix when they get in.
ASKER
mbam pro and SEP didn't find anything
ASKER
or combofix
ASKER
I'm onsite now - four XP workstations can connect to the server, four can't and cannot ping the server, so no point in trying to reconnect them to the server.
I've ran mbam pro, SEP and combofix on one problem PC and reports clean.
All PCs can ping the router/firewall.
Any ideas?
I've ran mbam pro, SEP and combofix on one problem PC and reports clean.
All PCs can ping the router/firewall.
Any ideas?
Have you rebooted the 4 offending PC's.On one of those XP PCs, check arp after trying to ping. (Arp -a). Does the server ip resolve to a MAC address? Perhaps there are static arp entries in those PCs interfering with normal arp (if so remove them). Compare arp entry with one from a working XP system. Do all the machines have the same IP mask? Where do the machines get their IPs from (server dhcp, or firewall dhcp, or static)?
ASKER
All PCs were rebooted several times and have following STATIC IP setup:
IP address: 192.168.1.x
Subnet mask: 255.255.255.0
Default g/w: 192.168.1.254 (2wire router)
DNS servers: 192.168.1.100 (sbs 2003 server) and 192.168.1.254
ARP -A results:
Good pc
Interface 192.168.1.119 -- 0x2
192.168.1.100 mac address dynamic
192.168.1.254 mac address dynamic
Problem PC
Interface 192.168.1.119 -- 0x2
192.168.1.254 mac address dynamic
Ipconfig /all on the server displays mac address.
IP address: 192.168.1.x
Subnet mask: 255.255.255.0
Default g/w: 192.168.1.254 (2wire router)
DNS servers: 192.168.1.100 (sbs 2003 server) and 192.168.1.254
ARP -A results:
Good pc
Interface 192.168.1.119 -- 0x2
192.168.1.100 mac address dynamic
192.168.1.254 mac address dynamic
Problem PC
Interface 192.168.1.119 -- 0x2
192.168.1.254 mac address dynamic
Ipconfig /all on the server displays mac address.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
you could download and run wireshark to do a packet capture and see if arp packets are going out and being received on the NIC of the XP PC. If not seeing arp responses being sent when you try to ping the server, then it is either the switch or the server blocking communications.
ASKER
Restarted the switches and hey presto!!