We have two LANs connected via ISDN. One site runs a remote app on the other using MS Windows NT Terminal Server thin client.
I need to enable printing to a local printer at the client site (the one running the remote app). The problem is that the only way I can think to do this is to add the printer to the remote server as a network printer by browsing to it, but the machines on these LANs cannot see each other.
They can ping each other fine, and the "client" site has no problem running the remote app, but I cannot add the printer since I cannot browse to it to add it as a newtork printer on the server where the remote app is running.
Other facts which may help:
1) the remote LAN has a Windows NT server but while clients use Client for MS Networks none are actually logging on to the server (log onto Windows NT domain is not checked).
2) the machines on each LAN can see machines on that LAN, but not machines on the remote LAN
3) all IP addresses on the site with the app installed are like 192.0.0.x with submask 255.255.255.0 - all IP addresses on the client site which runs the remote app are 192.0.5.x with subnet 255.255.255.0
4) Machines on both LANs have the same workgroup defined
5) There must have been a recent power spike, I guess, because the coax cable at the "client" site was fried, and the ISDN router configuration was reset to the default. I had to rebuild the configuration for the router, so maybe the problem is there?
Any ideas?
I need to enable printing to a local printer at the client site (the one running the remote app). The problem is that the only way I can think to do this is to add the printer to the remote server as a network printer by browsing to it, but the machines on these LANs cannot see each other.
They can ping each other fine, and the "client" site has no problem running the remote app, but I cannot add the printer since I cannot browse to it to add it as a newtork printer on the server where the remote app is running.
Other facts which may help:
1) the remote LAN has a Windows NT server but while clients use Client for MS Networks none are actually logging on to the server (log onto Windows NT domain is not checked).
2) the machines on each LAN can see machines on that LAN, but not machines on the remote LAN
3) all IP addresses on the site with the app installed are like 192.0.0.x with submask 255.255.255.0 - all IP addresses on the client site which runs the remote app are 192.0.5.x with subnet 255.255.255.0
4) Machines on both LANs have the same workgroup defined
5) There must have been a recent power spike, I guess, because the coax cable at the "client" site was fried, and the ISDN router configuration was reset to the default. I had to rebuild the configuration for the router, so maybe the problem is there?
Any ideas?
