NO

Author Topic: WNetOpenEnum error 1208  (Read 9889 times)

czerny

  • Guest
WNetOpenEnum error 1208
« on: September 17, 2014, 04:59:03 PM »
I have compiled an MS example to enumerate network resources.

On my system (XP SP3) the program shows some resources, but fails to list the resources of the container 'WORKGROUP' with error 1208.

Can you please try this with your systems? Are there any network computers listed?

Offline frankie

  • Global Moderator
  • Member
  • *****
  • Posts: 2096
Re: WNetOpenEnum error 1208
« Reply #1 on: September 17, 2014, 05:45:14 PM »
From what I have found around the error code 1208 - extended error - is showed when you have errors on the remote machines (that's why is an 'extended' error?? ).
I can only suggest to check that you have all the rights necessary to access machines and services in the network group you want to access...  :(
P.S. Missing rights can also be due to firewall and antivirus network protections...
« Last Edit: September 17, 2014, 05:48:54 PM by frankie »
It is better to be hated for what you are than to be loved for what you are not. - Andre Gide

aardvajk

  • Guest
Re: WNetOpenEnum error 1208
« Reply #2 on: September 17, 2014, 07:56:41 PM »
When you get 1208 call WNetGetLastError, that'll give you some idea of what the extended error was.

Offline frankie

  • Global Moderator
  • Member
  • *****
  • Posts: 2096
Re: WNetOpenEnum error 1208
« Reply #3 on: September 18, 2014, 05:27:08 PM »
Thanks aardvajk,
I missed this reference.
« Last Edit: September 18, 2014, 05:28:48 PM by frankie »
It is better to be hated for what you are than to be loved for what you are not. - Andre Gide

czerny

  • Guest
Re: WNetOpenEnum error 1208
« Reply #4 on: September 19, 2014, 09:46:21 AM »
With WNetGetLastError I get:

Error 6118 : The list of servers for this workgroup is not currently available

Don't know what this means.

The command 'net view' gives me the same error.
The explorer shows all the shared folders but if I select WORKGROUP (my workgroup name :-)) I get error 6118  too.
« Last Edit: September 19, 2014, 11:23:12 AM by czerny »

Offline frankie

  • Global Moderator
  • Member
  • *****
  • Posts: 2096
Re: WNetOpenEnum error 1208
« Reply #5 on: September 19, 2014, 12:26:24 PM »
It seem a problem with access rights or firewall filtering.
The shared folders have permission for 'everyone'?
Anyway the deny of rights can be due to many causes, i.e. your computer is member of a workgroup and of a domain with different names, the firewall is not set to allow shared resources access, etc.
You may look here, here, or googling around for 'Error 6118 :'.
It is better to be hated for what you are than to be loved for what you are not. - Andre Gide

czerny

  • Guest
Re: WNetOpenEnum error 1208
« Reply #6 on: September 19, 2014, 12:56:31 PM »
I have googled prior to my post and checked the two issues:
I have disabled xp firewall and nis firewall.
I have no domain controller running in this network.
So I don't know, what else could be the problem.

Offline frankie

  • Global Moderator
  • Member
  • *****
  • Posts: 2096
Re: WNetOpenEnum error 1208
« Reply #7 on: September 19, 2014, 01:29:30 PM »
The network issues are always a big problem  :(
Does the reverse works? I mean if you try on other computers also they deny the access?
It could seem stupid, but are you sure that the workgroup name is correctly typed?
The OS's of computers is XP for all or you have mixed types?

P.s. probably you've already checked this, NetBios is active and NetBios service is running?
I have found also this suggestion:
"Have local subnet (i.e 192.168.1.0/255.255.255.0) in the Trusted Zone and allow, Direction Both, UDP, Remote: Trusted Zone ports 137 -139, Local: ports 137-139."
« Last Edit: September 19, 2014, 01:50:13 PM by frankie »
It is better to be hated for what you are than to be loved for what you are not. - Andre Gide

Offline TimoVJL

  • Global Moderator
  • Member
  • *****
  • Posts: 2091
Re: WNetOpenEnum error 1208
« Reply #8 on: September 20, 2014, 08:21:24 AM »
You can first connect to another computer's share from your testing computer and run program again.

In my computer next error from your program is
WnetOpenEnum failed with error 1222
from  Provider: Web Client Network
May the source be with you

czerny

  • Guest
Re: WNetOpenEnum error 1208
« Reply #9 on: September 20, 2014, 10:38:15 AM »
The network issues are always a big problem  :(
Does the reverse works? I mean if you try on other computers also they deny the access?
Same problem!
It could seem stupid, but are you sure that the workgroup name is correctly typed?
The OS's of computers is XP for all or you have mixed types?
Workgroup name is correct. Most computers are XP, but there are also some newer.
P.s. probably you've already checked this, NetBios is active and NetBios service is running?
NetBios is active. Don't know if the service is running. Most look on monday!
I have found also this suggestion:
"Have local subnet (i.e 192.168.1.0/255.255.255.0) in the Trusted Zone and allow, Direction Both, UDP, Remote: Trusted Zone ports 137 -139, Local: ports 137-139."
This should be only a point to look at, if firewall is active, right? But that is not the case.

czerny

  • Guest
Re: WNetOpenEnum error 1208
« Reply #10 on: September 20, 2014, 10:41:39 AM »
You can first connect to another computer's share from your testing computer and run program again.
I will try on monday.
In my computer next error from your program is
WnetOpenEnum failed with error 1222
from  Provider: Web Client Network
What says WNetGetLastError?

czerny

  • Guest
Re: WNetOpenEnum error 1208
« Reply #11 on: September 20, 2014, 11:11:35 AM »
I wonder if there are other apis which could be usefull to check network problems?

Offline frankie

  • Global Moderator
  • Member
  • *****
  • Posts: 2096
Re: WNetOpenEnum error 1208
« Reply #12 on: September 20, 2014, 02:45:11 PM »
If you have the same problem and same errors also using the 'net view' the issue must be the network configuration, the computers doesn't see each other ...  :(
I forget to ask the other computers can access other machines? I mean forget your machine, the other works together?
Check again network address, subnet (is the same subnet? ) and workgroup name...

I wonder if there are other apis which could be usefull to check network problems?
Don't think so, use the old good ping to check if network and subnet are alive, and command line tools to check (like net command), using other software can create more problems because you don't know if there is a network or program problem... :(

P.S. Error 1222 = 'The network is not present or not started.'
« Last Edit: September 20, 2014, 02:51:02 PM by frankie »
It is better to be hated for what you are than to be loved for what you are not. - Andre Gide