OS2 World.Com Forum

Subject  :  Network problems
Author  :  melf mikaelelf@os2ug.se
Date  :  21 Feb, 2007 on 15:54
I have a somewhat unusual problem. I have a home network with 3 XP- computers, two win2000 computers and one eCS2.0beta3 computer. One laptop with win2000 acts as a webserver and a printerserver. All computers except for one XP-computer is connected wireless, via a router. The router deliver IP:s with DHCP, the lease is forever so each computer always have the same IP adress. In the last weeks something strange has happened. I can't print with any of the Windows machines, but I can print with my eCS machine, no problem.(Sometimes though it wont log on, and there doesn't seem to be any logic in why. It always works to log on via ecs sambaclient though) All of the windows machines can connect to the network and I can transfer files between them and between them and my eCS machine. If I connect to the printer server machine through VNC I can print from within the server.

I've checked access permissions and theres no strange with them. I just can't figure out how this has happened. I'm beginning to think if its due to the router, but on the other side I can transfer files...

Summary:
- If I'm logged on with my eCS machine I can always print
- Peridically I cannot log on to my network, win machines always can
- From the windows machines I can never print ("no answer" - message)
- Files can be transfered in any direction, to any computer
- For two months ago everybody could print and I could always log on.

The unusual is that my family have to send documents to me if they want to print them out..OS/2 rules! (but in a bad way I think..)

Any idea is welcome!


/Mikael

Subject  :  Re:Network problems
Author  :  obiwan
Date  :  21 Feb, 2007 on 20:45
I agree this is very strange, I can't tell for sure what is going on from the description, obviously there are too many variables. All I can do is throw out some simple checks.

The first thing I would look for is to open the printer object on the Windows printserver and see if any jobs are stuck in the queue. Windows print jobs always go to the end of the queue, so nothing will print until the first one does. Nothing says OS/2 has to play by Windows' rules, so maybe its jobs jump ahead of the queue.().

If there are print jobs still in the print queue, choose "Cancel all Documents" from the file menu. You might have to then reboot to free them. Also if that is the case, after the reboot be sure "Pause printing" is not selected in the File menu before you try printing again.

Also check the printer queues on the client machines. If they are stuck there, a look at the Events log might give you some clues about the problem.

On second thought, the Events logs on the Windows clients might give some clues even if the queues are clear.

That's the first thing I would look at because it's easy, but with logon problems it could be a deeper problem. If that doesn't work the next thing I would try would be to get rid of all the XP machines and reboot what is left, and see if the trouble goes away. If so, that would be because one of the XP machines made itself the master browser and decided for some reason to clobber access to to the w2k server. Removing File and Printer Sharing from the XP machines would be one possible solution in that case. It is not needed to access the server, only "Client for Microsoft Networks."

To test whether the trouble is with DHCP on the router, just run 'ifconfig lan0' on OS/2 and 'ipconfig' on Windows, and make sure every IP is unique and the network, netmask, and broadcast are the same.

To isolate the network hardware, change to static IP's and connect each system to the server one by one using a crossover cable. A bit time-consuming, but if the problem persists it would tell you right away the problem is software, and if it goes away the problem is the network hardware (once you have also tested that the pair still act up when they are alone on the existing network).

From where I'm sitting, that's as far as I can go without more information. You don't say what sort of authentication you are using.


Subject  :  Re:Network problems
Author  :  tex
Date  :  22 Feb, 2007 on 00:16
Have you tried powering down your server, your router, and your printer server, letting them set for a few minutes and then powering back up?

Subject  :  Re:Network problems
Author  :  jer jksamphere@yahoo.com
Date  :  22 Feb, 2007 on 00:41

melf (21 Feb, 2007 15:54):
I have a somewhat unusual problem. I have a home network with 3 XP- computers, two win2000 computers and one eCS2.0beta3 computer. One laptop with win2000 acts as a webserver and a printerserver. All computers except for one XP-computer is connected wireless, via a router. The router deliver IP:s with DHCP, the lease is forever so each computer always have the same IP adress. In the last weeks something strange has happened. I can't print with any of the Windows machines, but I can print with my eCS machine, no problem.(Sometimes though it wont log on, and there doesn't seem to be any logic in why. It always works to log on via ecs sambaclient though) All of the windows machines can connect to the network and I can transfer files between them and between them and my eCS machine. If I connect to the printer server machine through VNC I can print from within the server.

I've checked access permissions and theres no strange with them. I just can't figure out how this has happened. I'm beginning to think if its due to the router, but on the other side I can transfer files...

Summary:
- If I'm logged on with my eCS machine I can always print
- Peridically I cannot log on to my network, win machines always can
- From the windows machines I can never print ("no answer" - message)
- Files can be transfered in any direction, to any computer
- For two months ago everybody could print and I could always log on.

The unusual is that my family have to send documents to me if they want to print them out..OS/2 rules! (but in a bad way I think..)

Any idea is welcome!



I would recommend replacing all the Windoz machines with eComStation.

Since any idea is welcome

Cheers!


Subject  :  Re:Network problems
Author  :  El Vato
Date  :  22 Feb, 2007 on 02:08

obiwan (21 Feb, 2007 20:49):
[...]. If so, that would be because one of the XP machines made itself the master browser
[...]

He may verify what the master browser is by entering the following at a WinXX command prompt:

nbtstat -a <Melf's machine NetBIOS name>

where the expression within <> (inclusive) is replaced by each individual host NetBIOS name of his machines.

Additionally, even Melf's OS/2 may be attempting to become the master browser (and succeed partially). Melf should take a look at his SMB.CONF file in his OS/2. Open it in a text editor and note the value stated under:

#Browsing election options

os level= <====What is Melf's value here
local master= <====And here


Subject  :  Re:Network problems
Author  :  obiwan
Date  :  22 Feb, 2007 on 04:20
That's a good point, El Vato. I didn't think of that. If OS/2 is the master browser, and XP has issues with the OS/2 port of Samba, that would seem to fit this weirdness. I would check the smb.conf and even turn off master browser election participation completely. Then one of the XP machines would be the master browser, and that should be ok as long as they are on. Removing File and Printer Sharing might be a bad idea since it is used to copy files around.

Subject  :  Re:Network problems
Author  :  melf mikaelelf@os2ug.se
Date  :  22 Feb, 2007 on 12:08
Thanks a lot for all useful suggestions! I will try to go through them step by step. I would love to follow your revolutionary suggestion too, jer, but I think I would be downvoted right away .

---
/Mikael

Subject  :  Re:Network problems
Author  :  melf mikaelelf@os2ug.se
Date  :  22 Feb, 2007 on 16:53

tex (22 Feb, 2007 00:16):
Have you tried powering down your server, your router, and your printer server, letting them set for a few minutes and then powering back up?

Well I had rebooted the router several times without success, but not the printer server. Well, tex, it worked.. . Now printing works from all computers and I really don't know why. I checked the nbtstat -a command on all netbios names and one was called MSBROWSER...is that the master browser?? Well, it doesn't seem to disturb something now. Thanks for your help!

---
/Mikael

Subject  :  Re:Network problems
Author  :  El Vato
Date  :  22 Feb, 2007 on 20:11

melf (22 Feb, 2007 16:53):

tex (22 Feb, 2007 00:16):
Have you tried powering down your server, your router, and your printer server, letting them set for a few minutes and then powering back up?

Well I had rebooted the router several times without success, but not the printer server. Well, tex, it worked.. . Now printing works from all computers and I really don't know why. I checked the nbtstat -a command on all netbios names and one was called MSBROWSER...is that the master browser?? Well, it doesn't seem to disturb something now. Thanks for your help!

Although the proverbial saying goes something like, "If nothing is broken, do not mess with anything", there appears to be a reason for things to occur --at least in the realm of human creations.

In the section of SAMBA's SMB.CONF labeled:

[global]

#Browsing election options

os level = default should be 0 (zero) so that OS/2 will always loose an election for the master browser role. Any other value, especially above 30, will allow OS/2 to participate in the election process --hence possibly introducing problems for the current set up.

The SAMBA team had to include even the MS bugs in order to make their open source implementation fully compatible with the SMB ( CIFS) proprietary offering. Hence, the election for master browser may not necessarily take place at boot up.

local master = set to no --reasons are obvious in your situation

preferred master = If set to yes will immediately force an election for the master browser to take place --and most surely will allow OS/2 to win the role.

domain master = must be set to no if you already have a WinXX Primary Domain Controller (PDC)

Hope the info will shed some light into "the unexplained" and help you anticipate future issues.


Subject  :  Re:Network problems
Author  :  melf mikaelelf@os2ug.se
Date  :  23 Feb, 2007 on 13:17

El Vato (22 Feb, 2007 20:11):
Hope the info will shed some light into "the unexplained" and help you anticipate future issues.

I really appreciate it..but I don't have that file smb.conf. I've searched with pmsearch and it doesn't exist. Is it part of the ordinary network setup?

---
/Mikael


Subject  :  Re:Network problems
Author  :  El Vato
Date  :  23 Feb, 2007 on 19:49

melf (23 Feb, 2007 13:17):

El Vato (22 Feb, 2007 20:11):
Hope the info will shed some light into "the unexplained" and help you anticipate future issues.

I really appreciate it..but I don't have that file smb.conf. I've searched with pmsearch and it doesn't exist. Is it part of the ordinary network setup?


I apologize, Melf, that file is part of the SAMBA package in mainstream platforms.

It appears that the OS/2 client implementation is being done indirectly through a plugin to NetDrive (< http://samba.netlabs.org/en/site/index.xml >) and not as it is currently implemented for other platforms, for instance the Open SuSE Enterprise Desktop, Solaris, etc..

I had initially thought that at least a graphical utility would be provided to allow the user some control over the provided SAMBA client/peer binary files.

Notwithstanding, deviating from the normal implementation of SAMBA, leaves the OS/2 user at a disadvantage (from my perspective) --not being able to manipulate/tune the SMB.CONF.

it effectively ties behind the hands of the user --leaving him/her at the mercy of the provider of the SAMBA binaries.

Best regards.


Subject  :  Re:Network problems
Author  :  obiwan
Date  :  24 Feb, 2007 on 03:40
Oops, I also made reference, in my ignorance, to the smb.conf file, so I also must apologize.

A Samba client should not normally try to be a master browser. That is the role of a server or peer, and would only be done by a daemon running in the background.

In any case, messing with these settings will only be necessary if (A) Your eComstation system is (or anything on the network thinks it is) the master browser, and (B) there really is a bug in the OS/2 port of Samba that keeps it from working correctly.

Neither is by any means certain.

The fact that rebooting fixed it would make me just disregard it as typical Windows issues unless it starts recurring often enough to bother you. Then determine which system on the network is causing it, and if it turns out to be your eCS system, maybe some other Samba/2 users can help.


Powered by UltraBoard 2000 <www.ub2k.com>