VLAN network address issue

we are having 6500 series switch.we are able to telnet the switch with network address as well as with interface address...several vlan are created in this switch.
now my question is that how can we telnet it with network address...
help me out plz as soon as possible

you cannot telnet to a network address. for example, i'm guessing you have 24 bit subnetMask which would make your network address: 192.168.16.0.
you cannot telnet to 192.168.16.0 BECAUSE it is a network address and not a host able to respond to a telnet request.
your detail still seems a little fuzzy though...didn't you say:
"network address is 192.168.16.32...."
"now i can telnet the switch with 192.168.16.32...."
and then say:
"how can i telnet with network address???"

Similar Messages

SF300 VLAN IP Address Issues

I have purchased 3 SF300-48 switches to work with my Aironet AP1131AG wireless APs. I have now switched from 1 VLAN for everything to having a Guest_Wireless VLAN 200 as well as the default VLAN 1 for my Corporate_Network. The issue that I am having is that any client on my default VLAN is receiving an IP address from the Windows DHCP server without issue, but when you connect to the Guest VLAN you cannot get an IP address.
So, I also have a Cisco 3560G Router (Default Gateway) that has the same Aironet AP1131AG AP connected to it with the same config files as the other APs and it is working perfectly. I can connect to either wireless SSID (Corp Vlan1 or Guest Vlan 200) and get the proper IP address from the DHCP server.
I attached the diagram of the network below and was looking for help in configuring the SF300 to allow the IP address to be obtained on the Vlan 200 subnet. I also tried connecting my laptop directly into the SF300 and setting the port to access Vlan 200 and I can still not get an IP address.
Any help would be appreciated...
Aaron

Thank you for taking the time to help me Tom, yes the 3560G has its trunks set to dot11q encap and native valn of 1. The native vlan on the SF300 is set to vlan 1 but I didn't tag vlan 200 to the trunk. I was thinking that if not listed it would pass any vlan info across a trunk and when you tagged it would only limit passing vlan info of the vlans that you specified only.
I will definately give this a try and update this thread.
Thanks,
Aaron

4500 VLAN MAC address issue

We are facing an issue with our 4500 switch. It is using the same MAC address for all VLAN interfaces, which is causing a problem with our service provider.
Is there a way to disable this?
Thanks,
Fabián

Fabián,
I'm afraid that's not possible on a 4500:
Supported Platforms for Unique MAC Address Configuration on VLAN or L3 Interfaces for Catalyst Switches
Best regards
Rolf

Having issues with WRT54GS router acquiring network address after wireless connection.

I've been experiencing problems acquiring a network address after making a wireless connection with the WRT54GS wireless router. I have a Comcast cable modem connected to the internet port of the router and after configuring the SSID and the 64 bit WEP key, I can connect to my router's SSID, but since I can't get an IP address, never connect to the Internet. I've already cloned the laptop's mac address to no avail. Even after configuring a static IP address, subnet mask and default gateway, still cannot connect. I can Ping and Traceroute from the router but not the PC. I can ping localhost and host IP address from the laptop but not the default gateway. Any suggestions would be appreciated. Thanks, SJ

Connect the computer to the router with the Ethernet cable.
Try to access the internet when you connect the computer to the router with the Ethernet cable.
Open the setup page of the router and go to Status page. Check the Internet IP address on the status page of the router.
If you are able to access the Internet with the Wired connection to the router then try to create a new wireless network on your router.
Open the setup page of the router and go to Wireless tab. Change the wireless network name SSID and change the channel to 11. Save the settings. Go to Wireless security sub tab and check the wireless security settings. Click on Wireless MAC filter sub tab and make sure that it is disabled. Click on Advanced wireless settings sub tab. Change the Beacon Interval to 75, RTS and fragmentation threshold to 2304. Save the settings.
Try to connect to the new wireless network and see if that works.
How many wired and wireless computers do you have in the network?

Server 2012 R2 Network Teaming Issues After Adding WOW64 Feature

Recently I have had a specific issue adding the WOW64 feature to an active Server 2012 R2 server in core mode (no management). The server had two active virtual machines. A server 2008 R2 in version 1 mode and a 2012 R2 in version 2.
All were up2date as of April 10 2015. This was a domain connected core with domain connected virtual machines. We are the domain administrator.
After using powershell to install WOW64 and issuing a restart we lost all external network connectivity to the server once the server came back up. From the console we could ping 127.0.0.1 and all the network addresses of each VM but not the
default gateway or any address on the local network. We tried several resolutions including disabling all firewall rules and assigning a known VLAN but nothing worked. Something went completely haywire within Windows 2012 R2 and network teaming
and the virtual switch that supplies the VM's with communication.
What we had to do was remove one of the physical network adapters from the team using powershell from the core console. We then assigned an address to the nic and whallah we were able to remotely communicate to the server again but the problem
still remained with communicating to the team.
After hours of trials we finally stumbled on a solution deleting the hyper-v virtual switch though a remote console, then the team through powershell. This of course broke all the hyper-v VM's. We said f'it and rebooted.
This is the magical combination apparently
We then recreated the team using the remote management GRAPHICAL widget using every physical EXCEPT the nic we were communicating to.   Then we recreated the hyper-v virtual switch remotely again with the GRAPHICAL widget and assigned
it an address using the command line sconfig tool.   We then went into the GRAPHICAL hyper-v manager and assigned all VM's to the new virtual switch. WOW everything works again
Let me just say here in this post that the lack of graphical management in CORE mode is a complete nightmare. The fact we have to use some graphical tools to perform certain tasks and the command line for others is just silly. The sconfig.exe
tool should have built-in teaming commands as inexperienced remote administrators are very difficult to work with over the phone trying to explain spelling of the upper/lowercase commands.
This post is more informative than really asking a specific question but if I were to ask one I'd ask, why did installing the WOW64 feature and rebooting break the external communication of the team and the virtual switch?

Hi gettnmorebetter,
Could you try to confirm whether you have in the following situation, if you do not found the related symptom please try to install the latest update then monitor the issue
again.
Event ID 106 when a Hyper-V virtual switch is bound to an LBFO team
https://support.microsoft.com/en-us/kb/2974384
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Basic tiger server printing to network printer issues - HELP :)

Hi everyone, Im after some help as im running out of ideas, here is my basic setup: (sorry i have rambled on a bit
current 192.168.0.x network that has ADSL, PC's HP Laserjet 5Si network printer.
Connected to that is my Tiger server with 2 lan ports, one is connected to that network and the other connected to a switch where I run all my macs - the server is a basic file and software update server.
macs connected to the server get a 192.168.2.x address and can access the internet and each other etc - all is happy.
now - I had my personal macbook pro connected directly to the first network to access the printer, works fine and fairly quickly but was unable to access the server (i imagine because the server thinks i was from the big bad internet from the .0.x range
once i connected to the other network served by the mac server i could access all the files fine but printing would not work, so i thought I would have the server access the printer as it has access to both networks and just share it to the local macs.
well when i add it and put in the 192.168.0.71 address it connects and loads the GIMP HP5si driver, but when it tried to print it takes up to 5 mins to show that its finished, but only sometimes does the printer actually fire up, and the times it did it never printed the whole page...
The only thing i can think of is that the server is trying to print to the .0.x address'ed printer but using the .2.x address range, possibly confusing the systems.., im not too familiar with all the firewall/NAT settings ,i think i have everything turned off, but its still not working..
If anyone can help it would be greatly appreciated, im not sure what else to do.
Thank you for your time

This sounds more like a protocol or a driver issue rather than an addressing issue. Which protocol is being used to connect to the printer? You mention the GIMP driver gets loaded, which I read that it's an automatic function rather than you having to manually browse to the driver.
Also, I would look at trying the Gutenprint drivers from Sourceforge rather than the included GIMP-Print.
The other thing would be to check the cups error log on the server. It could give some clues as to why the spool file is taking so long.

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.

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 ....

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.

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 ?
> >>
> >>
> >
>
>

CIPC Doesnt take voice vlan Ip Address

ia have my pc (windows) connected to a 3com switch and its takes the ip address from an active directory. but to apply Voice QoS, i need that the CIPC takes an ip address from the voice vlan. placing a 7911 or 7941 in the network plug they take the voice vlan ip address. how i configure the CIPC to takes the voice vlan ip address?

CIPC is a SW running on a PC and uses the IP address of the PC.
You just have to configure the the IP address of the TFTP server (Callmanager running the TFTP service).
Therefore there is no need for the phone to get a IP address from the Voice VLAN.
Pierre.

Error:Network address DEFAULT of your computer is not maintained

Hi Experts,
I am creating Document InfoRecord using BAPI :BAPI_DOCUMENT_CREATE from a report program, when i execute it, BAPI is
returning a Error: *Network address DEFAULT of your computer is not maintained.* Can any one suggets on this, or i need to do
any setting for Network Address ?
Pleese respond ASAP.
Thanks and Regards,
ALSDIN

This sounds similar to an issue discussed here
http://www.sapfans.com/forums/viewtopic.php?f=23&t=284434

How to resolve error 'The DPMRA service terminated with service-specific error Only one usage of each socket address (protocol/network address/port) is normally permitted'

One of my exchange 2010 servers dpm agent is give the following error when the dpmra service attempts to start.
The DPMRA service terminated with service-specific error Only one usage of each socket address (protocol/network address/port) is normally permitted..
I have tried uninstalling/reinstalling the agent but this does not resolve the issue
Any help would be greatly appreciated.
Thanks
William Hickson

Hi
Something has probably changed on the protected server side that affects the DPM agent. In some cases the DCOM configuration could change. Look at this blogpost and verify your DPMRA DCOM object.
http://robertanddpm.blogspot.com/2010/08/dpm-ra-rights.html
If this doesn't do the trick try reinstall the agent.
Best Regards
Robert Hedblom
MVP DPM
Check out my DPM blog @ http://robertanddpm.blogspot.com

HP deskjet 3520 network print issues

Getting towards the end of my rope. I have an HP deskjet 3520 with wireless print capability from the network and have successfully been able to send jobs to the printer to print for the last 11 months. It can no longer print jobs from the network despite having an IP address and being visible by all machines connected to the network.
Each time I try to send a document to be printed.
I do not have MAC address filtering enabled on the router. I've updated the firmware via USB connection and re-installed the drivers and software to no effect. I've power-cycled the device, restarted the computer(s) that would print via the network to the printer, etc. I've done everything that I know how to get network printing fixed with no success.
I've also run the print doctor 4.5 program which can find the printer on the network, but then gets no response from the device when trying to access it.
Has anyone else had a similar problem with this model? Any ideas as to what can be done to get it to start printing documents that get sent to it form the network? I've been directed to this forum off web searches, but there are a lot of responses with links in them that have ether been relocated to a different web address, or have been deleted.
Any help is greatly apprectiated.
Thank you for your time.

Hey @Tom801,
Welcome to the HP Support Forums!
I would like assist you today with resolving the network communication issues you're experiencing with your HP Deskjet 3520 e-All-in-One Printer. As I understand, you are able to 'see' the printer through the Print and Scan Doctor and from the other computers on your network. But, you are not able to print to the Deskjet. I have a few troubleshooting suggestions to start with.
Gather the IP Address:
1. Select the Wireless Button on the front panel of your printer.
2. Your IP address should now display, please note down what this is.
Open the EWS Browser:
1. On one of the computers that you would normally use with this printer, open your Internet Browser.
2. In the website address bar at the top of the page type in your IP address (do not include www.)
3. Select enter on your keyboard to search for the printer Embedded Web Server.
Does a website open for your printer?
If the printers website opens than that proves that the printer is in fact still connected and communicating with your wireless network. If the website fails to open than the printer is being blocked from the network.
You noted in your post that you have Mac Filtering disabled, updated the firmware for the printer, and powercycled the printer and computer. Did you ever powercycle the router? If not, can I please have you do that now.
How to Properly Powercycle your Network:
1. First, unplug your routers power cable
2. Power off your printer
3. Power off your computer
4. After 30 seconds to 1 minute plug in your router
5. Turn on your printer
6. Turn on your computer
Once the network connection is re-established on your computer and printer please check your IP address once again on the printer using the steps I provided above.
Can you open the printer website now with the IP Address?
If yes, than it seems like your router had blocked communication to the printer. To avoid this in the future you can:
Open the Router Ports:
- Incoming (UDP) Ports:
137, 138, 161, 427
- Outgoing (TCP) Ports:
137, 139, 427, 9100, 9220, 9500
Also, you can refer to the steps within Printer Does Not Maintain Wireless Connection for additional configuration options. Focus on Solution two for assigning a static IP.
Please let me know if the steps provided resolve you issue. Good luck!
X-23
I work on behalf of HP
Please click "Accept as Solution" if you feel my post solved your issue, it will help others find the solution.
Click the "Kudos, Thumbs Up" on the right to say "Thanks" for helping!

VLAN network address issue

Similar Messages

Maybe you are looking for