SG Broadband Community

Ok. I got netbeui loaded on my XP laptop (I went through the have disk on the install protocol), worked like a champ. However, with only netbeui binded to file and print sharing and client for microsoft network (on desktop, win 9e se), I can't see the other computer (98 se). When I'm binded to tcp/ip, it works fine. Two questions. I'm connecting to my network from a wireless card, to my linksys ap (befw11s4 ver 2) which is connected to my desktop via ethernet. I know netbeui is non routable, hence that is why we use it to secure our computers. Since I'm going through a router via the AP, is that why it doesn't work (non-routable through my router). Also, when I turn off netbios in xp on my wireless card, it doesn't work. Does the linksys router require netbios over tcp/ip to see the other computer? I also have tiny personal firewal, version 2.0.15, installed on both. In the advanced, microsoft networking, I put the router ip address as a trusted network address. Is this smart, and the only way? I also put the entire network, with subnet mask. Lot of questions, hope it wasn't too confusing. Thanks.

Phil

Make sure that you have NetBEUI bound to the NIC in your XP box. Navigate to Start | Settings and double-click Network Connections or Start | Settings | Control Panel | Network Settings. The following screen should appear:


Select Advanced from the menu on the top of the window. The following screen should appear:


Make sure that the NetBEUI Protocol box is checked under File and Printer Sharing for Microsoft Networks and that the Internet Protocol (TCP/IP) box is NOT checked.

Since I'm going through a router via the AP, is that why it doesn't work (non-routable through my router).

NetBEUI is not routable over the internet. It is, however, routable over your LAN.

I don't know that the AP supports NetBEUI. Linksys WAP's claim that they support CSMA/CD, better known as ethernet, so I would assume that the AP does support this protocol.

Also, when I turn off netbios in xp on my wireless card, it doesn't work. Does the linksys router require netbios over tcp/ip to see the other computer?

NETBIOS is required for file/print sharing over TCP/IP

I also have tiny personal firewal, version 2.0.15, installed on both. In the advanced, microsoft networking, I put the router ip address as a trusted network address. Is this smart, and the only way?

I'm not familiar with this package so I can't speak to it's use. However, placing your routers IP as a trusted network doesn't pose a security risk as it's most likely in the private address range of 192.168.x.x. By setting that range as a trusted network you are telling the firewall that any connections from that range are safe.

One thing to realize....yes NetBEUI is not a routable protocol....therefore is more secure than TCP/IP, which, along with IPX, is a routable protocol.

But routers use NAT to provide a basic hardware firewall for your LAN. You only need to worry about protocol security if you have ports open/forwarded...meaning, if you have a computer in the DMZ, or if you have lots of ports open for services such as web, FTP, game, etc. If your router is totally closed, meaning no ports are open, then no traffice is making it out. If you have ports open, then traffic would "escape"..such as TCP/IP if it could.

Well,
I finally got back and tried the bindings. I bound netbeui to file and print serving. Still can't get the computers to see each other. If I bind tcp/ip, it works (takes a while to see each other, though). They are in the same workgroup, same subnet mask. I can ping by ip address, but not by name (I have netbios unchecked). I disabled the firewalls to make sure it wasn't the problem. I don't even see my xp computer in the workgroup on the xp computer. On my network places, I see my shared folders. Any more ideas? Thanks.

Phil

Under the dynamic routing tab of the router setup, it shows
Dynamic Routing TX, and RX, with RIP1, RIP1 Compatable, RIP2 and disabled as options. Does this have anything to do with it?

Thanks again.

Phil

As far as bindings, perhaps this article from Gibson research will help Bindings
For XP of course follow the NT instructions. Make sure the binding configuration match on all machines.

The router needn't be in the trusted zone, just the range of ip's of the boxes on your network.

Same user account exists on both 98 and XP machines?

[quote]
They are in the same workgroup
I don't even see my xp computer in the workgroup on the xp computer. On my network places, I see my shared folders.

I ran into problems with WEP when sharing between with XP and 98. Get the hex key off the router (must match exactly)
For XP go to the wireless network properties
SSID = (matches your router SSID)
WEP enabled
Network key= (hex key from the router)
Format=Hexadecimal digits
Length= "104 bits (26 digits)"
Provide auto=disabled
Reboot
Once I cut and pasted the hex key and figured out 104 bit (confusing since its a 128 wep hex key) and rebooted, they showed up network places just fine.

I've been through Gibsons site, and that was what I was trying to do. New to XP. I knew XP and NT were close, but I assume that the steps for NT will work. All the data out there doesn't have too much for XP. By same username, do you mean when I log onto Microsoft Network in 98, and the username in XP? They are not the same. Do I need to make a user in XP that is the same name as my logon in 98? Do I make the same password for logging on in 98 as the new user in XP? Thanks for your help. I'll follow the NT example in GRC.

As for wep, it seems to be working, as I can get on the internet just fine. Could you do this, or was it a separate problem?

Phil

I tried the NT way at GRC, but I couldn't even find where to add an adapter (loopback adapter?) It only has Client, service, and protocol listed. Am I in the wrong place, or is NT different (never used NT). Thanks.

Phil

Yes, you've got it Phil. Create a user account in XP the has the same user name as your 98 MS net logon.
If Phil wants to access Sally's machine, there needs to be a Phil user account on the Sally machine. And the reverse, user account Sally has to exist on Phil machine for Sally to access. I don't think the actual passwords matter, but you could match them. You don't have to be logged in as the same user on both machines; the same user accounts just have to exist on both boxes (for authentication purposes). As well as, the workgroup names have to match, and the ssid's and the wep keys(or phrase) on the router and wlan cards have to match, exactly.

WEP> For me each machine could get on the net just fine, but didn't show up in Network Places for file sharing until I did the WEP fix (cut and pasted the actual hex key) on the XP box.

You should be reeaaal close to being networked.

I think I'm going to cry uncle on the netbeui method. I removed netbeui and just used tcp/ip as my network protocal. Works fine (does seem like it takes a while to browse the network, though). I'm behind a router, without any funky ports open, so hopefully it will be enough. Maybe after my hair grows back after pulling it all out, I'll try again. Thanks for the help.

Phil