Computer can't connect by name

[sswingle]

I have a notebook that absolutely refuses to connect by using //computername It connects just fine if I put in say, //192.168.0.102

This hasn't been a problem in the past, but I got a Linksys USB print server, which is on the network as //printserver and this notebook refuses to connect. I tried changing it to an IP address in properties for the printer, but it still reports being unable to connect.


Also of interest, this is on a wireless card. I plugged it in to a wire, and eventually (after several reboots and lots of trying various things) got it to work. Now a couple days later, try to use the printer, and it won't connect.

It prints fine if I share the printer on a computer and direct the notebook to the printer at 192.168.0.102, but the whole reason I got the server is so people can print if this computer is turned off.

Any ideas?

Oh, this is an XP Pro box, just like everything else here except one XP Home machine. Everything else works great...except for my Linux box, but that is another story in itself.

 

[us3rnotfound]

w/e you do, DO NOT run the flaky network connection "wizard" :roll:

 

[sswingle]

Wow, that was a big help. Anyone else?

 

[sswingle]

Figured it out. I went into network properties to turn on NetBEUI. I noticed that firewall was turned on for wireless but not for wired. I turned off the firewall, and everything works great.

 

[LoudTIGER]

what does the firewall have to do w/ this?
just curious, my dad has this issue sometimes on his laptop too

 

[sswingle]

I don't know what the firewall has to do with it, but everything started working fine as soon as I turned it off.

Norton firewall used to give me problems too, until I added the private network range as trusted. Windows firewall isn't configurable that I know of, so the only solution is to turn it off.

 

[LoudTIGER]

hm, i tried turning off the firewal but it was still the same. 192.168.1.. whatever will bring me to the computer, but the \\computername wont. i dont know what's wrong. btw, it works fine on wired ethernet