DavidRoper
Programmer
I have a home office network with a Win 2K professional system, an iMac and various other stuff connected via a 3Com Office Connect ISDN LAN modem which has a 4 port ethernet hub, acts as a router and provides DHCP and NATS to the network. I found some good Mac NetBEUI software, so I just use the default WORKGROUP for local peer-to-peer networking.
I have to connect to a customer who is running NT 4.0 SP6a. I have got the PPP link up from the LAN modem to their RAS server and, having copied their HOSTS and LMHOSTS files, can happily ping any machine on their network.
What I can't do is see any of their computers or shares under "My Network Places". If I go to the Network Identification Wizard and try to tell the system that it's part of the XXXX domain, I simply get an error saying that the domain could not be contacted.
I suspect this is because I've not been able to tell my system the name (or IP address)of their domain controller. Consequently it it broadcasting(?) on the local net (192.168.1.0) and the router (quite rightly) isn't forwarding the packet. I somehow need to tell my system, "when you're booting, use XXX.XXX.XXX.XXX as your domain controller, the router knows how and where to root all packets for the XXX.XXX.XXX.0 sub-net."
Any help gratefully received.
I have to connect to a customer who is running NT 4.0 SP6a. I have got the PPP link up from the LAN modem to their RAS server and, having copied their HOSTS and LMHOSTS files, can happily ping any machine on their network.
What I can't do is see any of their computers or shares under "My Network Places". If I go to the Network Identification Wizard and try to tell the system that it's part of the XXXX domain, I simply get an error saying that the domain could not be contacted.
I suspect this is because I've not been able to tell my system the name (or IP address)of their domain controller. Consequently it it broadcasting(?) on the local net (192.168.1.0) and the router (quite rightly) isn't forwarding the packet. I somehow need to tell my system, "when you're booting, use XXX.XXX.XXX.XXX as your domain controller, the router knows how and where to root all packets for the XXX.XXX.XXX.0 sub-net."
Any help gratefully received.