Windows XP forum: Problem Connecting to network computer

I have xp pro sp3. I mis-spoke about the number on the net, its actually 4 and there are usually only 2 on at a time. One machine is a linux machine and even that one can connect to the other 3. I only have trouble making connection on one machine and it can only not get into a single machine. That single machine can access all machines but the one that cannot access it (until I run the lan access program). Its truly bizarre.

Thanks for the reply - I will just keep fighting it.

So that's not it. If there is a connect by NAME then you have to figure out how name resolution is being handled in this LAN.

The clue is your scanning software. It could be forcing the name server to get up to date. Try to connect by IP next time or open a command line and use the NET VIEW command.

All this over WiFi can have us looking at the router. Your post added a little detail but not enough for me to narrow it down.
Bob

Thanks, again, for the reply!

I have a wired connection to the network, not wifi. Those with wireless connections are working just fine. The machine I am trying to connect to, however, is connected to the network by wireless and is accessable by every other machine on the network but this one. I should also mention that I also cannot ping the offending machine, until I run the LAN scanner. I am convinced that my problem resides with this machine as its the only one that cannot access the machine in question.

Here are the results of ipconfig /all:
Windows IP Configuration
Host Name . . . . . . . . . . . . : me
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection
Connection-specific DNS Suffix . .
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-19-D1-69-4D-99
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Thursday, January 31, 2013 10:34:08 AM
Lease Expires . . . . . . . . . . : Friday, February 01, 2013 10:34:0

Ethernet adapter Local Area Connection 8: (VPN)
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : TAP-Win32 Adapter V9 #2
Physical Address. . . . . . . . . : 00-FF-7C-E2-0C-19

It looks like the usual router. So a router rarely holds the names of the server. This means you have to be the IT GURU and know how the name is resolved or use the IP instead.

After all that I have to take your word that it does connect after the scan. In this reply you didn't write that but the story changed a little.

You also have account issues but I let that slide for now.
Bob

Thanks for the reply.

I understand the name/ip thing. Just thought I would tell you how it worked. The lan scan was done by advanced lan scan, I tried a couple of these and this one worked. I think it logs in although I had to be logged in to access other machines on the net. As I previously said, once the lan scan is completed everything works just dandy. Oh, but not forever. I suspect that the signal from the good machine is, somehow, not recognized until the scan sends a login of some sort. It remains a mystery.

I have what kind of account problem?

I wrote I let that slide since it works after the lan scan.

That lan scan could be triggering an update to the windows name cache.

I didn't want to ask why you didn't put this into the hosts file since it's likely your system is pure DHCP without address reservation. If you reserve addresses in the router which looks to be your DHCP server then you could fix it with an entry in the hosts file.

This is basic IT networking stuff so I don't detail what the hosts file does.
Bob

I thank you for the help. Its mysterious but I can live with it. I have been at this stuff for well over 40 years and am used to it (build, program, etc). When it tries to access the specific machine it can't even find the network. It doesn't tell me it can't find the machine it tells me that it can't find the network. On the other hand I can goto my linux machine and IT finds it! The other thing is that this system never used to have a problem so I have obviously done something clever.

Oh, well - thanks again for the help. during all of this I did find some kinda neat and keen programs. One I liked was internet repair. Simply and straight forward. I figure I would play with that one over the week end. I have no problems with my internet but, sometimes, simply cannot resist <g>

Windows networking and name resolution is something that's been around since WFWG 3.1. The way the names are resolved to addresses hasn't changed much, if it at all. The clue is your lan scan.

It does not matter how it works but you could hurry it along with a few changes. Address reservation on the DHCP server then an entry in the hosts file.

Sorry but I didn't give a history on all this but you did give some but not all the details. I noted to try by address but am not finding where you did that.
Bob