Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: Jan Erik Amundsen on March 28, 2000, 12:21:42 AM
-
Hi
I have installed my e- smith on an box witch is connected to a windows LAN. When I open Network Neighborhood I don't see my e-smith box. What do I do wrong? I know it's something I have done wrong but what?
Does anyone have some ideas?
B.T.W I don't use it as an gateway just a server.
Kindly regards
>Jan Erik Amundsen
-
Hello,
> Hi I have installed my e- smith on an box witch is connected to
> a windows LAN. When I open Network Neighborhood I don't see my
> e-smith box. What do I do wrong? I know it's something I have
> done wrong but what? Does anyone have some ideas? B.T.W I don't
> use it as an gateway just a server.
When you open up network neighborhood can you see other computers on the network. If so try clicking on "entire network" as default e-smith uses the workgroup name homenet (don't quote me on this).
-geoff
-
You have not provided enough info. What is your Windows workgroup? Is it strictly Peer to peer or have you designated a server? Is that server a NT server that has been designated as a PDC? Who is setup to provide the DHCP services? You can't have more than one.
-
Hello
I have tried to click on everything in network Neighborhood. It's not there. My domain is named "PRIVAT" witout qoutes.
All workstations have tcp/ip and netbios. All have fixed ip adress and they can all see eachother.
In e-smith I have set it up to have an fixed IP adress and subnetmask. I haved named it "LINUX". However it do not want a domain name witout a lastname. Like ".com" or something. Therefore I choosed ".PRIVAT" as domain. Is this somewhat wrong?
Kindly regards
Jan Erik Amundsen
Jerry wrote:
> You have not provided enough info. What is your Windows
> workgroup? Is it strictly Peer to peer or have you designated a
> server? Is that server a NT server that has been designated as
> a PDC? Who is setup to provide the DHCP services? You can't
> have more than one.
-
Jan erik Amundsen wrote:
> Hello I have tried to click on everything in network
> Neighborhood. It's not there. My domain is named
> "PRIVAT" witout qoutes.
>
> All workstations have tcp/ip and netbios. All have fixed ip
> adress and they can all see eachother.
Your PCs will be more reliable if they only use tcp/ip, rather than mixing tcp/ip and netbeui (I presume that is what you mean when you say netbios).
> In e-smith I have set it
> up to have an fixed IP adress and subnetmask. I haved named it
> "LINUX". However it do not want a domain name witout
> a lastname. Like ".com" or something. Therefore I
> choosed ".PRIVAT" as domain. Is this somewhat wrong?
You are confusing the concept of internet domain name with the concept of windows networking domain (and workgroup, almost the same thing).
If you want your server to show up in the network neighbourhood you should set the same windows domain name as your workstations. You should still be able to find it in the whole network, or by Find->Computer.
Charlie
-
not to mention that "." is an invalid first character in a domain name and as far as I remember (it's been a while since I've seen someone try to use it as such) it breaks some network connectivity with some systems. SO, it is not suprising that something with a domain of ".PRIVAT" isn't being seen in your network neighborhood. I would just drop the "." and have everything in the "PRIVAT" domain. if I am not mistaken, you change the domain using the console (as opposed to the web-based admin)
-
Just a little off topic here, but howcome E-Smith won't allow me to use the workgroup name 0? It comes up and tells me that the workgroup name is not valid because it starts with a character. However all my windows machines worked just fine under the workgroup 0? Just a strange little thing I found.
-
Hi
Well, after a little moore research I have found out that if I remove Netbeui from a windows pc, it disappers from the network. I canstill ping it, but I cant see it.
So it seems that for that reason e-smith does not appear in Windows Network Neighborhood.
The reason for this I don't know, but if there is someone out there who does - please notify me.
Kindly regards
Jan Erik Amundsen
-
For starters, be sure that you have a valid workgroup name, say "office"
set the workgroup field in each workstation to "office"
set the workgroup field in e-smith to "office", don't worry about the Domain designation. Use e-smith to provide DHCP services. Let each Workstation obtain their
ip address from the e-smith server. Also besure to provide e-smith with a primary and
secondary DNS service if you are accessing the internet.
There is no reason to have netbui turned on at the Workstation level if you are using an e-smith server. TCP/IP will do the job.
If you can ping the server from each Workstation you are running properly and you
should be able to see the server.
hope this helps.
-
Jerry wrote:
> Also besure to
> provide e-smith with a primary and secondary DNS service if
> you are accessing the internet.
Actually that is optional. Name resolution will work fine using the e-smith server's built-in name server without specifying external DNS servers. The external servers might speed name resolution if they are well connected and competently run.
Charlie
-
This one I know a little about. Sounds like everyone has got some good suggestions, and will help you get there. Windblows is so very sensitive with workgroups. Many times this where things will go wrong especially trying to speak with Linux. Make sure the workgroup is the same all the way around. Also, I think e-Smith 4.0 uses e-smith as a default workgroup, not sure about 3.0.
-
Hello
I apprisiate that everybody is trying to help me out here.
Here is the latest info on the problem:
I have tried to remove netbeui from every windows box on my LAN. The result was that noone could see eatchother in Windows Network Neighborhood. However I could ping everyone. I had shared folders on all of them, but it didn't help much. I even tried to shut everything off an then on again to see if it helped, but no. When I installed netbeui again on 1 pc I could instantly see it.
This is not very funny situation when every linux box uses only tcp/ip.
In e-smith I have a fixed IP adress and set my LAN workgroup to PRIVAT on every box on my LAN.
Enyone?
Kind Regards
Jan erik Amundsen
-
Here goes,
netbeui has to be on for the windows boxes to speak, so even if Linux doesn't need it, it has to be there. Set your Linux ip as 192.168.1.1 and all the others to get theirs from the server. MAKE sure your linux workgroup is the same as you windows boxes. This is NOT the same as the domain.
Good luck
Garret
-
Garret Acott wrote:
> netbeui has to be on for the windows boxes to speak, so even
> if Linux doesn't need it, it has to be there.
That just simply isn't true. The clients do not need netbeui, but they do need Netbios over TCP/IP, which translates in Microsoft speak to needing the Microsoft Networking Client with a binding to TCP/IP.
> Set your Linux ip as
> 192.168.1.1 and all the others to get theirs from the server.
> MAKE sure your linux workgroup is the same as you windows
> boxes. This is NOT the same as the domain.
That is all true. It will also help the clients to locate the network shares if the checkbox to use DHCP to locate WINS server is checked.
Charlie
-
Hello
Thank you for all your help and this is the latest info on this issue.
I have the same workgroup on all boxes, named PRIVAT. One windows box I tried to use DHCP with wins resolution checkbox on and this one could actually find e-smith. All other with fixed IP do not,yet.
This is my e-smith domain config:
System name: linux
Domain name:
Windows workgroup: PRIVAT
Windows server name:PRIVAT
Backup DNS server (1): < Is it IP or \servername that this means?>
Backup DNS server (2):
Kind Regards
Jan Erik Amundsen
Norway
-
Jan erik Amundsen wrote:
> Hello Thank you for all your help and this is the latest info
> on this issue.
>
> I have the same workgroup on all boxes, named PRIVAT. One
> windows box I tried to use DHCP with wins resolution checkbox
> on and this one could actually find e-smith. All other with
> fixed IP do not,yet.
Either be patient, or configure them to use DHCP and WINS. Without WINs, the machines all have to chat to each other to work out which is responsible for collecting a list of names and resources. This takes time, and net traffic.
> This is my e-smith domain config:
>
> System name: linux
> Domain name:
> Windows workgroup: PRIVAT
> Windows server name:PRIVAT > with this one. I don't know what this does. Could anyone fill
> me in here?
That is the system name as far as Windows networking is concerned. Windows networking uses a whole different name space than DNS does. To save confusion, you might set it to "linux".
> Backup DNS server (1): < Is it IP or
> servername that this means?
It is IP. The DNS server specifications are optional - the name server in the e-smith server/gateway will function fine with nothing entered here.
Charile