Solved

Multihomed Windows 2003 server needs clients to print from one lan to the other

Posted on 2008-10-21
9
204 Views
Last Modified: 2012-05-05
I have a multihomed Windows 2003 server that has 2 nics that are on a 172.20.9.x and a 192.168.2.x network and shares printers on both networks.  The clients that are on the 172. LAN need to be able to print to the 192. printers shared on the windows 2003 server and vice versa.

Scenario: When I connect a 192. printer from the Win2003 server on a client on the 172. network it installs the IP port for the opposite network.  

Question: Is it possible to print to the server and have the server push the print job from one network to the other?  or is there another way to do it using windows 2003 server?

0
Comment
Question by:poohberry
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
9 Comments
 
LVL 38

Expert Comment

by:ChiefIT
ID: 22773195
Files and printer sharing is all a part of the SMB shares. You will need a WINS connection between the shares in order to do this.
0
 
LVL 38

Expert Comment

by:ChiefIT
ID: 22773226
OOPS:
"You will need a WINS connection between the shares in order to do this."

That should have said:

You need a WINS connection between the two domain master browsers to do this. This should be the PDCe by default.
0
 

Author Comment

by:poohberry
ID: 22782308
I have WINS, DNS and Reverse DNS setup.  I can see the printers on the server from either side but I cannot print to them.  If I browse to the server locate the printer click connect it will install the printer but the printer is installed with PORT IP_192.168.2.126 and that works great from machines with a 192.168.2.x address.  If a printer is installed on a computer on the 172.20.9.x network I can locate the printer share, click connect and it will install the printer but the printer is installed with PORT IP_192.168.2.126.  

I assume I would need to be able to print to the server and the server push the print job to the other network.  But I do not know how to do that or if its possible...
0
Space-Age Communications Transitions to DevOps

ViaSat, a global provider of satellite and wireless communications, securely connects businesses, governments, and organizations to the Internet. Learn how ViaSat’s Network Solutions Engineer, drove the transition from a traditional network support to a DevOps-centric model.

 

Author Comment

by:poohberry
ID: 22782319
EDIT ABOVE: I have WINS, DNS and Reverse DNS setup.  I can see the printers on the server from either side but I cannot print to them if the computer is on the other network. If I browse to the server locate the printer click connect it will install the printer but the printer is installed with PORT IP_192.168.2.126 and that works great from machines with a 192.168.2.x address.  If a printer is installed on a computer on the 172.20.9.x network I can locate the printer share, click connect and it will install the printer but the printer is installed with PORT IP_192.168.2.126.  

I assume I would need to be able to print to the server and the server push the print job to the other network.  But I do not know how to do that or if its possible...
0
 
LVL 38

Expert Comment

by:ChiefIT
ID: 22782407
What you are asking is highly possible: I have printed on remote sites plenty of times.

There are three things to look at when printing:

1) Trust relationship.
Are your sites trusted to print on eachother's sites.
2) SMB blockage:
SMB is on port 445. Some ISPs block SMB traffic because of the vulnerabilities in the SMB shares. Direct access to those could cause IT security woes. So, this of course depends upon your connection to the remote site. Is it a point to point site connection that bypasses interaction with a ISP, or is this a VPN connection that might be blocked on the SMB share port of 445.

You can test this by going to the command prompt and typing:
Portquery -n xxx.xxx.xxx.xxx -o 139, 445 -p both

4) Some printers are having problems printing from remote sites because they have bidirectional support enabled and SNMP enabled. In this case printing may get stuck on the server's queues of the 2003 server. You might consider disabling bidirectional support and SNMP for these printers for both sites.
0
 

Author Comment

by:poohberry
ID: 22789166
I only have one server with one Domain and the server is multihomed to both networks.
0
 
LVL 38

Accepted Solution

by:
ChiefIT earned 500 total points
ID: 22810554
What's has worked for me in the past is to create a WINS connection between the remote computers and the PDCe.

Why does this work, you might ask?

A while ago printers and shares were really netbios shares. They were shared out using netbios broadcasts to all the clients. A netbios broadcast was sent to the domain master and would elect the domain master to be the domain master browser. The browser service allowed for connections to file and print shares. These netbios broacasts were not routeable, so WINS was used to allow access to these shares from a remote location. If the remote site had a DC, The two "primary domain controllers" of the two sites could use a WINS connection between them to share the browselist and traffic netbios data between the sites.

Then, Microsoft came up with DNS. However certain services, like the browser service remained with the Netbios protocol to share out some shares. So with DNS came another issue, how do you share out files and use the browser service. This is where SMB traffic came into play. SMB uses ports 139 and 445 to share SMB traffic. SMB traffic is able to go across remote sites. The issue with SMB traffic is this. It BINDS to one network binding. So, if your LAN binding is working for SMB shares, your remote sites will not.

What I found out about SMB shares is this. Your SMB shares can work internally, But while SMB sends out a SMB discovery it also sends out a WINS discovery too. When one of them replies, this is when you get the connection between the two machines. In other words, you can use SMB for the LAN computers, and WINS connection for your WAN computers.
0

Featured Post

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Numerous times I have been asked this questions that what is it that makes my machine log on so slow, there have been cases where computers took 23 minute exactly after taking password and getting to the desktop. Interesting thing was the fact th…
I've always wanted to allow a user to have a printer no matter where they login. The steps below will show you how to achieve just that. In this Article I'll show how to deploy printers automatically with group policy and then using security fil…
I've attached the XLSM Excel spreadsheet I used in the video and also text files containing the macros used below. https://filedb.experts-exchange.com/incoming/2017/03_w12/1151775/Permutations.txt https://filedb.experts-exchange.com/incoming/201…

696 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question