Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.
Can not access server
Name: Chris (by Chris Kirk) Date: May 11, 2008 at 12:58:01 Pacific OS: Xp pro & Server 03 CPU/Ram: - Product: -
Comment:
Hi, i can not see any reason for it but now no computer can access the server and the server can not acees any of the computers, this includes both domain clients and computers not on the domain. All the computers can acess other pc fine but not the server, and the server (win Server 2003) can not access any pcs. Same problem if i try typing in the server name, it just say it can not be found, check spelling ete. Domain user can not log in. Any help Thanks
Name: guapo Date: May 11, 2008 at 13:05:19 Pacific
Reply:
Open a command prompt on the server and run netstat -an
Is it getting an IP address? It can't be that 169.254.x.x that MS gives to NICs when something is wrong. It has to be an IP on the same subnet as the rest of the network.
0
Response Number 2
Name: Chris (by Chris Kirk) Date: May 11, 2008 at 13:33:32 Pacific
Reply:
it sas active connection and a long list, what part of it am i looking at.
0
Response Number 3
Name: guapo Date: May 11, 2008 at 13:37:05 Pacific
Reply:
Look in the local address column for an IP address that's on the same subnet as the rest of your network. Examples: 192.168.x.x 10.x.x.x 172.x.x.x.
If you don't understand the output run: ipconfig instead.
0
Response Number 4
Name: Chris (by Chris Kirk) Date: May 12, 2008 at 08:54:07 Pacific
Reply:
I ran ipconfig instead and got
Connection-specific DNS Suffix . IP Address. 192.168.x.x Subnet Mask . 255.255.xxx.x Default Gateway .
That is nothing for DNS suffix and nothing for Defult Gateway. The Subnet Mask is the same as on the clients. Any help from this please Thanks.
0
Response Number 5
Name: guapo Date: May 13, 2008 at 06:38:34 Pacific
Reply:
First of all, you didn't have to hide the last octets on the IP addresses. They are internal IPs and can't be accessed from the outside.
If the IP is 192.168.0.100 then the default gateway is the IP address of the router which would most likely be 192.168.0.1
If that's the case, then you should be able to ping the from the server. You should also be able to open the web interface of the router in the browser. http://192.168.0.1
Also run netstat -r
and check the output. The default gateway should be listed there. You can also try a static IP address.
0
Response Number 6
Name: Chris (by Chris Kirk) Date: May 13, 2008 at 08:45:18 Pacific
Reply:
Thanks that has helped and now it works again.
0
Response Number 7
Name: guapo Date: May 13, 2008 at 16:10:43 Pacific
Summary: Hi All. This is the issue i'm having with W7 as a server... - connection to internet is fine for all clients - pinging outside world also works great - sharing is fine - i can not ping server by it's ...
Summary: I have some trouble in my network setup, but I have very limited knowledge of networking. I recently purchased an ADSL modem, which also has a built-in router, DHCP and other stuff (as I discovered la...
Summary: After setting up a netgear router for my desktop ( XP) and a wireless card to my notebook (ME), I was able to get internet connection on both. I set up my LAN with the wizard on the desktop, and tried...
0 
Password needed to connec...
