General discussion

Locked

Unable to Browse the other network PCs

By ashvak ·
We have two remote office connected to H.O on leased line in an Window NT 4.0 single Domain.
I am unable to see other network PC from the PDC and H.O network.If use IPX/SPX in my workstation in H.O i can see the other network PCs.Similarly from theother end if i use IPX/SPX i see all the H.0 PC's .
If any further clarification let me know.

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Unable to Browse the other network PCs

by DC1 In reply to Unable to Browse the othe ...

Should the network be TCP/IP? If so make sure you have either WINS or DNS running on the networks for name resolution.

Collapse -

Unable to Browse the other network PCs

by ashvak In reply to Unable to Browse the othe ...

I would like to thank u for the reply.
I'm working around the wins & dns. but couldn't find any problem. Wins is configured on PDC and DNS is configured on webshield e-appliance firewall.
But i couldn't find any problem in that as the name resolution is going on.
But i could not see the other network pc on PDC(NTserver 4.o).
If anything deep u suggest me to check.

Collapse -

Unable to Browse the other network PCs

by jwilczyn In reply to Unable to Browse the othe ...

If you are using IPX, can you check your frame type settings - maybe it's your problem.

Collapse -

Unable to Browse the other network PCs

by ashvak In reply to Unable to Browse the othe ...

Basically, it will be better we think on tcp/ip side as it our major protocol used by our system.Anyway i check this.
Thanks for ur reply

Collapse -

Unable to Browse the other network PCs

by NetTek In reply to Unable to Browse the othe ...

It is apparent that you would like to use TCP/IP as your protocol. You don't say whether or not you can ping across your routers by IP address or name, or if you are using DHCP or static addresses, so I can only give you broad information.

First,it is obvious that your routers are set up to pass IPX/SPX traffic, since you can communicate over your WAN using that protocol. But have the routers also been set up to pass TCP/IP traffic?

If they have: In the remote offices, make sure that the PCs have the WINS servers IP addresses and the default gateway (their local router's IP address) installed under their network properties. If their default gateway is set to another IP address, such as for Internet access, you need to add a ROUTE.EXE statement to the PCs so that they will know to use your WAN router to get to the HO network. You can add the Route statement in a login script, or use a batch file in the local PC's Startup folder.

Similarly, at your HO, use a persistent Route statement on your servers so that they know how to get to your remote networks.

Collapse -

Unable to Browse the other network PCs

by ashvak In reply to Unable to Browse the othe ...

The question was auto-closed by TechRepublic

Collapse -

Unable to Browse the other network PCs

by gmscne In reply to Unable to Browse the othe ...

Have someone right-click on their network neighborhood icon to get to the properties.
On the configuration tab, click on "File and Print Sharing", and have them select "I want to share my files". This will permit the computer to show up when browsed.

Collapse -

Unable to Browse the other network PCs

by ashvak In reply to Unable to Browse the othe ...

The question was auto-closed by TechRepublic

Collapse -

Unable to Browse the other network PCs

by ashvak In reply to Unable to Browse the othe ...

This question was auto closed due to inactivity

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums