Sean/Gene, When adding the printer to the RH machine that was connected to an XP machine I found that RH discovered the printer through a probing mechanism when adding a networked Samba printer. This is what threw me. The Share name was based on the IP address/domain name (plus the printer name) of the XP machine.
Fortunately, I have a dual boot system on my machine. My RH system coexists with a copy of XP in a separate partition. While deceived by RH detecting the printer on the networked XP machine, using the IP address/domain name, I found that the copy of XP residing on my machine showed that the NetBIOS name of the computer, where the printer resided, was not what RH had detected. Once I changed the Share name of the networked machine in my RH printer setup to the Share name used in my XP setup I was able to print SUCCESSFULLY !! What tricked me was RH detecting the networked printer based on the IP address (of the remote XP machine) I had used in the printer setup on my RH machine. Once I changed it to the NetBIOS name used in Windows it worked perfectly. Thank you both for your suggestions and help!!! Now, if I could just figure out why I cannot successfully download a kernel up2date download :) Bob / wa2mno -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gene Poole Sent: Monday, August 11, 2003 10:20 AM To: [EMAIL PROTECTED] Subject: Re: Printing to an XP printer Sean, I too print from a Red Hat Linux box to a Windows box (Red Hat is 8.0 and Windows is 98SE, but shouldn't matter). One thing, if the alias for the machine in /etc/hosts of the Linux box and the netbios name of the Windows machine are the same, it makes life easier. Be sure that you have created a 'Share' for the printer on the Windows box. Remember the name of the share. The command looks like: smbclient //alias name (or netbios name)/share name When you get the smb prompt, enter: print your-file-name When complete, enter: quit Thanks, Gene Poole [EMAIL PROTECTED] On Sun, 10 Aug 2003 20:20:13 -0500 "Bob" <[EMAIL PROTECTED]> wrote: > Sean, > > I don't think this is a firewall issue because I was able to get a response > when issuing: > smbclient //XP_computer_IPaddress/print > > The response from the XP machine was: > > Domain=[LAN] os=[Windows 5.1] Server=[Windows 2000 LAN Manager] > tree connect failed:NT_STATUS_BAD_NETWORK_NAME > > This sounds like an XP issue, doesn't it? > > Bob > Hi Bob, Ok, There is a dependence on ip name resolution that is being reported here. You need to make an entry in your /etc/hosts file for the IP address of your XP machine. Also you need to match the name you give to this IP to be the same name as the computer name you've assigned within Windows XP. I seem to recall that the SMB protocol does imbed the machine name in each request itself so getting the packet to the server isn't enough. It must also arrive with the correct machine name. After you update your /etc/hosts file it should work for you. There is a command line option of smbclient that accomplishes the same thing but the best way to do it is to update your hosts file. Good Luck, Sean -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
