Network addresses to my PC's

I have 2 wireless PC's and a Mac 5; each are connected to my Airport Express. The Mac works terrific, but I am unable to connect either PC to Airport Express. Each receives an excellent network signal from airport, but I get an error message indicating "...the network did not assign a network address to your computer." What am I doing wrong?
Be gentle, and Thanks!!
GPNP

Similar Messages

PL/SQL Network Address Type Functions

Hi,
I'm wondering if anyone knows of a PL/SQL package(s) that provides similar capabilities as the following postgreSQL network address type functions:
http://www.sql.org/sql-database/postgresql/manual/functions-net.html
I don't see anything in the standard Oracle 10g packages, so I'm wondering if anyone else has dealt with this problem and posted the package.
Thanks,
- Greg.

I think the easiest way of getting some of this functionality would be to write a PL/SQL wrapper to a Java Stored Procedure that implements calls to the Java InetAddress class. It doesn't haven't the full set of operators but I'm not sure what 'less than' actually means in the context of an IP address . If you really need them you could always extend the InetAddress class to implement such tests.
Cheers, APC

Windows XP failing to acquire network address whether wired or wireless

Hi guys,
I initially asked this question elsewhere because it was happening in OSX as well, though now that the OSX side of things has been fixed it is purely a Windows XP problem, and is a different problem to the one in Mac OSX.
The problem seems simple enough, in that Windows XP just refuses to acquire a network address when connecting to the internet whether wired or wirelessly. I spent the best part of 7 hours on this on Monday, and after trawling through countless web pages I seemed to establish that there was an error with the AFD Driver (which, as I understand, is one of three required for the DHCP Client service to run). I was on the verge of probably doing something monumentally stupid and trying to repair/replace that driver when in a moment of genius (which should have arrived significantly sooner in the day) I asked my fiancee when the last time was that she could remember the internet working properly. She said it was the day before just after she agreed to install SP3, but the installation failed. So I used System Restore and rolled the system back to before that point, et voila. Everything was fine.
Not appreciating the path taken to fix her iMac, my fiancee then tried to install SP3 again and the same problem reoccurred. Another System Restore fixed it. The problem now is that on startup Windows XP seems to revert back to the same state, and will refuse to acquire an IP address. A System Restore back to the same time will fix it. However, whilst this takes little longer than an actual startup, I was wondering whether or not anybody had any bright ideas for a permanent fix to this problem.
All ideas, solutions and pearls of wisdom welcomes with open arms.

Crazy Jamie wrote:
Hi guys,
I initially asked this question elsewhere because it was happening in OSX as well, though now that the OSX side of things has been fixed it is purely a Windows XP problem, and is a different problem to the one in Mac OSX.
The problem seems simple enough, in that Windows XP just refuses to acquire a network address when connecting to the internet whether wired or wirelessly. I spent the best part of 7 hours on this on Monday, and after trawling through countless web pages I seemed to establish that there was an error with the AFD Driver (which, as I understand, is one of three required for the DHCP Client service to run). I was on the verge of probably doing something monumentally stupid and trying to repair/replace that driver when in a moment of genius (which should have arrived significantly sooner in the day) I asked my fiancee when the last time was that she could remember the internet working properly. She said it was the day before just after she agreed to install SP3, but the installation failed. So I used System Restore and rolled the system back to before that point, et voila. Everything was fine.
Not appreciating the path taken to fix her iMac, my fiancee then tried to install SP3 again and the same problem reoccurred. Another System Restore fixed it. The problem now is that on startup Windows XP seems to revert back to the same state, and will refuse to acquire an IP address. A System Restore back to the same time will fix it. However, whilst this takes little longer than an actual startup, I was wondering whether or not anybody had any bright ideas for a permanent fix to this problem.
All ideas, solutions and pearls of wisdom welcomes with open arms.
Try using a system that is able to connect to the internet in Windows. Then go to http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2FCDE6CE-B5FB-4488-8 C50-FE22559D164E and then download SP3 to the hard drive of that system. Then using the CD/DVD burning of your choice that you have for Windows burn the disc image file to CD/DVD and then insert it to the system that has the issue and upgrade it to SP3 that way.
I used to use Windows update to get service pack, but one time it did not download and install correctly on an HP system. Since then I have went to Microsoft and downloaded the Service Pack and when it said that it installed successfully I deleted the file I downloaded. I never had issues when I get them and install them that way. The only Service Pack I had issues with was Service Pack 1 for Windows 7. I downloaded it from Microsoft to the hard drive and after it said it was installed successfully I deleted the file. I used it for a while then I shut the system completely down. Then when I booted into Windows I went to put in my password and nothing happened. I tried moving the mouse nothing happened. Then I did a hard reset, booted into Mac OS X, used Boot Cap Assistant, removed the partition, downgraded to Windows XP 32-bit and now miss all the features that come with 64-bit Operating Systems. I am now able to use 2.5GB of RAM out of the 8GB that is in my system. I thought with Windows 32-bit that 4GB what the most that could be used.

Connecting over a network address

I have just purchased a copy of apple remote desktop version 3 as I am going away to university week after next and need to be able to access my home computer to help my parents with any problems that they have. The problem is, I can access their computer (intel imac) from my laptop (mbp) while on my home network but when I go to my aunts house to try and connect it doesn't work.
I know that I have to use the network address of the internet to login but that doesn't seem to work either.
My public internet IP is: 83.xx.xx.xxx and then the imac is connected to a router with ip 192.168.1.71 .
Can anyone please tell me what to type into remote desktop to connect to this computer.
Many thanks.

Here is a tutorial.
I'm tired of hearing the same freakin' questions.
http://www.starkpr.com/ard.htm
I welcome any comments to make this tutorial more user-friendly.
Thanks,
Kevin Nichols
[email protected]

WRT54G - limited or no connectivity - stalls at "aquiring network address"

Ok, so I decided to move my modem and router to a different location in the house and unplugged and re-set everything. I went through the basic setup and finally got to the point where I can get internet when the pc is wired to the router. Wireless, the pc is picking up the network fine but when it gets to "aquiring network address" it just stalls and eventually I get the message that I have limited or no connectivity. When I righ click on the network connection icon and click "repair" connection it cannot verify network address. My xbox 360 is also picking up the network but fine but will not connect. Everything was working fine beforehand but I cannot for the life of me figure out what setting needs adjustment.
Any suggestions?
Thanks

FWIW, this is similar to a problem I just posted. I got around the problem by selecting properties on the connection, and changing the settings under 'Internet Protocol (TCP/IP) Properties' to use a specific IP address.
These settings worked for me:
IP 192.168.1.101
Subnet mask 255.255.255.0
Default Gateway 192.168.1.1
Preferred DNS server 192.168.1.1
Alternate DNS server 192.168.1.2
I haven't yet found a solution to allow me to go back to obtaining an IP address automatically. Did you?
Mike

Wireless PC wont connect---wont acquire network address

Your Network Magic Version installed: 5.5.5195
The type of connection to the Internet : ADSL2
The Brand of Modem and its Model Number the router is connected to.Linksys ADSL WAG120N
The Method of connection your problem computer has to the Router: Wireless.
The Connection in use on the problem computer: TP-Link TL-WN350GD
Operating system and version and Service Pack Level, XP Service pack 3
Software Firewall in use: windows
Also if any Anti-Virus Program or Spyware Program is actively protecting your computer. Iobit Security and Avast
I have a problem, ever since I had to do a hard reset of my pc. It works on wireless and the signal is strong. But it cannot acquire the network address from the router no matter what I do.
Can anyone help ?

Firstly, you must know your router's wireless settings. click on these links to learn how:
http://www6.nohold.net/Cisco2/ukp.aspx?vw=1&articleid=3698
http://www6.nohold.net/Cisco2/ukp.aspx?vw=1&articleid=22046
After getting your router's wireless settings, get your Kindle and follow the steps on this link:
http://askville.amazon.com/Kindle-connect-wireless-router-passwords-work-Help/AnswerViewer.do?reques...

WRT54G Wireless Router Will Not Assign a Network Address

A Linksys WRT54G router will not assign a network address when I access the router using a Linksys WPC600N wireless card. I have the same problem accessing the router with a TRENDnet TEW-621PC wireless adapter. Both wireless adapters are assigned network addresses when I use other wireless routers. Also, I have no problems being assigned a network address when I access the WRT54G router in question using an old 2WIRE 802.11b wireless card.
I have tried "Repairing" the connection, I have used ipconfig to "release" and "renew" the connection. However, each attempt fails to have a DHCP address assigned.
I am a visitor at the work location with the connection problem, the router works for others without any issues.
Thanks

Well in such case .... you can try few settings on the wireless adapter ....
If you are using WLAN monitor .....
Click start >> All programs >> Linksys wireless monitor >> Click on "Profile" >> Delete all profiles >> Click "New" >> Type in the wireless network name >> Click next >> Configure the rest of the wireless settings same as in the router ...
At last point it shows .... all the configuration settings ...reconfirm that >> Click on connect ot a network & reboot the computer ...
After reboot see if it shows connected or not....
You can also use Static Ip in the configuration ....

Can i change the wifi card MAC address in windows 10 /configure/Advanced „Network Address" funktion works?

Many users complained some wifi cards missing the
/configure/Advanced „Network Address” funktion.Without this function
does not work normal MAC adresses which begin for example
„00”.There are many
forums people write about (indignantly)
the problem.
picture here
of what
I mean:
stewx.cba.pl/extend-your-free-wifi-by-spoofing-your-mac-address/
older post more links:
social.technet.microsoft.com/Forums/windows/en-US/8f33667e-ba25-442c-a49b-a3aec79b6cc9/windows-781-can-not-change-the-mac-address-on-wifi-and-cannot-load-login-page-in-public-hotspot?forum=w8itpronetworking
I'm curious about the Windows 10 users
experience with different
wifi cards.
This function working perfectly, all linux platform,Mac,already in android,the old windows XP,windows 2000,
it's a basicthing.This problem affects some reason only are newer Windows platforms and directly the wifi option.

well....it doesn't matter whether the MAC add is 00-14-BF-93-D2-66 or 00:14:BF:932:65 or any other format .. the most important thing is the hex decimal numbers are the same ... so not worry about it...

Message "Network address default of computer not mainatined" in CV01N.

Gurus,
I just created content repository in OAC0 and linked it to storage type in OACT. Now when I try to checkin the original document in CV01N. Instead of asking me for storage type, its displaying message saying that "Network address default of your computer is not maintained".
Regards,
Rajesh.

HI Rajesh,
Please do the require setting in DC20 define data carrier.
in dc20 : click on define data carrier for server frontend computer. define data carrier there,.slect it and click on the folder Identify frontend computers. Make the setting default there.
Once you make the defualt setting, that error will get resolved.
thanks
regards,
nitin

ACS Database Replication over VPN with overlapping Network Addresses

We currently have two co-locations each situated in different provinces. We have two ACS servers which we want to deploy at each co-location. All our network equipments are behind PIX/ASA devices. Getting them to replicate over the VPN should be easy but in our case we have overlapping Network Addresses at both ends of the tunnels.
As per Cisco data does not transit a NAT device when the two Cisco Secure ACS servers communicate and a successful database replication can occur only if the secondary ACS server perceives no change in the IP header or content of the data it receives. So that means we will not be able to Implement NAT to achiever this.
Has any one of you faced this problem of replicating ACS Database over the VPN with overlapping Network Addresses and was anyone able to successfully solve this issue using a work around ?
All provided info and comments are greatly appreciated.

I can help with the 3005 setup if you decide to go that route.
You will need to add 2 network list entries under Configuration>Policy Management>Traffic Management>Network Lists.
You will need to configure a local and remote address. The local will be one of the public ip's for the site.(Provided by your ISP)The remote will be the device you are connecting to on the other end.
You will also need to add a Nat Lan to Lan rule under Configuration>Policy Management>Traffic Management>Nat>Lan to Lan.
Use a static Nat type. The rest will look similar to my example.
Source(Local address)Translated(Public Ip Address used in the network local list)Remote(Ip address of the device on the other end)
Now just create an Ipsec lan to lan tunnel. You will need to agree with the ISP on des type and auth type. Use you local and remote networks you created earlier.

The server network address can not be reached or does not exist

Hi all
    When i am trying to configure Mirroring .i am getting the below error.
The server network address "TCP://RDEEPA:5022" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)
. TCP/IP and Name pipe connection is enabled in both principle and mirror server configuration.
I post the complete error message below ,which is in red
TITLE: Database Properties
An error occurred while starting mirroring.
ADDITIONAL INFORMATION:
Alter failed for Database 'success'. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Alter+Database&LinkId=20476
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
The server network address "TCP://RDEEPA:5022" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=1418&LinkId=20476
BUTTONS:
OK

Hi,
I have the same problem. However beginning over and over again and using other ports did not solve this unfortunately.
Here is the SQL I used to setup the mirroring.
* Principal DB
CREATE ENDPOINT [MirroringEndpoint]
    AUTHORIZATION [DOMAIN\administrator]
    STATE=STARTED
    AS TCP (LISTENER_PORT = 5022, LISTENER_IP = ALL)
    FOR DATA_MIRRORING (ROLE = PARTNER, AUTHENTICATION = WINDOWS NEGOTIATE
, ENCRYPTION = REQUIRED ALGORITHM RC4)
BACKUP DATABASE TEST
    TO DISK = 'C:\full-backup.bak'
    WITH FORMAT
BACKUP LOG TEST
    TO DISK = 'C:\log.bak'
ALTER DATABASE TEST SET PARTNER ='tcp://sql2.domain.local:5022';
* Mirroring DB
CREATE ENDPOINT [MirroringEndpoint]
    AUTHORIZATION [DOMAIN\administrator]
    STATE=STARTED
    AS TCP (LISTENER_PORT = 5022, LISTENER_IP = ALL)
    FOR DATA_MIRRORING (ROLE = PARTNER, AUTHENTICATION = WINDOWS NEGOTIATE
, ENCRYPTION = REQUIRED ALGORITHM RC4)
RESTORE DATABASE TEST
    FROM DISK = 'C:\full-backup.bak'
    WITH NORECOVERY
RESTORE LOG TEST
    FROM DISK = 'C:\log.bak'
    WITH FILE=1, NORECOVERY
ALTER DATABASE TEST SET PARTNER ='tcp://sql1.domain.local:5022';
The last statement on the principal server gives me the following error :
Msg 1418, Level 16, State 1, Line 1
The server network address "tcp://sql2.domain.local:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.
From the principal server I'm able to ping the mirror server and can establish a telnet connection. When the statement gets executed even netstat gives me the following output :
TCP    0.0.0.0:5022           0.0.0.0:0              LISTENING       1244 [sqlservr.exe]
TCP    10.1.1.140:5022       10.1.1.110:1223       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1226       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1216       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1218       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1225       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1222       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1221       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1224       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1219       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1220       TIME_WAIT       0
Is it normal so many ports get opened?
Any help would be greatly appreciated (as this drives me crazy :-( )
Found the problem eventually. The mirroring ran as the NT_AUTORITY user instead of DOMAIN\administrator.

LDAP Lookup / Network Address sometimes populates with TCP

Our development team has configured our local intranet to do LDAP searches against our tree, thus eliminating the need for users to login. They're doing an IP lookup and then retrieving the user name. What happens very rarely is the the "Network address" field under the Environment tab within ConsoleOne will display "TCP:" followed by the users IP address.
When this hapens (it's rare), the lookup fails. The typical results display "IP:" followed by the users IP address. This always works. Here's the code that is doing the LDAP query:
$sLDAPQuery = ldap_search($sLDAPConn, "o=XYZ", "(networkaddress=1#$sIPAddress)")
Where "(networkaddress=1#$sIPAddress)" is the search string, $sIPAddress being the HEX value of the IP.
My question is, is there a way for me to eliminate the return value of TCP? Does anyone have any other pointers or potential workarounds for this? Like something that would still allow the IP lookup to succeed when TCP is presented instead of IP?
Thanks for your help,
Ryan

ryan r sd 2 wrote:
> My question is, is there a way for me to eliminate the return value of
> TCP? Does anyone have any other pointers or potential workarounds for
> this? Like something that would still allow the IP lookup to succeed
> when TCP is presented instead of IP?
There are different types of network addresses (as defined by that first
number in the returned string). So, your dev folks need to decode
according to the type of address that is being returned, and not just
assume its always IP (ie 1).
Peter
eDirectory Rules!
http://www.DreamLAN.com

BRIDGE process is not able to establish network address

Hi,
I am trying to setup a network application, the operating system is SunOS 5.8 , the listeners have been brought up, while booting the master it gives the error could not establish network address, check device and address. the network section of ubb is as below :
NADDR="//10.188.42.96:58640"
BRIDGE="/dev/tcp"
NLSADDR="//10.188.42.96:58641"
the ulog shows following entries....
075149.gws210d113!DBBL.15079.1.0: CMDTUX_CAT:4350: INFO: BBL started on d2d_3 - Release 7000
075149.gws210d113!BBL.15084.1.0: 07-15-2010: Tuxedo Version 7.1, 32-bit, Patch Level 350
075149.gws210d113!BBL.15084.1.0: LIBTUX_CAT:262: INFO: Standard main starting
075149.gws210d113!BRIDGE.15088.1.0: 07-15-2010: Tuxedo Version 7.1, 32-bit
075149.gws210d113!BRIDGE.15088.1.0: LIBTUX_CAT:262: INFO: Standard main starting
075204.gws210d113!BRIDGE.15088.1.0: CMDTUX_CAT:4400: INFO: Waiting up to 75 seconds for port to clear
075219.gws210d113!BRIDGE.15088.1.0: CMDTUX_CAT:4400: INFO: Waiting up to 60 seconds for port to clear
075234.gws210d113!BRIDGE.15088.1.0: CMDTUX_CAT:4400: INFO: Waiting up to 45 seconds for port to clear
075249.gws210d113!BRIDGE.15088.1.0: CMDTUX_CAT:4400: INFO: Waiting up to 30 seconds for port to clear
075304.gws210d113!BRIDGE.15088.1.0: CMDTUX_CAT:4400: INFO: Waiting up to 15 seconds for port to clear
075319.gws210d113!BRIDGE.15088.1.0: CMDTUX_CAT:4400: INFO: Waiting up to 0 seconds for port to clear
075320.gws210d113!BRIDGE.15088.1.0: CMDTUX_CAT:4340: ERROR: Could not establish network address //10.188.42.96:58640 - check device and address
075320.gws210d113!BRIDGE.15088.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
075320.gws210d113!BRIDGE.15088.1.0: CMDTUX_CAT:494: INFO: BRIDGE exiting system
Thanks.
Edited by: user12831907 on Jul 15, 2010 12:10 AM

Hi,
the ports seem to be clear, lsof gives following ouput :
(gws210d113)/opt/tuxedo> lsof -i :58640
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
tlisten 19585 tuxedo 3u IPv4 0x3002fbff228 0t0 TCP gws210d113:58640 (LISTEN)
(gws210d113)/opt/tuxedo> lsof -i :58641
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
tlisten 19592 tuxedo 3u IPv4 0x3003ddaec70 0t0 TCP gws210d113:58641 (LISTEN)
I am starting tlisten as non-root user and as follows :
tlisten -l //10.188.42.96:58640
tlisten -l //10.188.42.96:58641
The following are the logs from master machine :
021524.gws210d113!DBBL.19074.1.0: 07-24-2010: Tuxedo Version 7.1, 32-bit
021524.gws210d113!DBBL.19074.1.0: LIBTUX_CAT:262: INFO: Standard main starting
021526.gws210d113!DBBL.19074.1.0: CMDTUX_CAT:4350: INFO: BBL started on d2d_3 - Release 7000
021526.gws210d113!BBL.19079.1.0: 07-24-2010: Tuxedo Version 7.1, 32-bit, Patch Level 350
021526.gws210d113!BBL.19079.1.0: LIBTUX_CAT:262: INFO: Standard main starting
021527.gws210d113!BRIDGE.19080.1.0: 07-24-2010: Tuxedo Version 7.1, 32-bit
021527.gws210d113!BRIDGE.19080.1.0: LIBTUX_CAT:262: INFO: Standard main starting
021541.gws210d113!BRIDGE.19080.1.0: CMDTUX_CAT:4400: INFO: Waiting up to 75 seconds for port to clear
021556.gws210d113!BRIDGE.19080.1.0: CMDTUX_CAT:4400: INFO: Waiting up to 60 seconds for port to clear
021611.gws210d113!BRIDGE.19080.1.0: CMDTUX_CAT:4400: INFO: Waiting up to 45 seconds for port to clear
021626.gws210d113!BRIDGE.19080.1.0: CMDTUX_CAT:4400: INFO: Waiting up to 30 seconds for port to clear
021642.gws210d113!BRIDGE.19080.1.0: CMDTUX_CAT:4400: INFO: Waiting up to 15 seconds for port to clear
021657.gws210d113!BRIDGE.19080.1.0: CMDTUX_CAT:4400: INFO: Waiting up to 0 seconds for port to clear
021658.gws210d113!BRIDGE.19080.1.0: CMDTUX_CAT:4340: ERROR: Could not establish network address //gws210d113:58640 - check device and address
021658.gws210d113!BRIDGE.19080.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
021658.gws210d113!BRIDGE.19080.1.0: CMDTUX_CAT:494: INFO: BRIDGE exiting system
021701.gws210d113!tmboot.19064.1.-2: 07-24-2010: Tuxedo Version 7.1, 32-bit
021701.gws210d113!tmboot.19064.1.-2: CMDTUX_CAT:825: ERROR: Process BSBRIDGE at d2d_3_fallback failed with /T tperrno (TPENOENT - no entry found)
021703.gws210d113!tmboot.19064.1.-2: CMDTUX_CAT:825: ERROR: Process BBL at d2d_3_fallback failed with /T tperrno (TPENOENT - no entry found)
021703.gws210d113!tmboot.19064.1.-2: WARN: No BBL available on site d2d_3_fallback.
Will not attempt to boot server processes on that site.
Also, I think that the problem occurs when master is trying to boot the services on slave machine, the following is the ULOG entries logged in slave machine :
022324.apt3s009z1!BSBRIDGE.14223.1.0: 07-25-2010: Tuxedo Version 7.1
022324.apt3s009z1!BSBRIDGE.14223.1.0: LIBTUX_CAT:262: INFO: Standard main starting
022324.apt3s009z1!BSBRIDGE.14223.1.0: CMDTUX_CAT:1373: ERROR: Abnormal disconnect from gws210d113
022324.apt3s009z1!BSBRIDGE.14223.1.0: CMDTUX_CAT:473: ERROR: Could not find DBBL
022324.apt3s009z1!BSBRIDGE.14223.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
022326.apt3s009z1!BBL.14224.1.0: 07-25-2010: Tuxedo Version 7.1
022326.apt3s009z1!BBL.14224.1.0: LIBTUX_CAT:503: ERROR: Cannot find DBBL
022326.apt3s009z1!BBL.14224.1.0: LIBTUX_CAT:248: ERROR: System init function failed, Uunixerr =
022326.apt3s009z1!BBL.14224.1.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
Also, it might help to know that on Slave machine, the connection is established on the listener port :
10.80.156.13.58502 10.188.42.96.64462 131768 0 49248 0 ESTABLISHED
10.80.156.13.58502 *.* 0 0 49152 0 LISTEN
Thanks and Regards.
Edited by: vis_punch on Jul 24, 2010 2:53 AM

Router not assigning network address

I have the Verizon FIOS Actiontec router. The wired connection is great but the wireless connection is nothing but trouble. My wireless computers see the wireless network and say they "connect" to it, but then they have a problem getting a "network address" from the router - about half the time I get no network address and so can't access my network or the internet. The actual message is "Getting network address" - this stays on for a minute or two and then I get the message that I have no or limited connectivity and I can't connect - even though the network signal I get is "very strong". I try rebooting my wireless computers, re-booting my router and sometimes it connects and sometimes it doesn't - there is no pattern. If I leave my computer alone it will re-try the connection every once and a while and may eventually connect - usually if I wait long enough, but this may be hours or a day latter before it will eventually connect. It is not a password issue because about half the time I have no problem at all, the other half of the time it may be hours or a day before I can connect.
Verizon sent me a new router and I have the very same problem. I never had this problem when I used my own wireless router with DSL (before FIOS). The same problem is true for both a desktop with a wireless connection and a netbook I have (all systems are running xp). I even re-set up my old wireless router in serial with my Verizon router and both computers picked up and connected to the old router right away - I even got internet using this serial set up - but I have other problems with this set up so it really is not a solution - but it was useful in letting me know it is not something with my wireless computers. I even uninstalled and reinstalled the wireless adapter to my desktop and that did not help.
Has anyone else had this problem? Why is this happening? What can I do to fix this? Please help.

How to improve wireless networking on Verizon MI424WR
follow this guide, but you're best bet is to change the wireless channel. that is a relatively painless procedure. There are only three channels in N.America that are useable. Those are wireless channel 1, wireless channel 6 and wireless channel 11.
you probably have some heavy interference on whichever wireless channel you are currently on. One of the three listed should provide good results for you, but you'll want to cycle through each of them to find which channel is the best.
Log into your router
http://192.168.1.1
Default user name is 'admin'
Default Password is 'password1' other variants are 'password', or 'admin'
Once you're logged into the router, stay in the first column and look for change wireless settings.
When you click on that your wireless settings will come up, and you'll see the channels as your number 3 option. simply use the drop down list to choose channel 1, place a check mark where it says something to the effect of "keep these changes even after a reboot" and then hit apply.
wait for it to lock in, try to reconnect to your wireless and try it out for however long it takes to drop off again. if it does not drop off then you are good, if it does, then change it from 1 to 6, and then if that does not work change it to 11.
also take a quick look at the actiontec link at the top. It's very basic but it gives some food for though with regard to things that potentially can interfere with that wireless transmission.

Network Address of Subscriber Objects

When I look at a Distribution in Imanager's Tiered Distribution View,
Some of my Subscribers show up with the IP address.
I have gone into the Object in NDS and checked under the Other tab and
looked at the Network address. On some Subscribers I have a TYPE_13 that
has the DNS and some that have the IP in the TYPE_13. On other
Subscribers I have both a TYPE_13 field and an IP field.
My question is
1. Is there any issue with changing the TYPE_13 field that has the IP
address to the DNS name as it should be.
2. Is there any issue with leaving the extra field IP in place.
3. does adding the field IP to my subscribers get me anything ?

Ron,
I have made the change to the entry on the Subscriber objects under the
other tab/network Address/type_13 and changed the entry from the IP
address to the DNS name.
This has resolved the issue of the IP address of the subscriber showing
in iManager rather than the Subscribers name and also looks like it may
of resolved a certificate issue we were having with these subscribers as
well.
Thanks for your help as always
Groten
Jules ;-))
> It should just use the DNS entry
>
> Ron
>
> <[email protected]> wrote in message
> news:%[email protected]...
> > Yes some of our links were goign up and down at the time we were
running
> > some our initial installs, and we have had a few Certificate issues
with
> > the Subscribers that have the IP address in the TYPE_13 address field.
> > I will change the information in the TYPE_13 field back to DNS name
entry
> > so that it matches the rest of the subscribers.
> > I was also wondering about the IP address field as I have this on some
> > subscribers as well. Should I add this to all of the subscribers ?
> > Would this help the subscriber if we have a DNS issue ?
> >
> >> Might be that there where some problems with the reversed lookup
during
> > the
> >> install, this is why sometimes you see the IP address. Shouldn't be a
> >> problem in a pure NetWare environment, if you have certificate
problems
> > this
> >> is one thing to look at.
> >>
> >> Ron
> >>
> >> <[email protected]> wrote in message
> >> news:[email protected]...
> >> > When I look at a Distribution in Imanager's Tiered Distribution
View,
> >> > Some of my Subscribers show up with the IP address.
> >> > I have gone into the Object in NDS and checked under the Other tab
and
> >> > looked at the Network address. On some Subscribers I have a TYPE_13
> > that
> >> > has the DNS and some that have the IP in the TYPE_13. On other
> >> > Subscribers I have both a TYPE_13 field and an IP field.
> >> > My question is
> >> > 1. Is there any issue with changing the TYPE_13 field that has the
IP
> >> > address to the DNS name as it should be.
> >> > 2. Is there any issue with leaving the extra field IP in place.
> >> > 3. does adding the field IP to my subscribers get me anything ?
> >>
> >>
> >
>
>

Network addresses to my PC's

Similar Messages

Maybe you are looking for