can't access Microsoft Networks client over WAN

[pbxphoneman]

I have a network setup with WIN95/98 Microsoft Networks ..works fine on one side of the LAN but I'm trying to access same setup across a WAN (T1) doesn't.Other side of the WAN works fine too, just doesn't show the remote computers in Network Neighborhood..I'm logged in because I can see my network profile.
I can ping/tracert fine to the remote computers (on either side). just can't see them.
Should I have a route on the workstation that points to t he remote network?

thanks for the input

 

[TheOldMan346]

pbxphoneman,

What you're trying to do is establish a Virtual Private Network (VPN). You can't do this just having both networks connected on the internet. You'll either need additional software or hardware on both sides to do this. Here's some information that might be helpful.

http://www.howstuffworks.com/vpn.htm

What goes around - comes around.
The Old Man

If you feel that this post can help others, please indicate it with a star.

 

[pbxphoneman]

It is a T1...I own every aspect of it..from the cable to the 2 routers at each end...It connects to building about 1000ft away.I'm not using VPN..
I have been looking towards the Browser Master issue and might give that a try.

thanks !!!!!!

 

[TheOldMan346]

Ahhh. You didn't say it was a dedicated T and I assumed it was connected by way of the internet. My bad for assuming.

Could very well be Browse Master issues if you can ping and tracert back and forth. Are you in a workgroup or domain? I would guess domain but thought I better ask. Multiple domain controllers? WINS server(s)?
What goes around - comes around.
The Old Man

If you feel that this post can help others, please indicate it with a star.

 

[pbxphoneman]

computers are just configed with "workgroup" as "workgroup" on both LANS..I tryed switching workgroup names on remote lan to see if that made a difference...notta.default proto is TCP/IP.not using WINS.have static IP's,no DCHP.NETBIOS is grayed out(and can't be changed for some reason) but,is checked "I want to use NETBIOS over tcp/ip" (someone told me I should be using that) basically defaults right out of the box (microsoft networks)
any ideas where I should be tweaking...I tryed using NET DIAG... same results..ping tracert work fine end to end.

thanks!!!!!

 

[TheOldMan346]

pbxphoneman,

What is the make/model of the two routers?
Are there any ACL's used on the routers?

Pick a representative computer in each LAN segment and do the following on each. Say you picked 192.168.1.10 in segment A and 192.168.1.100 in segment B. On 192.168.1.10:
1. Open a DOS prompt.
2. Type "ipconfig /all" without the quotes
2. Type "netbios -an" without the quotes
3. Type "netstat -an 192.168.1.100" without the quotes
3. Copy the results and post back here

Do the same on 192.168.1.100 and post the results back.

What goes around - comes around.
The Old Man

If you feel that this post can help others, please indicate it with a star.

 

[pbxphoneman]

I found that I need to Have WINS or DNS to resolve this matter ...thanks for everything!!!!!!!!!!!!!

 

[pbxphoneman]

I have win95/98se machines.
NETBIOS command doesn't work
HOSTNAME doesn't either
machine 192.0.3.10 =win98se
hostname=laptop
node type= broadcast
and usual adapter addy,ip addy,subnet mask (255.255.255.0)
and default gateway (router) nothing checked on any of the other options ie..ip routing,netbios resolution..etc on either machine.

when running NETSTAT -AN ....
I get 3 TCP/IP IP's & 2 UDP's listening

however

when running this on other machine (win95) (192.0.2.10) other side of T1.
I don't get any TCP/IP listed
just UDP's .... and nothing listening
I think something is up here??
I have entry in host file for the win98 machine and it pings the win95 machine just fine with the computers name....but not the other way around...ping works fine using ip's between both machines....just can't get the computers to show up in network neighborhood.

 

[pbxphoneman]

ok,,,name pinging works fine on both machines now

 

[TheOldMan346]

pbxphoneman,

In Win 95/98, the network neighborhood is accomplished using NetBEUI protocol unless you have configured TCP/IP to carry NetBIOS. Not sure if that is even a possibility with Win95. NetBEUI is a non-routable protocol and will only work on the SAME subnet. You have different subnets (192.168.2.x and 192.168.3.x) so this is not going to work. You already have the names/addresses in your host files. You can also use the LMHOST files but I don't believe you will be able to share files. You might want to consider upgrading the Win96 machines to Win98SE or upgrading all the machines to a newer OS like Win2K or Win XP. Support for Win9x will soon terminate if it has not already.

Hope that helps. What goes around - comes around.
The Old Man

If you feel that this post can help others, please indicate it with a star.

 

[pbxphoneman]

I just found what you said in a book (bought it today,lol) It is a common question that is asked of WIN9x...i have to add/use a routable protocol (tcp/ip ) BUT I'll need a WINS server if I use it... ok..can I setup WINs on a 95/98 machine to be able to reach my machines in the other subnet? or upgrading to XP will fit the bill?

thanks a million

 

[TheOldMan346]

Actually, that's not exactly true. You can use a routable protocol like TCP/IP without a DNS or WINS server. That's what many home networks are these days. Populating your HOSTS and LMHOSTS files will provide name resolution services in the absence of a WINS server. I run Win98SE, WinNT and WinXP on my network with full file sharing over TCP/IP with no WINS server. I recently installed Linux on one of the machines for other purposes and turned on a WINS server there but that had no effect on the sharing.

I would seriously recommend upgrading to at least Win98SE. If the money is not an issue, XP would be the best to upgrade but you'd need new licenses for everything. Win98SE will be less expensive and get you the needed protocol capabilities.

Hope that helps. What goes around - comes around.
The Old Man

If you feel that this post can help others, please indicate it with a star.

 

[pbxphoneman]

does your network span across a WAN (router)though?...that is where I'm having a problem....everything works great on this side..win95..win98 & XP machine...all come up in network neighborhood....I can share internet (dsl) and file share all over the place...I'd like to be able to do this with TCP/IP to the other side.I have loaded the HOSTS file on each side of the WAN and I can PING with IP or with name of machine just fine.just doesn't show an icon in the folder.I haven't loaded LMHOSTS yet though...is it nessasary to do both?

thanks again

 

[TheOldMan346]

Not currently but it did in the past. No T but a router joining multiple segments. This should provide the necessary information.

http://support.microsoft.com/default.aspx?scid=KB;en-us;q150800

Good luck. What goes around - comes around.
The Old Man

If you feel that this post can help others, please indicate it with a star.

 

[bierhunter]

Without a WINS server or LMHOST files, your machines are relying on broadcasting to create a browse list for the network. Broadcasts by default are blocked by the routers.

You can set up LMHOST files, setup a WINS server, or configure the routers to forward the broadcasts (depending upon what type of routers).

The HOSTS files are used for traffic using the FQDN (Fully Qualified Domain Name) of the machine. (ie...like DNS).

The LMHOST files are needed to browse the network, since that is handled at the netbios level.

So, basically that is what you need in order to establish internetworked browsing. I get the impression that there aren't any servers on the network, so the LMHOST file or setting the routers to forward broadcasts will be most likely what you will need to do.

Hope that helps.

 

[pbxphoneman]

there are no servers on either LAN segments.Just using combo of computers (win95/98se,me,xp) on each sides of the router (Intel 8220 & openroute gt60).I have the HOSTS file
in each machine but still can't browse..I guess that's what I'm after (to be able to share files,printers etc...to see the available comps across the WAN in network neighborhood)
I'm under the impression that the Microsoft Networks that is packaged with win 95 & 98 uses NetBUEI and can't be routed across my router. thus the need for TCP/IP.I'm looking at upgrading all the win95 to win98se as soon as I can find that damn disk

Question
....the 3 protocols that are packaged with Wins95/98...ipx,tcp/ip & netbeui.... if your default proto fails (tcp/ip) will the computer attempt to use the other ones,or is it just one protocol per network segment?

Question..
Should I delete my HOSTS file then if I'm going to use LMhosts so there isn't a conflict?

Question..
does win98se have better network flexability then win95 to make my situation work.

I'm going to play around with the LMhosts file now and see if I can get it to share files across the segments.

thanks for all the info...I'm learning alot here,more so then in the books !!!

 

[bierhunter]

You can use TCP/IP instead of netbeui. The windows networking will use netbios over tcp/ip.

Yes, you can use HOST files and LMHOST files together without conflict. They serve different purposes.

The HOST file is for finding a machine by

http://www.mydomain.com

and works at the TCP/IP level.

The LMHOST file is for finding a machine by computer name such as \\myserver and works at the netbios level.

The HOST file is like a DNS replacement and the LMHOST file is like a WINS server replacement.

We had a similar situation with a client where some of their people worked across the complex where their network was controlled by a different group of people. Therefore, they had no access to our WINS server. We set them up with LMHOST files, and they could then log in, browse etc. Of course, you will have to have an entry in the file for every machine you wish them to see.