IT BS thread

I saw that in the funny pics thread, EPIC!

 

Been messing around with this for a while and can't find anything on google. I have a Linksys WAP200 wireless AP connected to a the company network through a Cisco Cat 2950. AP is setup and when connected, I'm able to connect wirelessly through the router, out of the company network to the internet. Seems like if I disconnect the AP from the switch, my users (who aren't connected via wireless and are going through normal wired network) are losing connection to company servers. Any thoughts?

 

Is your wired subnet/VLAN the same as the Wireless subnet/VLAN?

 

Subnet uses standard 192.168.1.0/24 on both wired and AP. Wired network isn't split up and only uses VLAN 1, VLAN's are disabled on the AP.

 

have you run a tracert when the ap is plugged in and again after it is unplugged to see if it is somehow routing somewhere wierd.

 

I haven't. I'll get here early tomorrow morning and test it out. It has happened twice and both times users have been screaming. It's disconnecting them from our iSeries which runs all business logic. It only disconnects them for a second but it's enough to end all their active sessions and have to start over.

 

I have a fix.

Either don't plug it in at all or don't unplug it once it's plugged in.

 

LOL It's a lose lose for me. If i don't plug it in, I'll have people bitching that they don't have wireless access to the internet. This AP used to connect to a DSL line but that has been cancelled. I'm not positive it is disconnecting users when it's unplugged. That seems to be what's going on but I haven't had it plugged in long enough to know for sure. I've had it plugged in for testing to the production network for maybe 5 minutes. By the time I hear bitching, it could have disconnected them at anytime during those 5 minutes.

You know you can never please everyone.

 

Anyone ever seen windows RDP just stop taking incoming connections on any port you choose?

Win 7 64bit
stock port: 3389 (typically use 3399)
firewall off (don't use them internally)
Never can get RDP to work. internally or externally on one BOX.
Port Forwarding is setup correctly for outside world since my other machines have no issues.
Slashtop works
haven't tried any other RDP programs.

 

Is the terminal services service enabled/running? Making sure connections are allowed. When you nmap it, what do you see? Is 3389 open/closed? I assume this is all on your LAN. I genuinely hope you don't just port forward RDP to the internet...

 

I had several 2008 R2 server that did th same thing after being updated wirh SP1. An MS update fixed it the update was one of the "normal" server updates availble via windows update. Sorry I do not remember which update it was.

 

Do you have RIP enabled? It's almost like your AP is black-hole routing.

 

Terminal services is running (remote desktop service in win7)
haven't ran nmap yet on it
I'm port fwd 3389 right now for testing. Tho changing ports in the reg and port fwd in router has no effect.

I'll look for an update on it. i'm having very little luck solving this.

RIP isn't enabled. When I get home I'll mess around more.

 

The AP doesn't have any mention of RIP. Just a gateway between the wired and wireless LAN.

 

Are there any routes defined in it?

 

No routes defined in the usual sense. I gave the AP an IP address and a default gateway so it probably has a default route to that gateway. But there isn't any other place to define routes.

I might have it working. I disconnected it and didn't hear anybody losing connection. I didn't lose it from my workstation but that doesn't mean anything because I didn't lose it yesterday. I turned on VLAN support and defined VLAN 1 as default (which is how the switch it setup also). The AP's manual says if VLANs are disabled, it drops all tagged VLAN traffic. I probably didn't need to do this but I disabled portfast on the switch interface. I'm going to keep an eye on it and see what happens.

 

Check your gateway addressing... If your ap is setup as a gateway or last resort then traffic is looking to get out through the dsl that was on it. Run your tracert, you will find the bad route.

 

I verified that it is indeed cutting people off when AP is disconnected. Had it connected for 20 or so minutes to see if it would disconnect any users and it didn't. As soon as I disconnected it, it happened again. I got the logs from the switch this time and it looks like the port is receiving a BPDU in trunk mode when the AP is being disconnected which is causing an inconsistent port type. Interface on the switch is not setup to accept 802.1Q encap. I'm going to change the port over to trunk mode and see what happens. Stay tuned.

Thanks for the help guys!

 

God damn... I am having a hell of a time getting to my friggen vmx files!