Network Browsing
#4
Scooby Regular
Join Date: Feb 2006
Location: Bring back infractions!
Posts: 4,554
Likes: 0
Received 0 Likes
on
0 Posts
The built in Windows XP/Vista/Win7 Firewall has a habit of turning itself on unless you tell the PC otherwise. This would most likely stop ping and browse requests.
#5
Scooby Senior
Join Date: Feb 2000
Location: West Midlands
Posts: 5,763
Likes: 0
Received 0 Likes
on
0 Posts
You haven't really given us any information to work from, but in simple terms...
When a computer boots up, it broadcasts certain details (name, address, workgroup etc.) to the local subnet (computers that can "see" each other without going through a router).
Computers on that subnet may (or may not) collect that information in a list so that they know what is out there (on the subnet)
Some computers may collect that information and share it with other computers outside of the subnet (e.g. via Active Directory).
This is how your "net view" obtains basic details of the PC that you want to look at.
When you "ping" a computer, a special network packet gets sent to what should be the network card of the destination machine (which may or may not be on the same subnet).
On arrival, (traditionally) a friendly operating system will reply to that "ping" to confirm that it is there - but it does not have to. For example, why should you confirm to a Chinese script-kiddie that you computer is available on the Interweb?
This is why (by default) XP etc. enable a "firewall" which defined rules as to what kind of packets and what source addresses are allowed.
Thus, as Coffin Dodger says, you need to specifically disable the firewall to let stuff through - something that your "wouldn't have a clue" probably hasn't done.
Now "pings" are simple and part of the Interweb standards. Browsing (assuming you mean trying to access files on a Windows machine and not connect to a web-site via HTTP) is much more complicated and somewhat specific to Microsoft.
Thus you need to know whether the destination PC has file sharing enabled etc. (as well as if it has a firewall).
Or in layman's terms - when you walk down the high street you can see the banks but it doesn't mean that they will let you in (never mind enter the vault)
mb
When a computer boots up, it broadcasts certain details (name, address, workgroup etc.) to the local subnet (computers that can "see" each other without going through a router).
Computers on that subnet may (or may not) collect that information in a list so that they know what is out there (on the subnet)
Some computers may collect that information and share it with other computers outside of the subnet (e.g. via Active Directory).
This is how your "net view" obtains basic details of the PC that you want to look at.
When you "ping" a computer, a special network packet gets sent to what should be the network card of the destination machine (which may or may not be on the same subnet).
On arrival, (traditionally) a friendly operating system will reply to that "ping" to confirm that it is there - but it does not have to. For example, why should you confirm to a Chinese script-kiddie that you computer is available on the Interweb?
This is why (by default) XP etc. enable a "firewall" which defined rules as to what kind of packets and what source addresses are allowed.
Thus, as Coffin Dodger says, you need to specifically disable the firewall to let stuff through - something that your "wouldn't have a clue" probably hasn't done.
Now "pings" are simple and part of the Interweb standards. Browsing (assuming you mean trying to access files on a Windows machine and not connect to a web-site via HTTP) is much more complicated and somewhat specific to Microsoft.
Thus you need to know whether the destination PC has file sharing enabled etc. (as well as if it has a firewall).
Or in layman's terms - when you walk down the high street you can see the banks but it doesn't mean that they will let you in (never mind enter the vault)
mb
Trending Topics
#9
Scooby Regular
Join Date: Aug 2003
Location: Epsom
Posts: 5,832
Likes: 0
Received 0 Likes
on
0 Posts
yep, sounds like windows firewall is on for that machine. Do you not have a group policy for the office that sets this? If so, the policy hasnt applied and you have bigger problems!. If not, as an administrator, go to control panel, windows firewall, advanced, icmp settings button, and tick the first entry, allow incoming echo request. Ok out of it all and it will ping. (You have got the correct ip address for that machine haven't you?!)
As for the admin share, you are an administrator on that machine aren't you....?
As for the admin share, you are an administrator on that machine aren't you....?
Thread
Thread Starter
Forum
Replies
Last Post
IWatkins
ScoobyNet General
1
24 October 2000 10:46 AM
Aaron Payne
ScoobyNet General
1
18 January 2000 02:16 PM