one pc can’t access via windows server 2003 network




 in network all pcs are connected together, but one pc not show that shred data. all are in the domain.
Dear Jay Nelish


Your Question is incomplete


is the specific system is not on Network? its might be a problem discovered last year, that system ping but not share any data, or cannot access the system


you click on start menu and then click on run  

type serivces.msc  

and run the computer browser service, Remote Procedure call service, Server, and Client service


and your problem will resolved  

but actually this is because of virus change your antivirus program and scan your system wtih updated A/V
that is where i'd start as well. osi...
so:
1. physical link (maybe check the patch panel and the cabling that's involved in connecting to the computer, maybe swap cables and try a usb to ethernet adapter to rules the nic out.
2. data link - check the switches and switchports on the way. maybe try to use different portts
3. network - most likely not an issue if all the other computers are working fine...
etc.
but this is pretty much it: Windows 7 is the operating system for your computer and it must have one to function. You have to install another operating like Windows XP or Vista and then you will be able to use the net. If you have not done this before, you should propably find someone who has to help you. Your card is ok. There is interference between the router and your computer.  

  

1. The router or the PC may be "hidden" behind a metal cabinet, refrigerator, etc.  

2. Move router higher  

3. Microwave ovens and some cordless phones (not cellphones) that use 2.4GHz will interfere with the 2.4GHz WiFi signal.  

4. Point the router antennas in-line with the direction of the PC.  

5. Move the router closer to the PC. The question is can you get out of your computer and after that the thing to check is can you resolve any domain names. Try going to a command prompt and checking to see if you can ping your computers IP address then the gateway then try to resolve domain names.


ipconfig /all


Will give you the information you need to check these things.


nslookup google.com


If that does not come back with a IP address then you have problems with your DNS server. Try to xcopy the data over to the external drive.



start>run>type "cmd">hit ok  

In dos window type "xcopy /?" this will show you all of the parameters or switchs used in xcopy.



If you are not famaliar with dos you may want to seek out a friend who is. i assume your new router is wireless?

limited access with wireless usually means you don't have a valid ip address assigned. you need two things for a working internet connection. 1. you need a physical connection, known as layer 1 and layer 2. 2. you need a logical connection known as layer 3.

if you've got the limited access message that means your laptop has a working wireless connection at layers 1 and 2. what you don't have is the layer 3 connection i.e. an ip address.

there could be a number of reasons why this is happening. i would suggest that you start by powering your pc down - shut it off completely not just hibernate it or just shut the lid. next power down the router, pull the power cord out of it. let the router sit unplugged for about 2 minutes. power the router back up......wait about 2 min more. power your pc back up.

learn how to use the command line command "ipconfig". you access the command line via the accessories folder on windows. when you get the c:/> prompt - enter the command "ipconfig" hit enter. in the group of stuff on the screen you want to see an ip addess assigned to the wireless interface. when you get the limited access message the first thing you want to do is check to see if you have an ip address assigned.

if the above trick doesn't work, then i suspect there is something wrong with your network configuration on your pc. if you take your laptop to a starbucks does it work there? try that drive with another computer. if it doesn't work, it's probably dead. simple answer. no two nodes ever store the same data. instead storj uses erasure coding for which each piece is unique. so piece id’s are unique across the network.

maybe if a piece is lost and then subsequently rebuilt in a repair action it ends up having the same name on the new node. it would de… in this case you can try simply rebooting your home router, if not at home please contact your network administrator.

failing this try using alternative dns -

[image]

[how to enable faster dns resolution on windows 10](https://www.000webhost.com/forum/t/how-to-enable-faster-dns-resolution-on-windows-10/118671) [tutorials](/forum/c/tutorials)

this is a windows based tutorial so if you r… just a heads up. i believe we found the solution. as far as we could tell, these issues began to happen after we moved everything to windows 7. however, one of the helpdesk people said they thought they remembered it happening once before that while the computers were still all xp. 
i looked into the av, which was moved to a different server and upgraded shortly before our windows 7 project began. evidently, trend's migration tool that was used did not migrate over port exceptions in the firewall. after adding a few recommended exceptions to the firewall, everything started to work. 
it seems that the client firewall was blocking return snmp traffic from the printer which was keeping the computer from realizing that printing had completed. this was keeping the connection open to the printer preventing anything else from printing on that computer or any others connected to it. 
the ports added as exceptions were: udp 161(probably the only one needed), tcp 9100, 9220, 9500.