Q: Hey All,
There a simple answer to this question, but it has me baffled. I have three static IPs in my house. So far, three of each machine occupies one of the addresses and I could printers and files. Now I am adding a few machines, so I picked up a DLink Dl-604 broadband router and they get one of the statics and put one of the machines on the routers private IP range (192.168.xx). I can surf the web and e-mail and all of that machine no problem. What I can do is to abandon the machine or other means to share with them. Heres how the machines are set:
All have NetBEUI in addition to IP addressing.
All have Netbios over IP with a disability (net hacking security) all have the same workgroup 0.
name.
All permissions for others to use them (ie they worked before the change)
The WAN side of the DSL modem is plugged into the wall (duh!)
The LAN side of the DSL modem is connected to a crossing gate on an 8-port switch.
The WAN side of the router is connected to a port on the 8-port switch.
The LAN side of the router is connected to a port on the 8-port switch using a crossover cable.
The machine with the private IP connected to a port on the 8-port switch.
The machine with the private IP NetBEUI is set as primary protocol.
All other machines connected to the 8-port PS switch.
Thanks for insights.
Joe
A few questions like:
Can NetBEUI Cross off to another? It is not “driven” per se, but maybe its not the same as two devices connected to the same switch.
Re:Originally posted by: guy
guy!
You're right!… well, halfway. I did right on the Win98 machines, but I didn't even realize that the Advanced->Advanced Settings menu was there in that folder! Thanks for teaching me something new! You were correct that TCP/IP was still checked off for both MSFPS and MS Networking.
Thanks for the new knowledge.
Joe
Your velcome! This is one of the things I uncheck on a Win2K Web Server, in my long-long security lockdown list.
Re:guy!
You're right!… well, halfway. I did right on the Win98 machines, but I didn't even realize that the Advanced->Advanced Settings menu was there in that folder! Thanks for teaching me something new! You were correct that TCP/IP was still checked off for both MSFPS and MS Networking.
Thanks for the new knowledge.
Joe
Re:For the LAN file sharing, my guess is you did not do the following on the Win2K PC's: Network Connections folder -> Advanced -> Advanced Settings -> Uncheck TCP/IP for both, if you want to exclusivley use NetBEUI for MSFPS.
Any Win9X PC's, you go into bindings under TCP/IP and uncheck MSFPS, etc.
Re:AHHHH HA!
Tried something just to see what would happen…. AND IT WORKS PERFECTLY!
On my STATIC (Routable) IP Machines (Win2k Pro) I was fiddling around with the TCP/IP configuration under network settings. Under advanced, there was something I'd never noticed before… a place to add ADDITIONAL IP addresses to the same NIC! I went ahead and added 192.168.0.95 and the appropriate subnet mask and VOILA! it all works perfectly!
I'm a little confused though, as I thought that a NIC could only be assigned a single IP… but I guess I'm pretty wrong about that! Anyway… even though I'm still doing my LAN file and print sharing with NetBEUI, it seems that Windows still wants the machines on the same logical network (subnet) of the IP protocol even when they are already on the same physical network.
I am also implementing the practice that knupt spoke about with the different display number (and hence port) for each machine running VNC.
Thanks everyone….. just thought I'd give this update since I had some success.
Joe
Re:If the only reason to have more public IP's to use remote desktop programs, you could use it like I mentioned, and remove the two extra IP's. Then move all your computers behind the router, and then you can do all the filesharing you would like to.
You know…. you're absolutly right!
I'm still curious why the NetBEUI isn't working…. but it's more a curiosity now instead of a necessity.
Thanks,
Joe
Re:U can change the default ports in pcanywhere.
Re:If the only reason to have more public IP's to use remote desktop programs, you could use it like I mentioned, and remove the two extra IP's. Then move all your computers behind the router, and then you can do all the filesharing you would like to.
Re:Still doesn't help with file and print sharing though
For the love of god man! TURN NETBIOS BACK ON!!
Re:Take a look at the SMC Barricade 7004VBR.
It is a $50 Router thta can put few computers with independent IPs in the DMZ Zone.
Re:HEY NOW!
That's worth going for. It wouldn't help with PCanywhere (which I use sometimes for file transfer), but I could always just copy the files to the computer that was PCanywhere enabled and the get them from there.
Still doesn't help with file and print sharing though.
Thanks for the imput… I'm gonna give the VNC a try anyway!
Joe
Re:You could forward different ports to different computers. If you put display number 1 in the winvnc properties, the port 5901 (and 5801) will forward to another computer than the primary with display number 0 and port 5900, and 5800.
Re:NetBEUI is not suppose to work through RoutingWhich is exactly why I have all machines hooked to the switch first… so that the NetBEUI packets won't have to hit the router. The IP packets do forward from the switch to the router and go outbound through the router's WAN port back to thw switch and then out to the modem.
If it works you have to make a decision whether you really need to use the two extera IPsThey aren't extra. I get into my machines via VNC and/or PCanywhere from remote locations. Since I can only port forward to a single machine, that isn't possible for these two machines unless I use static IPs.
Joe
Re:NetBEUI is not suppose to work through Routing, I don?t know whether this apply to Entry Level Cable/DSL Router (nevet tried it), since they are a special case of the general.
For the heck of it, plug all computers behind the Router (don?t forget to enable DHCP on the private IP computers), and see if you get a functional Network.
If it works you have to make a decision whether you really need to use the two extera IPs (there is a known phenomenon that people tend to get obsessed with using free things even when it become unnecessary), or just stick with one IP and the Router.
Re:Dude, turn off NEtBEUI, turn NetBIOS back on.
Put a firewall up on your gateway.
Enjoy your filesharing.
Re:Well… another week starts… after a holiday weekend.
Anyone back at work with any ideas?
Joe
Re:Seems like it *should* work. NETBEUI should not care that there is a router plugged into the switch. It should just communicate with the other machines that have NETBEUI installed on them.
Must be something your overlooking… not sure. It *should* work.
Re:Ok… lemme try again….
The DSL modem goes to the 8 Port switch. This is because I have 3 incoming static IPs. By hooking the modem into the switch, it makes the connection available to the router and the other two machines with static IPs.
The router's WAN side goes to the switch via a CAT5 straight cable… this is where the router makes it's connection to the modem and out to the internet.
The router's LAN side (one of the ports) goes to the switch via a CAT5 crossover cable. This is because I'm connecting a switch port to a switch port. I'm hooking the router's LAN side to the switch so that I can hook the private LAN computer's cable to the same switch (just to make sure that it's on the same "physical" net as the other machines.
The static IP machines are hooked to the switch via CAT5 cables.
The private LAN machine is hooked to the switch via CAT5 cable.
Everything is connected. Everything can ping everything. Everything has internet connectivity. The private machine get's its IP and DNS through DHCP from the router just fine.
The problem is that I can no longer share printers and files between the machine on the private LAN side and the other machines. I would understand this if I were doing file and print sharing via TCP/IP, but I've installed NetBEUI on all the machines and have made sure that their workgroup is the same. When all were static IP's on the same subnet, everything worked fine… the problem came only after going to a private range for the one machine.
NetBEUI is a non-routeable protocol, but it should always work as long as all of the machines are on the same physical network. I works just peachy on networks that don't even have IP addressing and shouldn't be effected by the IP's in this situation…. so I'm a little stumped. I've made sure that all the machines are physically cabled on the same switch, so the router (NetBEUI isn't routable anyway) isn't even in the loop for this protocol.
Anyone have any ideas?
Joe
Re:Im not quite getting the structure of your network.
I really hope that you got 2 8 port switches, and that the dsl modem are connected to one of them, and one cord are going out from that one to the wan port on the router, and after that you have connected the computers.
But it does seem like you have connected all computers (and dsl modem) to the same switch. Then you would need to connect a cable from the dsl modem straight to the router, and not through a switch.
What kind of router do you have? The DHCP server on the SMC barricade works great. I have had it 1,5 year and it haven't changed the IP of my main computer yet. It's not difficult for me at all to use DHCP on the router and then open ports to specific PC's.
Re:File Sharing is bound to what protocol?
On the private IP machine it's bound to NetBEUI… it's a Win98 machine. The others are Win2k. How do I bind File and Print sharing to a specific protocol on Win2k?
Joe
Re:I keep statics so that I can remote (VNC, PCanywhere) into my machines from remote locations.
Re:File Sharing is bound to what protocol? NetBEUI is not routable so if it's bound to that then you're hosed and you'll have to go with a routable protocol (like TCP/IP). My next question would be is there a need for the static addresses now that you have a router?
Re:It just occurred to me that in the near future I plan on adding some wireless. I'm guessing I'm going to have the same issues there also. If anyone knows for sure, let me know.
Joe
0 Comments.