Koozali.org: home of the SME Server

win2k as a client to e-smith ver 4

craig

win2k as a client to e-smith ver 4
« on: January 26, 2001, 04:21:44 PM »
hi,
i have setup my esmith box as per istructions (and it was painless !!:) )
however i am experiancing problems connecting using my w2k prof pc.
i get an ip address from the dhcp - np there, and i can access the manager via http, and i can telnet into it also. but i have nothing in my network places. both boxes are in the same workgroup, and i can ping the server again - no probs.

any suggestions ??

also i have a win me box that is set up the same and has the same problems, telnet,ping,http all fine - but the 2 clients cant ping each other ??? winipcfg reports routing disabled - is this related ???

any help appreciated..

btw - great product anyway !!

Paul

Re: win2k as a client to e-smith ver 4
« Reply #1 on: January 28, 2001, 02:17:55 AM »
craig wrote:
>
> hi,
> i have setup my esmith box as per istructions (and it was
> painless !!:) )
> however i am experiancing problems connecting using my w2k
> prof pc.
> i get an ip address from the dhcp - np there, and i can
> access the manager via http, and i can telnet into it also.
> but i have nothing in my network places.
> both boxes are in
> the same workgroup, and i can ping the server again - no probs.
>
> any suggestions ??

Does the userid and password you are using on the windows boxes correspond to userid/passwd on the e-smith server?  If they are, can you find the e-smith server? (ie. start->find->computer-> "e-smith-server").
 
> also i have a win me box that is set up the same and has the
> same problems, telnet,ping,http all fine - but the 2 clients
> cant ping each other ??? winipcfg reports routing disabled -
> is this related ???

Both clients are getting their IPs from the e-smith server, and you cannot ping from one client to another?  Check your gateway settings in the TCP/IP control panel...there should not be any entries there, if there are remove them and reboot.  

> any help appreciated..

HTH.

> btw - great product anyway !!

Yep :-)

Cheers,
Paul

Gerald

Re: win2k as a client to e-smith ver 4
« Reply #2 on: January 28, 2001, 08:41:59 PM »
We use W2KP and W9X with e-smith, 3X and 4X. Have never experienced the problems you describe. If the Workstations see the server but not each other it may be because the WS's are not setup to share resources. That usually makes sense because in a server enviroment the WSs use the server for file,printer and Internet sharing.

craig

Re: win2k as a client to e-smith ver 4
« Reply #3 on: January 30, 2001, 12:06:31 AM »
ok, after further investigation :-

ipconfig on the w2k pc gives :-
ip address = 192.168.1.100
subnet= 255.255.255.0
gateway= 192.168.65.1

now im sure the gateway shouldnt be that - there is no .65.x defined anywhere ???
also the winME pc gets the same gateway ?
im sure this is wrong but cant seem to change it anywhere (without getting too deep into red hat (im only a newbie !))

can anyone share their w2k setup as its not like setting up win98 clients - wheres the access control options ? - cause the 2nd setup i have at work (e-smith and win98) works fine when i turn on user acces control (instead of share level)

anyway thanks for suggestions so far but i still cant connect my w2k box !!! :o(

Holger Imbery

Re: win2k as a client to e-smith ver 4
« Reply #4 on: January 31, 2001, 12:25:13 PM »
Hello,

just try this registry-key on your W2k box:

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\lanmanworkstation\parameters]
"enableplaintextpassword"=dword:00000001

--
Holger Imbery

Boris

Re: win2k as a client to e-smith ver 4
« Reply #5 on: January 31, 2001, 01:07:11 PM »
gateway= 192.168.65.1 is on the different network then WS (192.168.1.100) according mask 255.255.255.0.
it should be 192.168.1.1 (assuming that e-smith LAN interface has 192.168.1.1)
Verify DHCP config and gateway setting on e-smith.

Charlie Brady

Re: win2k as a client to e-smith ver 4
« Reply #6 on: January 31, 2001, 06:14:07 PM »
Holger Imbery wrote:

> just try this registry-key on your W2k box:
>
> [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\lanmanworkstation\parameters]
> "enableplaintextpassword"=dword:00000001

No, that's not necessary, e-smith is already equipped to handle encrypted passwords.

Regards

Charlie

Allen Rapini

Re: win2k as a client to e-smith ver 4
« Reply #7 on: February 03, 2001, 03:54:45 AM »
Craig
I came late to this exchange, but after looking thru the responses, I didn't see any suggestions to release and renew your DHCP leases from each machine. Not knowing what you had earlier, for DHCP or not, it would be a first step for me.
win2k - from help (ipconfig /?)
Examples:
ipconfig                                      ... Show information.
ipconfig /all                                 ... Show detailed information
ipconfig /renew                            ... renew all adapaters
ipconfig /renew EL*                      ... renew adapters named EL....
ipconfig /release *ELINK?21*        ... release all matching adapters, eg.
                                                          ELINK-21, myELELINKi21adapter.

WIN9x ( I don't have acces to Me, but I think it's the same syntax)
winipcfg
From DIalog box, choose release all, then renew all
OR
winipcfg /release_all
winipcfg /renew_all

I have found that the default 30 day lease from e-smith didn't suit my "dynamic environment" at work. I have adjusted mine to 3 days instead, which suits me better.

If you get no joy from this, and your sure that no other devices like the ADSL modem, or an additional router are also supplying DHCP services to your network, then you can always use static IP addresses. There are excellent details in the manual, or just ask again with the "Internal" IP address of your e-smith box in the message.

Hope this is not redundant, and helps somewhat.

Allen