[rudy45]

thanks so much everyone. I fixed it. Here's what I had to do:

- add to the hosts file a line for each "local" ip address and associated host name
- add [workgroup name].NET as a domain name suffix

All these problems arose because of a switch in routers, from DLink 614+ to a Belkin Wireless G (because the latter supports 802.11g and WPA, and the former supports only WEP). Remote printing was working fine under the DLink, then stopped once I replaced it with the Belkin.

I thought the problems would disappear if I re-installed the DLink, but the problems remained. What's puzzling is that I didn't have to do all this stuff when I first put in the DLink. Is it possible that switching the router (which uses a different local address scheme, 192.168.2.1 instead of 192.168.0.1) could have clobbered the DNS suffix and hosts file (which maybe Windows DID put in automatically the first time I set up the network?)?

One final question: does an Apple MacBook have an counterpart for the hosts file. Also, will I have to tell it the domain name suffix? If so, where and how?

Thanks.

[freedumb2003]

I didn't want to admit it, but I had the very same problem.

I didn't have time to mess with it so I just transfer files to the main computer and print from there.

Thanks for getting back to us.

[HAL9000]

One final question: does an Apple MacBook have an counterpart for the hosts file. Also, will I have to tell it the domain name suffix? If so, where and how?

Mac OS X has that file at - /etc/hosts

You could add entries like -

DELL_COMPUTER 192.168.0.102

and

DELL_COMPUTER.mysuffix 192.168.0.102

- with a tab between the host name and the IP address.

I generally use the "vi" tool in terminal for editing files like 'host', but you may prefer to use a free editor like Text Wrangler instead.