How can I check to see if I'm able to connect to my networked PC?

[edprush]

I have a laptop with a US Robotics wireless card and I have a D-Link router that is connected to my PC via a LAN connection.

It appears that I can connect to the router from my laptop but I can't seem to connect to the PC.

Any suggestions on how I can check whether I am able to connect to my PC?

 

[JackMDS]

In order to conncet to your PC you need to Sahre the resources.

Successful Sharing involves some general consideration in Network settings, http://www.ezlan.net/sharing.html

As well as specific adjustment of each computer according to what is allowed to be shared.
http://support.microsoft.com/default.aspx?scid=kb;en-us;304040

 

[edprush]

Thanks for the reply.

Is there anyway to just ping the other computer to see if I'm connected to it? At this point I just want to see if I can even connect to it.

 

[JackMDS]

Download and run this, it would enable you to ping as well as showing you the sharing status.

http://www.softperfect.com/products/networkscanner (oh yeah, it is freeware).

:sun:

 

[edprush]

I gave the SoftPerfect Network Scanner a try and it found an IP that I didn't recognize. When I look at the properties of the IP (via SoftPerfect Network Scanner) I get a message that says the network location cannot be reached.

Any suggestions?

 

[ktwebb]

Start, run, cmd and hit enter. Ping the other machine. Unless I am missing something in your post. Either by name, or if that doesn't work, then by IP. You don't need software to find out what the IP is. The name is easy enough obviously. As well as the IP. run ipconfig /all from a prompt on that machine. Then start pinging. Hell, maybe I am just missing what the problem is. Wouldn't be the first time.

 

[edprush]

Wow. All I did was ping the other machine by name and the command prompt diplayed 0 packets lost! Then I tried to connect to the other machine and it worked!

Pinging the machine couldn't have caused that right? I wonder what happened.

 

[edprush]

After being able to finally ping my desktop yesterday I browsed the shared folders on the desktop then I shut down.

Today I booted the desktop then tried to ping it from the other machine and I received the command prompt message"Ping request could not find host desktop. Please check the name and try again."

I can't connect to the shared folders on the desktop either. Any idea what could be happening to cause this? I have not made any changes to either machine since being able to pnig and connect to shared folders on the desktop, yesterday. The only thing I did was shut the desktop down then restart it today.

 

[edprush]

I've been trying to ping the desktop for about 15 minutes and suddenly I get this from the command prompt:
---------------------------------------------
Pinging desktop [192.168.0.XXX with 32 bytes of

Request timed out.
Reply from 192.168.0.XXX: bytes=32 time=2ms TTL=1
Reply from 192.168.0.XXX: bytes=32 time=3ms TTL=1
Reply from 192.168.0.XXX: bytes=32 time=3ms TTL=1

Ping statistics for 192.168.0.XXX:
Packets: Sent = 4, Received = 3, Lost = 1 (25
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms
-------------------------------------------

It looks like there was a lost packet...so what does that mean? I have a poor connection? My router shows Excellent signal strength.

 

[ojai00]

That sounds like Wake-On-LAN to me. If you shut your desktop down, power it back on, can you access the Internet/network?

 

[edprush]

Originally posted by: ojai00
That sounds like Wake-On-LAN to me. If you shut your desktop down, power it back on, can you access the Internet/network?

When I turn the desktop back on I cannot access it via the Laptop.

 

[edprush]

Ok, I think I found a clue!

When I first boot the DESKTOP and look at the Properties of the Local Area Connection the Address Type says "Automatic Private Address." Then after about 20 minutes it changes to "Assigned by DHCP." At that time I am able to connect to the DESKTOP.

Does this show what my problem is and would anyone have an idea how to fix it so it stays at "Assigned by DHCP?"

thanks.

 

[ojai00]

What kind of NIC is in your desktop? You might want to check if there are updated drivers. Also, look in the BIOS for any signs of Wake-On-LAN

 

[edprush]

My Desktop NIC is a U.S.Robotics 10/100.

The drivers have been updated.

How could Wake-On-Lan cause the Address Type to be "Automatic Private Address" when I boot the Desktop but later it, somehow, resolves to "Assigned by DHCP"--at which point I am able to connect to the desktop via the network?

 

[ojai00]

Sorry, after looking on Google, it seems to be a problem with DHCP. Have you tried restarting your router or switching to another port on the router? You could also try a firmware upgrade on the router.

 

[edprush]

I have restarted and reset the router a number of times without any improvement.

I have the latest router firmware upgrade.

If a new router will fix the problem I'll go out and buy one but I'm not sure if the DHCP is router-related or Windows or something else...

Do you think a new router will fix my problem?

 

[ojai00]

You can either try to set a static IP address or hooking the desktop up to the modem directly to see if that helps. If your laptop is getting the IP address fine, it's probably not router related.

 

[edprush]

There is not a modem involved, yet.

I just have a laptop and a desktop connected to a router. By the way, when I first boot the desktop it CANNOT find the router either.

 

[edprush]

^