Printer Mapping on Different Networks

[John Schneider]

I'm running Windows 2003 Server on a new IBM T42 laptop. When in the office,
I'm connected to our corporate network. When at home, I plug it into my
router. One of the machines on the home network is Win XP Pro (no domain,
just the standard workgroup "MSHOME"), and it has a printer attached to it.
If I try to map to that printer from the laptop by using the path
\\MachineName\SharedPrinterName, I get an error that the network cannot be
found. However, if I use the IP address of the XP machine
(\\192.168.1.100\SharedPrinterName), the mapping works fine. The problem lies
with the router being recycled daily. The XP box may then end up with the
..100, .101 or even .102 address. Then, I have to delete the printer on the
laptop, and re-add it with the new IP address. The really frustrating point
with this is that the mapping, using the MachineName, worked fine with
Windows 2000 Server. I did not have to resort to using an IP address.

What is so different about Windows 2003 Server that the MachineName
technique will not work? There has to be a way to do this without resorting
to using IP addresses.

Thanks

[John Schneider]

Robert - Thanks for the reply!

I just double-checked, and NetBIOS over TCP/IP does appear to be set
correctly. Here's a screenshot:
http://pg.photos.yahoo.com/ph/ewebitjohnny/detail?.dir=/7e9d&.dnm=b5f3.jpg&.src=ph

I'm not sure how to setup LMHOSTS in this situation though. First of all,
in 2k3 Server, there is a file lmhosts.sam, rather than the plain old
lmhosts. Also, how would this work, given that the XP box could be one of 4
different addresses (192.168.1.100, 192.168.1.101, 192.168.1.102 or even
192.168.1.103)?

Again, I really do appreciate your response. I've posted this question in a
number of different forums, both Microsoft and non-MS related, but until now,
have yet to get a response.

John

"Robert L [MS-MVP]" wrote:

> this is name resolution issue. Have you enabled NetBIOS over TCP/IP? Alternatively, you can use lmhosts.
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "John Schneider" > wrote in message ...
> I'm running Windows 2003 Server on a new IBM T42 laptop. When in the office,
> I'm connected to our corporate network. When at home, I plug it into my
> router. One of the machines on the home network is Win XP Pro (no domain,
> just the standard workgroup "MSHOME"), and it has a printer attached to it.
> If I try to map to that printer from the laptop by using the path
> \\MachineName\SharedPrinterName, I get an error that the network cannot be
> found. However, if I use the IP address of the XP machine
> (\\192.168.1.100\SharedPrinterName), the mapping works fine. The problem lies
> with the router being recycled daily. The XP box may then end up with the
> .100, .101 or even .102 address. Then, I have to delete the printer on the
> laptop, and re-add it with the new IP address. The really frustrating point
> with this is that the mapping, using the MachineName, worked fine with
> Windows 2000 Server. I did not have to resort to using an IP address.
>
> What is so different about Windows 2003 Server that the MachineName
> technique will not work? There has to be a way to do this without resorting
> to using IP addresses.
>
> Thanks

[Robert L [MS-MVP]]

Sorry. The lmhosts doesn't since the IP is dynamic. Can you setup static IP?

If not, we need to figure it out. Do you enable NetBIOS on both computers? If yes, what do you receive if using net view \\hostname?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"John Schneider" > wrote in message ...
Robert - Thanks for the reply!

I just double-checked, and NetBIOS over TCP/IP does appear to be set
correctly. Here's a screenshot:
http://pg.photos.yahoo.com/ph/ewebitjohnny/detail?.dir=/7e9d&.dnm=b5f3.jpg&.src=ph

I'm not sure how to setup LMHOSTS in this situation though. First of all,
in 2k3 Server, there is a file lmhosts.sam, rather than the plain old
lmhosts. Also, how would this work, given that the XP box could be one of 4
different addresses (192.168.1.100, 192.168.1.101, 192.168.1.102 or even
192.168.1.103)?

Again, I really do appreciate your response. I've posted this question in a
number of different forums, both Microsoft and non-MS related, but until now,
have yet to get a response.

John

"Robert L [MS-MVP]" wrote:

> this is name resolution issue. Have you enabled NetBIOS over TCP/IP? Alternatively, you can use lmhosts.
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "John Schneider" > wrote in message ...
> I'm running Windows 2003 Server on a new IBM T42 laptop. When in the office,
> I'm connected to our corporate network. When at home, I plug it into my
> router. One of the machines on the home network is Win XP Pro (no domain,
> just the standard workgroup "MSHOME"), and it has a printer attached to it.
> If I try to map to that printer from the laptop by using the path
> \\MachineName\SharedPrinterName, I get an error that the network cannot be
> found. However, if I use the IP address of the XP machine
> (\\192.168.1.100\SharedPrinterName), the mapping works fine. The problem lies
> with the router being recycled daily. The XP box may then end up with the
> .100, .101 or even .102 address. Then, I have to delete the printer on the
> laptop, and re-add it with the new IP address. The really frustrating point
> with this is that the mapping, using the MachineName, worked fine with
> Windows 2000 Server. I did not have to resort to using an IP address.
>
> What is so different about Windows 2003 Server that the MachineName
> technique will not work? There has to be a way to do this without resorting
> to using IP addresses.
>
> Thanks

[John Schneider]

Static IP is not really an option.

I'm going to play with this some more over the weekend.

Thanks again for your responses!
John

"Robert L [MS-MVP]" wrote:

> Sorry. The lmhosts doesn't since the IP is dynamic. Can you setup static IP?
>
> If not, we need to figure it out. Do you enable NetBIOS on both computers? If yes, what do you receive if using net view \\hostname?
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "John Schneider" > wrote in message ...
> Robert - Thanks for the reply!
>
> I just double-checked, and NetBIOS over TCP/IP does appear to be set
> correctly. Here's a screenshot:
> http://pg.photos.yahoo.com/ph/ewebitjohnny/detail?.dir=/7e9d&.dnm=b5f3.jpg&.src=ph
>
> I'm not sure how to setup LMHOSTS in this situation though. First of all,
> in 2k3 Server, there is a file lmhosts.sam, rather than the plain old
> lmhosts. Also, how would this work, given that the XP box could be one of 4
> different addresses (192.168.1.100, 192.168.1.101, 192.168.1.102 or even
> 192.168.1.103)?
>
> Again, I really do appreciate your response. I've posted this question in a
> number of different forums, both Microsoft and non-MS related, but until now,
> have yet to get a response.
>
> John
>
> "Robert L [MS-MVP]" wrote:
>
> > this is name resolution issue. Have you enabled NetBIOS over TCP/IP? Alternatively, you can use lmhosts.
> >
> > Bob Lin, MS-MVP, MCSE & CNE
> > Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> > How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> > "John Schneider" > wrote in message ...
> > I'm running Windows 2003 Server on a new IBM T42 laptop. When in the office,
> > I'm connected to our corporate network. When at home, I plug it into my
> > router. One of the machines on the home network is Win XP Pro (no domain,
> > just the standard workgroup "MSHOME"), and it has a printer attached to it.
> > If I try to map to that printer from the laptop by using the path
> > \\MachineName\SharedPrinterName, I get an error that the network cannot be
> > found. However, if I use the IP address of the XP machine
> > (\\192.168.1.100\SharedPrinterName), the mapping works fine. The problem lies
> > with the router being recycled daily. The XP box may then end up with the
> > .100, .101 or even .102 address. Then, I have to delete the printer on the
> > laptop, and re-add it with the new IP address. The really frustrating point
> > with this is that the mapping, using the MachineName, worked fine with
> > Windows 2000 Server. I did not have to resort to using an IP address.
> >
> > What is so different about Windows 2003 Server that the MachineName
> > technique will not work? There has to be a way to do this without resorting
> > to using IP addresses.
> >
> > Thanks

[John Schneider]

Robert,

I've checked, and the NetBIOS setting is the same on both machines, per the
screenshot referenced below.

When I try the "net view \\hostname" command, I get the same error as when I
try to map a drive or printer:
System error 53 has occurred.
The network path was not found.
However, if I use the IP address (i.e. "net view \\192.168.1.102), I can see
the share name of the printer just fine. Do you have any idea what is so
different with Windows 2k3 Server vs Windows 2k Server?

Thanks again for your responses,
John

"Robert L [MS-MVP]" wrote:

> Sorry. The lmhosts doesn't since the IP is dynamic. Can you setup static IP?
>
> If not, we need to figure it out. Do you enable NetBIOS on both computers? If yes, what do you receive if using net view \\hostname?
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "John Schneider" > wrote in message ...
> Robert - Thanks for the reply!
>
> I just double-checked, and NetBIOS over TCP/IP does appear to be set
> correctly. Here's a screenshot:
> http://pg.photos.yahoo.com/ph/ewebitjohnny/detail?.dir=/7e9d&.dnm=b5f3.jpg&.src=ph
>
> I'm not sure how to setup LMHOSTS in this situation though. First of all,
> in 2k3 Server, there is a file lmhosts.sam, rather than the plain old
> lmhosts. Also, how would this work, given that the XP box could be one of 4
> different addresses (192.168.1.100, 192.168.1.101, 192.168.1.102 or even
> 192.168.1.103)?
>
> Again, I really do appreciate your response. I've posted this question in a
> number of different forums, both Microsoft and non-MS related, but until now,
> have yet to get a response.
>
> John
>
> "Robert L [MS-MVP]" wrote:
>
> > this is name resolution issue. Have you enabled NetBIOS over TCP/IP? Alternatively, you can use lmhosts.
> >
> > Bob Lin, MS-MVP, MCSE & CNE
> > Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> > How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> > "John Schneider" > wrote in message ...
> > I'm running Windows 2003 Server on a new IBM T42 laptop. When in the office,
> > I'm connected to our corporate network. When at home, I plug it into my
> > router. One of the machines on the home network is Win XP Pro (no domain,
> > just the standard workgroup "MSHOME"), and it has a printer attached to it.
> > If I try to map to that printer from the laptop by using the path
> > \\MachineName\SharedPrinterName, I get an error that the network cannot be
> > found. However, if I use the IP address of the XP machine
> > (\\192.168.1.100\SharedPrinterName), the mapping works fine. The problem lies
> > with the router being recycled daily. The XP box may then end up with the
> > .100, .101 or even .102 address. Then, I have to delete the printer on the
> > laptop, and re-add it with the new IP address. The really frustrating point
> > with this is that the mapping, using the MachineName, worked fine with
> > Windows 2000 Server. I did not have to resort to using an IP address.
> >
> > What is so different about Windows 2003 Server that the MachineName
> > technique will not work? There has to be a way to do this without resorting
> > to using IP addresses.
> >
> > Thanks